DestinationsCrm destinations

Attentive Integration

Step-by-step guide to integrate Ours Privacy with Attentive for sending custom events and updating user attributes to trigger SMS and email journeys while prioritizing privacy and HIPAA compliance.

Attentive Integration

Attentive is an SMS and email marketing platform that helps brands trigger personalized journeys, send transactional messages, and segment subscribers based on behavior. With this integration, you can send custom events to Attentive to fire journeys and update user profiles with attributes used for personalization and segmentation.

Requirements

  • An Attentive account with the ability to create a Private App
  • An API key from your Private App (used as a Bearer token)

Setup

  1. In Attentive, create a Private App and copy its API key. Treat the key as a secret — it grants the same access as a password.
  2. Paste the API key into your Ours Privacy Attentive destination settings. Ours sends it on every request as Authorization: Bearer <API key>.
  3. (Optional) Verify the key by hitting Attentive's /v1/me endpoint with the same Bearer token.

Data Mapping Actions

The Attentive integration supports two action types that you configure in the mapper UI:

Custom Event Actions

Use Custom Event actions to send behavioral events to Attentive. This triggers:

  • SMS and email journey automations (for example "Order Shipped" or "Subscription Cancelled")
  • Behavioral segmentation
  • Personalization tokens inside journey messages

Required Fields:

  • event_name - The custom event type. Sent as type in the Attentive payload. Cannot contain ", ', (), {}, [], \, |, or ,.
  • One of:
    • phone - Phone number in E.164 format (for example +15551234567)
    • email - Email address
    • externalId - Your own user identifier (sent as clientUserId)

Events older than 12 hours are still recorded but will not trigger journeys.

User Attribute Actions

Use User Attribute actions to create or update a profile in Attentive. This is useful for:

  • Keeping first/last name, location, and date of birth in sync for personalization
  • Maintaining custom attributes such as loyalty tier or lifetime value for segmentation

Required Fields: one of

  • phone - Phone number in E.164 format
  • email - Email address
  • externalId - Your own user identifier (sent as clientUserId)

Attentive enforces a maximum of 100 custom attributes per profile, and attribute values cannot be arrays or nested objects.

Common Use Cases

Journey Triggers

Send custom events to fire automated SMS or email journeys, such as:

  • "Order Shipped" or "Order Delivered" notifications
  • "Account Created" welcome flows
  • "Appointment Booked" or "Appointment Cancelled" reminders
  • "Subscription Cancelled" win-back sequences

Profile Enrichment

When a visitor signs up or updates their information, automatically update their Attentive profile with:

  • Name and contact information
  • Date of birth (powers birthday journeys)
  • Location (city, state, postal code, country)
  • Custom attributes such as VIP status or loyalty tier

Privacy and Compliance

This integration is designed to send data to Attentive while maintaining privacy and HIPAA compliance standards. Phone numbers must be E.164 formatted, and Ours Privacy enforces an identifier requirement before any request is sent so events without a valid identifier do not leave your environment.

Additional Information

For more information about Attentive and its capabilities, visit the Attentive website.

How is this guide?

On this page