# Sprig Destination

## About this integration

Sprig provides real-time in-context user research through In-Product Surveys and Usability tests. Our Sprig integration sends source data that identifies your users and tracks their activities, so you better understand how they use your product and gaining insights that help you improve your product.

[Mode How we forward source data to the destination: through Customer.io's servers or directly from our JavaScript client.](/cdp/destinations/getting-started/#connection-mode)

[Web sources Indicates whether or not this integration supports our the JavaScript client.](/cdp/sources/getting-started/#types-of-sources)

[API sources Indicates whether or not this integration supports our server libraries (Go, NodeJS, Python), API, Mobile SDK, and other data sources.](/cdp/sources/getting-started/#types-of-sources)

[Supported calls The API methods this integration supports.](/cdp/sources/source-spec/source-events/)

[Integration name The name of this integration if you want to enable or disable it in the `integrations` object.](/cdp/sources/source-spec/common-fields/#the-integrations-object)

Web

[identify](/api/cdp/#operation/identify), [track](/api/cdp/#operation/track), and [alias](/api/cdp/#operation/alias)

sprig-web

## Getting started[](#getting-started)

1.  Go to **[Data & Integrations > Integrations](https://fly.customer.io/workspaces/last/journeys/integrations/all/directory)** and select the **Sprig** entry in the *Directory* tab.
    
2.  (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.
    
3.  Configure your integration.
    
    1.  **Env Id**: Your environment ID (production or development).
        
    2.  **Debug Mode**: Enable debug mode for testing purposes.
        
4.  Click **Enable Destination**.
    

## Actions[](#actions)

When you’re done setting things up, you can go to the *Actions* tab to see how we map incoming data to your integration.

You may need to add actions for this integration

While we often have default triggers for actions, we don't always add those actions as defaults. You may need to add actions to make sure that you're sending all the data that you want to send to your integration. See our [actions](/integrations/data-out/actions/) page for help setting up actions.

Action

Default Trigger

Description

Identify User

`type = “identify”`

Set user ID and/or attributes.

Sign Out User

`type = “track”` and  
`event = “Signed Out”`

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

Track Event

`type = “track”` and  
`event != “Signed Out”`

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

Update User ID

`type = “alias”`

Set updated user ID.