This destination lets you push data from various sources into Attentive to maintain an up-to-date subscriber list for mobile messaging campaigns. Add attributes to subscribers in Attentive to build better segments for
personalized experiences and create user-associated events to trigger targeted workflows.
To use the Attentive destination in Hightouch, you will need to generate an API key within Attentive.
To generate the API key, follow these steps.Ensure that the generated key has the correct scopes for the endpoints you wish to use:
Identity:identity:write
Custom Events:events:write
Custom Attributes:attributes:write
Product Catalog:product_catalogs:write
Additionally, within Attentive, set Event webhook status to Enabled and Subscriber to event notifications to Subscription webhook for your app.
Syncing to Attentive identities lets you associate a client user identifier or custom identifier with other identifiers. A client user or custom identifier must be accompanied by at least one of the following identifiers:
phone, email, Shopify ID, Klaviyo ID, client user ID, or custom identifier.
Refer to the Attentive Identity API docs to learn more.
Syncing custom events lets you send user actions to use in the Attentive Segment Builder and the Journey Builder.
This data can’t contain any sensitive or special categories of information as defined in applicable data
protection and privacy laws, including the California Consumer Privacy Act (CCPA) and California Privacy Rights Act (CPRA).Refer to the Attentive Custom Events API docs to learn more.
To ensure syncs send each event, your event model must use a truly unique primary key. See the events syncs documentation for more information.
The event type can be a static value or a field from the model to send multiple different event types.
The event type name is case-sensitive. For example, “Order shipped” and “Order Shipped” are different event types.
Hightouch allows you to send a timestamp of when a custom event occurred in ISO 8601 format.
If the timestamp is older than 12 hours, relevant Journeys aren’t triggered in Attentive.
If an event doesn’t include a timestamp, the time of the API request is used.
You can use properties to send metadata associated with the event.Object keys are expected to be strings and can’t contain any of the following special characters:
Syncing custom attributes lets you send attribute-based user data to Attentive. You can create as many custom attributes as needed. Note that you can create net-new properties with this API, however,
it can’t be used to create new values for an existing UI-created property name. Whenever you create a property name on the Attentive platform, you must also define all possible property values there. Refer to the Attentive Attributes API docs to learn more.
User attributes are any metadata associated with a user. Attribute object keys should be strings, and object values can be any type. Both object keys and object values are case-sensitive. “Favorite color” and “Favorite Color” are considered different custom attributes.
You can match rows from your model to message in Attentive on any column in your model and any field in Attentive. Ensure the data types of the model column and Attentive field you select match.
Refer to the record matching docs for more information.
To see the exact API requests and responses from each sync run, use the live debugger. To get notified by Slack, PagerDuty, SMS, or email when a sync fails, set up sync alerts. If you run into an issue this page doesn’t cover, .
