--- "@context": https://schema.org "@type": TechArticle "@id": https://www.twilio.com/docs/segment/connections/destinations/catalog/actions-attentive#article headline: Attentive (Actions) Destination description: Connect the Attentive (Actions) destination in Segment to sync customer and event data through Attentive's APIs by creating a private app and API key. url: https://www.twilio.com/docs/segment/connections/destinations/catalog/actions-attentive inLanguage: en dateModified: 2026-06-10T17:19:57.000Z author: "@type": Organization name: Twilio Developer Education Team publisher: "@type": Organization name: Twilio --- # Attentive (Actions) Destination > \[!IMPORTANT] > > This feature is in active development and may change before general availability. ## 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 **Attentive** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object) * This integration is **partner owned.** Please reach out to the partner's support for any issues. * This destination is **Beta.** [Attentive](https://www.attentive.com/?utm_source=partner-generated\&utm_medium=partner-marketing-\&utm_campaign=partner-generated-4.15.22-segment.io) with Segment makes it easy to sync customer and event data from Segment to Attentive so that you can send highly personalized and timely messages. Attentive Mobile maintains this destination. For any issues with the destination, [contact the Attentive Mobile Support team](mailto:support@attentivemobile.com). The Attentive (Actions) destination uses Attentive's APIs. For more information about the APIs, see the [Attentive developer site](https://docs.attentivemobile.com/). ## Getting started To enable your new Attentive (Actions) destination: 1. Create a new private app by opening Attentive's UI and clicking [Marketplace > Create App](https://ui.attentivemobile.com/integrations/app/setup). 2. Enter an `App name` and `Contact email`. Then change the permissions for Custom Events, Custom Attributes, eCommerce and Subscribers to `Write`. 3. Then, click `Create` to save the app. An API key will be provided. Copy the API key. 4. Return to Segment and open the destination settings for your Attentive destination. 5. Enter the private key into the "API Key" field. 6. Enable your Actions destination. ## Destination Settings | Field | Description | Required | Type | | ------- | ----------------------- | -------- | -------- | | API Key | Your Attentive API Key. | Yes | password | ## Available Presets Attentive has the following presets | Preset Name | Trigger | Default Action | | ---------------------- | -------------------------------------------------- | --------------------------- | | Add to Cart | Event event = "Product Added" | Send Ecommerce Event | | Purchase | Event event = "Order Completed" | Send Ecommerce Event | | View Item | Event event = "Product Viewed" | Send Ecommerce Event | | Subscribe User | Event type = "track" and event = "User Subscribed" | Subscribe User to Attentive | | Upsert User Attributes | Event type = "identify" | Upsert Custom Attributes | ## Available Actions Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Attentive-supported actions: > \[!NOTE] > > Individual destination instances support a maximum of 5 mappings. * [Send Custom Events](#send-custom-events) * [Subscribe User to Attentive](#subscribe-user-to-attentive) * [Send Ecommerce Event](#send-ecommerce-event) * [Upsert Custom Attributes](#upsert-custom-attributes) ### Send Custom Events Send custom Segment analytics events to Attentive. Send Custom Events is a **Cloud** action. The default Trigger is `type = "track" and event != "Product Viewed" and event != "Product Added" and event != "Order Completed" and event != "User Subscribed"` | Field | Description | Required | Type | | ----------------- | ------------------------------------------------------------------------------------------------------------------------------ | -------- | ------ | | User Identifiers | At least one identifier is required. Custom identifiers can be added as additional key:value pairs. | Yes | OBJECT | | Occurred At | Timestamp for the event, ISO 8601 format. | No | STRING | | External Event Id | A unique identifier representing this specific event. | No | STRING | | Type | The type of event. This name is case sensitive. "Order shipped" and "Order Shipped" would be considered different event types. | Yes | STRING | | Properties | Metadata to associate with the event. | No | OBJECT | ### Subscribe User to Attentive Send a subscription request to Attentive. Subscribe User to Attentive is a **Cloud** action. The default Trigger is `type = "track" and event = "User Subscibed"` | Field | Description | Required | Type | | ----------------- | -------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | | User Identifiers | At least one identifier is required. Custom identifiers can be added as additional key:value pairs. | Yes | OBJECT | | Occurred At | Timestamp for the event, ISO 8601 format. | No | STRING | | External Event Id | A unique identifier representing this specific event. | No | STRING | | Subscription Type | Type of subscription | Yes | STRING | | Locale | User locale. e.g. "en-US". Either Locale or Signup Source ID is required. | No | STRING | | Signup Source ID | A unique identifier for the sign up source. Talk to your Attentive represenative. Either Locale or Signup Source ID is required. | No | STRING | | Single Opt-In | Whether to use single opt-in for the subscription. | No | BOOLEAN | ### Send Ecommerce Event Send Segment ecommerce events to Attentive. Send Ecommerce Event is a **Cloud** action. The default Trigger is `event = "Product Viewed" or event = "Product Added" or event = "Order Completed"` | Field | Description | Required | Type | | ---------------- | --------------------------------------------------------------------------------------------------- | -------- | ------ | | User Identifiers | At least one identifier is required. Custom identifiers can be added as additional key:value pairs. | Yes | OBJECT | | Occurred At | Timestamp for the event, ISO 8601 format. | No | STRING | | Event Type | The type of ecommerce event | Yes | STRING | | Items | List of items. | Yes | OBJECT | ### Upsert Custom Attributes Upserts custom attributes on a user profile in Attentive. Upsert Custom Attributes is a **Cloud** action. The default Trigger is `type = "identify"` | Field | Description | Required | Type | | ---------------- | --------------------------------------------------------------------------------------------------- | -------- | ------ | | User Identifiers | At least one identifier is required. Custom identifiers can be added as additional key:value pairs. | Yes | OBJECT | | Properties | Metadata to associate with the event. | Yes | OBJECT | ## Engage You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo). For user-property destinations, an [identify](/docs/segment/connections/spec/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. ## Settings Segment lets you change these destination settings from the Segment app without having to touch any code. | Field | Description | Required | Type | | ------- | ----------------------- | -------- | -------- | | API Key | Your Attentive API Key. | Yes | password |