Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Sprig Actions


(information)

Additional versions of this destination are available

This page is about the Sprig Actions. See below for information about other versions of the Sprig destination:

  • Sprig Cloud

Sprig(link takes you to an external page) is an in-context user research platform that makes it fast and effortless for product teams to learn from their actual customers in real-time, through In-Product Surveys, Concept and Usability tests.

Sprig maintains this destination. For any issues with the destination, consult Sprig's documentation(link takes you to an external page) or contact support@sprig.com.


Benefits of Sprig Actions versus Sprig Classic

benefits-of-sprig-actions-versus-sprig-classic page anchor

Sprig Actions provides the following benefits over the Sprig Classic destination:

  • Trigger studies. Sprig Actions integrate into your browser-based Analytics.js source, so you can use them to trigger Sprig studies.
  • Code-free Sprig installation. You can intall Sprig Actions on your website, without you having to update any code.

  1. In the Segment web app, click Catalog, then click Destinations.
  2. Type Sprig in the Filter Destinations field.
  3. Click Sprig, then click Configure Sprig.
  4. Select an existing JavaScript website source to connect to Sprig and click Next.
  5. Type in a Destination name, Select Actions, and click Save.
  6. Type in the Environment ID and click Save Changes. Your Environment ID can be found in Connect > JavaScript(link takes you to an external page). For for information, see Sprig's Environments(link takes you to an external page) documentation.
  7. Select Enable Destinations and click Save Changes.

Property nameTypeRequiredDescription
Debug modeboolean

Optional

Enable debug mode for testing purposes.


Environment IDstring
required

Your environment ID (production or development).


Sprig (Actions) has the following presets

Preset NameTriggerDefault Action
Sign Out UserEvent type = "track" and event = "Signed Out"Sign Out User
Update User IDEvent type = "alias"Update User ID
Track EventEvent type = "track" and event != "Signed Out"Track Event
Identify UserEvent type = "identify"Identify User

Build your own Mappings. Combine supported triggers with the following Sprig-supported actions:

(information)

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

Sign Out User

sign-out-user page anchor

Clear stored user ID so that future events and traits are not associated with this user.

Sign Out User is a Web action. The default Trigger is type = "track" and event = "Signed Out"

This action does not have any fields.

Set updated user ID.

Update User ID is a Web action. The default Trigger is type = "alias"

Property nameTypeRequiredDescription
User IDSTRING

Optional

New unique identifier for the user


Anonymous IDSTRING

Optional

New anonymous identifier for the user

Track event to potentially filter user studies (microsurveys) later, or trigger a study now.

Track Event is a Web action. The default Trigger is type = "track" and event != "Signed Out"

Property nameTypeRequiredDescription
Event nameSTRING
required

The event name that will be shown on Sprig's dashboard


User IDSTRING

Optional

Unique identifier for the user


Anonymous IDSTRING

Optional

Anonymous identifier for the user


Event PropertiesOBJECT

Optional

Object containing the properties of the event

Set user ID and/or attributes.

Identify User is a Web action. The default Trigger is type = "identify"

Property nameTypeRequiredDescription
User IDSTRING

Optional

Unique identifier for the user


Anonymous IDSTRING

Optional

Anonymous identifier for the user


User AttributesOBJECT

Optional

The Segment user traits to be forwarded to Sprig and set as attributes


Migration from Sprig Classic

migration-from-sprig-classic page anchor

Segment placed the Classic destination framework in maintenance mode. Sprig encourages all customers to move to the Actions destination framework. To prevent the generation of duplicate events in Sprig, don't enable the Sprig Web destination and the Sprig Cloud destination on the same source.