# Sprig (Actions) Destination

## Destination Info

* Accepts [Page](/docs/segment/connections/spec/page), [Alias](/docs/segment/connections/spec/alias), [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **Sprig (Actions)** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)
* This destination is not compatible with [Destination Insert Functions.](/docs/segment/connections/functions/insert-functions/)
* This integration is **partner owned.** Please reach out to the partner's support for any issues.

> \[!NOTE]
>
> This page is about the Sprig (Actions) Destination. See below for information about other versions of the Sprig destination:
>
> * [Sprig Cloud](/docs/segment/connections/destinations/catalog/sprig-cloud)

[Sprig](https://sprig.com/?\&utm_source=segmentio\&utm_medium=docs_actions\&utm_campaign=integration) 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](https://docs.sprig.com/docs/segment) or contact [support@sprig.com](mailto: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

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](https://app.sprig.com/connect). For for information, see Sprig's [Environments](https://docs.sprig.com/docs/products-and-environments#environments) documentation.
7. Select **Enable Destinations** and click **Save Changes**.

## Destination Settings

| Field          | Description                                      | Required | Type    |
| -------------- | ------------------------------------------------ | -------- | ------- |
| Debug mode     | Enable debug mode for testing purposes.          | No       | boolean |
| Environment ID | Your environment ID (production or development). | Yes      | string  |

## 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](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Sprig-supported actions:

> \[!NOTE]
>
> Individual destination instances have support a maximum of 50 mappings.

* [Sign Out User](#sign-out-user)
* [Update User ID](#update-user-id)
* [Track Event](#track-event)
* [Identify User](#identify-user)

### 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                           | Required | Type   |
| ------------ | ------------------------------------- | -------- | ------ |
| User ID      | New unique identifier for the user    | No       | STRING |
| Anonymous ID | New anonymous identifier for the user | No       | STRING |

### 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                                            | Required | Type   |
| ---------------- | ------------------------------------------------------ | -------- | ------ |
| Event name       | The event name that will be shown on Sprig's dashboard | Yes      | STRING |
| User ID          | Unique identifier for the user                         | No       | STRING |
| Anonymous ID     | Anonymous identifier for the user                      | No       | STRING |
| Event Properties | Object containing the properties of the event          | No       | OBJECT |

### Identify User

Set user ID and/or attributes.

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

| Field           | Description                                                            | Required | Type   |
| --------------- | ---------------------------------------------------------------------- | -------- | ------ |
| User ID         | Unique identifier for the user                                         | No       | STRING |
| Anonymous ID    | Anonymous identifier for the user                                      | No       | STRING |
| User Attributes | The Segment user traits to be forwarded to Sprig and set as attributes | No       | OBJECT |

## 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.