Attentive (Actions) Destination
Beta
This feature is in active development and may change before general availability.
Attentive 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.
The Attentive (Actions) destination uses Attentive's APIs. For more information about the APIs, see the Attentive developer site.
To enable your new Attentive (Actions) destination:
- Create a new private app by opening Attentive's UI and clicking Marketplace > Create App.
- Enter an
App nameandContact email. Then change the permissions for Custom Events, Custom Attributes, eCommerce and Subscribers toWrite. - Then, click
Createto save the app. An API key will be provided. Copy the API key. - Return to Segment and open the destination settings for your Attentive destination.
- Enter the private key into the "API Key" field.
- Enable your Actions destination.
Your Attentive API Key.
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 |
Build your own Mappings. Combine supported triggers with the following Attentive-supported actions:
Mapping limits per destination
Individual destination instances support a maximum of 5 mappings.
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"
At least one identifier is required. Custom identifiers can be added as additional key:value pairs.
Optional
Timestamp for the event, ISO 8601 format.
Optional
A unique identifier representing this specific event.
The type of event. This name is case sensitive. "Order shipped" and "Order Shipped" would be considered different event types.
Optional
Metadata to associate with the event.
Send a subscription request to Attentive.
Subscribe User to Attentive is a Cloud action. The default Trigger is type = "track" and event = "User Subscibed"
At least one identifier is required. Custom identifiers can be added as additional key:value pairs.
Optional
Timestamp for the event, ISO 8601 format.
Optional
A unique identifier representing this specific event.
Type of subscription
Optional
User locale. e.g. "en-US". Either Locale or Signup Source ID is required.
Optional
A unique identifier for the sign up source. Talk to your Attentive represenative. Either Locale or Signup Source ID is required.
Optional
Whether to use single opt-in for the subscription.
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"
At least one identifier is required. Custom identifiers can be added as additional key:value pairs.
Optional
Timestamp for the event, ISO 8601 format.
The type of ecommerce event
List of items.
Upserts custom attributes on a user profile in Attentive.
Upsert Custom Attributes is a Cloud action. The default Trigger is type = "identify"
At least one identifier is required. Custom identifiers can be added as additional key:value pairs.
Metadata to associate with the event.
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.
Segment lets you change these destination settings from the Segment app without having to touch any code.
Your Attentive API Key.