Attentive

The following is a guide on how to integrate Attentive with Marketing.

Attentive is a marketing automation platform. Use it to send personalized SMS and email campaigns to your customers. The Attentive integration transfers opt-in, opt-out, and campaign engagement data from Attentive to Marketing, and lets you trigger SMS sends from Marketing through Attentive Journey.

How the integration works

The Attentive integration is a one-way sync: Attentive to Marketing.

Consent events: SMS subscribe, email subscribe, SMS unsubscribe, and email unsubscribe

Campaign events: SMS sent, email sent, SMS clicked, email clicked, and email opened

The integration transfers each event to Marketing as soon as Attentive triggers it. This applies to every event that occurs after you complete setup.

The integration doesn't transfer consent or unsubscribe changes from Marketing to Attentive. If a customer unsubscribes in Marketing—through consent.page, the email.unsubscribe event, or a scenario—this change stays in Marketing only.

Attentive integration setup

Prerequisites

Before you set up the integration, confirm your project has these IDs configured:

• email_id: Hard ID, lowercase, trimmed. Email address is the primary customer identifier in Marketing.
• attentive_id : Soft ID. Maps to external_id from the Attentive webhook.
• phone_id: Soft ID. Maps to phone from the subscriber entity in the Attentive webhook.

Authentication

After you have checked your prerequisites, you need to set up the authentication first. Please follow these steps to do so:

1. In Marketing, go to Data & Assets > Integrations > Attentive.
2. Get your API key: in your Attentive account, go to App Marketplace > Create App. Enter the app name in App name and your contact email in Contact email. Under Permissions, set Custom Events to Write. Click Create.

3. Open your app under the Built by you tab in the App Marketplace. Go to the Webhooks sub-tab and configure:
   • Event webhook status: Enabled
   • Subscribe to event notifications: Subscription webhook
4. Save the configuration.

5. Go to the Settings sub-tab in your app. Scroll to the API key and copy it.

6. Paste the API key into Marketing.
7. Save the integration.

Map customer IDs and properties

Define how Marketing displays the Attentive identifiers: email_id, attentive_id, and phone_id.

Map consent

Map each Attentive campaign channel you want to track email, sms) to a consent category in Marketing.

For example: map the Email channel to the Email Newsletter consent category. Customers who opt in to email then get a consent event with action set to accept and category set to email newsletter.

Save the integration

Click Save. The integration is now active. From this point on, the integration transfers every Attentive campaign or consent event to your Marketing project.

Trigger SMS send from Marketing through Attentive Journey

1. Go to Scenarios > Actions > Other > Attentive - Sending SMS Campaign.

2. Fill in Message and Title.

3. Under the Settings tab, enable authentication and create a new authentication method for the Attentive webhook. Select HTTP Custom Headers.

4. Name the authentication schema and fill in the fields as shown.

5. Replace <your_token> with your API key.

6. Use the Attentive webhook preset to trigger an SMS send from Marketing.

7. In Attentive, create a Journey that triggers on the SMS Campaign event from Marketing and sends the SMS campaign.

Use cases

• Advanced reporting: Combine Attentive profiles and campaign events with Marketing data.
• Complex segmentation: Segment using running aggregates, expressions, and other Marketing tools.
• Single customer data platform: Sync all data sources into one platform; you don't need to switch between tools.

Limitations

Historical import required

The integration doesn't transfer segments from Marketing to Attentive—that's a limitation of the Attentive API. Instead, Marketing determines which phone numbers should receive a message and transfers each one to Attentive as an individual API call for the actual message sending..

Because of this, you need a one-time historical import of all contacts before setup. This ensures Marketing and Attentive start with matching contact records. After setup, the integration keeps opt-ins and opt-outs in sync going forward—but only the historical import closes the initial gap.

One app per integration

Each Attentive integration in Marketing needs its own app in Attentive. The API key can't be shared across integrations—use one API key per integration. If you skip this, none of your Attentive integrations will work correctly, and events will be misdirected between them.

For each Attentive integration inside Bloomreach, you need to create a separate app in Attentive. That is because the Attentive API key cannot be shared between integrations - only 1 Attentive Api Key per integration. Unless you validate this rule, none of the Attentive integrations will work properly, and events will be randomly shared between integrations.

JavaScript snippet required in the sign-up unit

To track web behavior, add a JavaScript snippet to your sign-up unit in Attentive. This transfers cookie data from Attentive to Marketing.