Sprig Actions
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 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 or contact support@sprig.com.
Benefits of Sprig Actions versus Sprig Classic
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.
Getting started
- In the Segment web app, click Catalog, then click Destinations.
- Type Sprig in the Filter Destinations field.
- Click Sprig, then click Configure Sprig.
- Select an existing JavaScript website source to connect to Sprig and click Next.
- Type in a Destination name, Select Actions, and click Save.
- Type in the Environment ID and click Save Changes. Your Environment ID can be found in Connect > JavaScript. For for information, click here.
- Select Enable Destinations and click Save Changes.
Destination Settings
Setting | Description |
---|---|
Debug mode | Enable debug mode for testing purposes. |
Environment ID | Required. Your environment ID (production or development). |
Available Presets
Sprig (Actions) has the following presets:
Preset Name | Trigger | Default Action |
---|---|---|
Sign Out User | Event type = "track" and event = "Signed Out" |
Sign Out User |
Update User ID | Event type = "alias" |
Update User ID |
Track Event | Event type = "track" and event != "Signed Out" |
Track Event |
Identify User | Event type = "identify" |
Identify User |
Available Actions
Build your own Mappings. Combine supported triggers with the following Sprig-supported actions:
Mapping limits per destination
Individual destination instances have support a maximum of 50 mappings.
Sign Out User
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.
Update User ID
Set updated user ID.
Update User ID is a Web action. The default Trigger is: type = "alias"
Field | Description |
---|---|
User ID | Type: STRING New unique identifier for the user |
Anonymous ID | Type: STRING New anonymous identifier for the user |
Track Event
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"
Field | Description |
---|---|
Event name* | Type: STRING The event name that will be shown on Sprig’s dashboard |
User ID | Type: STRING Unique identifier for the user |
Anonymous ID | Type: STRING Anonymous identifier for the user |
Event Properties | Type: OBJECT Object containing the properties of the event |
Identify User
Set user ID and/or attributes.
Identify User is a Web action. The default Trigger is: type = "identify"
Field | Description |
---|---|
User ID | Type: STRING Unique identifier for the user |
Anonymous ID | Type: STRING Anonymous identifier for the user |
User Attributes | Type: OBJECT The Segment user traits to be forwarded to Sprig and set as attributes |
Migration from Sprig Classic
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.
This page was last modified: 04 Oct 2022
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!