Sprig (Actions) Destination
Sprig (formerly UserLeap) 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 microsurveys, concept tests, and video questions.
Sprig maintains this destination. For any issues with the destination, consult Sprig’s documentation or contact support@sprig.com.
Good to know: This page is about the Actions-framework Sprig Segment destination. There’s also a page about the non-Actions Sprig Cloud (formerly UserLeap) destination. Both of these destinations receive data from Segment.
Benefits of Sprig (Actions) vs Sprig Classic
Sprig (Actions) provides the following benefits over the classic Sprig destination:
- Trigger microsurveys. Because Sprig (Actions) hooks into your browser-based, JavaScript Segment source, it can be used to trigger Sprig microsurveys.
- Code-free Sprig installation. The Sprig (Actions) destination can install the Sprig SDK onto your website, without you having to update any code.
Getting started
- From the Segment web app, click Catalog, then click Destinations.
- Use the navigation on the left to locate and select Sprig (Actions).
- Click Configure Sprig (Actions).
- Select an existing JavaScript website source to connect to Sprig (Actions).
- Find your Environment ID on Sprig Dashboard > Connect > JavaScript. Use the Development Environment ID for a testing environment, and the Production Environment ID for your live website environment. When you configure the destination, input the appropriate Environment ID.
- Select Quick Setup to start with pre-populated subscriptions, or Customized Setup to configure each action from scratch. Click Configure Actions to complete setup.
Destination Settings
| Setting | Description |
|---|---|
| Debug mode | Required. 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 |
|---|---|---|
| Identify User | Event type = "identify" |
Identify User |
| Update User ID | Event type = "alias" |
Update User ID |
| Sign Out User | Event type = "track" and event = "Signed Out" |
Sign Out User |
| Track Event | Event type = "track" and event != "Signed Out" |
Track Event |
Available Actions
Build your own Mappings! Combine supported triggers with the following Sprig-supported actions:
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.
This action does not have any fields.
Update User ID
Set updated user ID.
Update User ID is a Web action.
| Field | Description |
|---|---|
| User ID | Type: STRINGNew unique identifier for the user |
| Anonymous ID | Type: STRINGNew 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.
| Field | Description |
|---|---|
| Event name* | Type: STRINGThe event name that will be shown on Sprig’s dashboard |
| User ID | Type: STRINGUnique identifier for the user |
| Anonymous ID | Type: STRINGAnonymous identifier for the user |
Identify User
Set user ID and/or attributes.
Identify User is a Web action.
| Field | Description |
|---|---|
| User ID | Type: STRINGUnique identifier for the user |
| Anonymous ID | Type: STRINGAnonymous identifier for the user |
| User Attributes | Type: OBJECTThe Segment user traits to be forwarded to Sprig and set as attributes |
Migration from the classic Sprig destination
To prevent duplicate events being created in Sprig, ensure that for each Segment source, this destination and the Sprig Cloud destination are not both enabled at the same time.
This page was last modified: 03 Mar 2022
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!