Sprig Cloud Destination
Destination Info
- Accepts Page, Alias, Identify and Track calls.
- Refer to it as UserLeap, or Sprig, or Sprig Cloud in the Integrations object
- This integration is partner owned. Please reach out to the partner's support for any issues.
Additional versions of this destination are available
This page is about the Sprig Cloud Destination. 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.
Segment placed the Classic destination framework in maintenance mode. Sprig encourages all customers to move to the Sprig Actions destination framework when convenient.
- In the Segment web app, navigate to Catalog > 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.
- Enter a Destination name, select Classic, and click Save.
- Type in the Environment ID and click Save Changes. You your Environment ID can be found in Connect > JavaScript. For for information, see Sprig's Environments documentation.
- Select Enable Destinations and click Save Changes.
You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.
For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to false.
When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.
Real-time to batch destination sync frequency
Real-time audience syncs to Sprig Cloud may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.
Segment lets you change these destination settings from the Segment app without having to touch any code.
Find your API key here https://app.userleap.com/settings/installation