Attentive

Personalised SMS and email marketing platform focused on driving revenue through conversational commerce.

⚠️

This integration is currently in beta. Configuration and behaviour may change.

Prerequisites

Complete these steps in Attentive before configuring Signal.

Create or access your Attentive account

Log in to the Attentive dashboard at ui.attentivemobile.com. If you do not have an account, contact your Attentive representative.

Find your Company ID

Navigate to Settings > Account in the Attentive dashboard. Your Company ID is displayed on this page. Copy it for use in Signal configuration.

Create an API key

Go to Settings > API Keys (or Integrations > API Keys) and click Create API Key. Provide a name (e.g. “Datafly Signal”) and select appropriate permissions for event tracking and subscriber management. Copy the API key immediately.

Note your Sign-Up Source ID (optional)

If you want to attribute new subscribers to a specific sign-up source, navigate to Sign-Up Units in the Attentive dashboard. Find or create the sign-up unit and note the Source ID. This is optional but recommended for attribution tracking.

Configuration

FieldTypeRequiredDescription
api_keysecretYesYour Attentive API key. Generated in Settings > API Keys.
company_idstringYesYour Attentive company identifier. Found in Settings > Account.
sign_up_source_idstringNoThe sign-up source ID for attributing new subscriber sign-ups. Found in Sign-Up Units.

Signal Setup

Quick Setup

  1. Navigate to Integrations in the sidebar.
  2. Open the Integration Library tab.
  3. Find Attentive or filter by CDP.
  4. Click Install, and fill in the required fields with the credentials gathered above.
  5. Click Install Integration to create the integration with a ready-to-use default configuration.

API Setup

curl -X POST http://localhost:8084/v1/admin/integration-catalog/attentive/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Attentive",
    "variant": "default",
    "config": {
      "api_key": "attentive_api_xxxxxxxxxxxx",
      "company_id": "your-company-id",
      "sign_up_source_id": "src-12345"
    },
    "delivery_mode": "server_side"
  }'

Event Mapping

Signal events are mapped to Attentive API calls as follows:

Signal EventAttentive ConceptNotes
pageCustom EventPage view data sent as a custom event with URL and page properties
trackCustom EventEvent name and properties forwarded as custom events for triggering journeys
identifySubscriber updateEmail, phone, and traits used to create or update subscriber profiles
track (purchase)eCommerce EventPurchase events with order and product data sent as eCommerce events

When a sign_up_source_id is configured, new subscribers identified through Signal events are attributed to that source.

Delivery

Events are delivered server-side from your Datafly Signal infrastructure directly to the Attentive API. No client-side scripts are loaded for this integration.

Testing

  1. After installing the integration, trigger a test event from your website or via the Signal event API.
  2. In Attentive, navigate to Subscribers and search for the test user by email or phone number to verify the profile was created or updated.
  3. Check the Event Log (if available) or create a test journey triggered by your custom event to verify event delivery.
  4. In Signal, check the Live Events view to confirm the event was delivered with a 200 response status.

Troubleshooting

SymptomPossible CauseResolution
401 UnauthorizedInvalid or expired API keyRegenerate the API key in Attentive Settings > API Keys and update the integration config
400 Bad RequestMissing or invalid company IDVerify the company ID in Attentive Settings > Account
Subscribers not createdMissing phone number or emailAttentive requires at least a phone number or email to create a subscriber profile
Events not triggering journeysJourney not configured for the eventEnsure your Attentive journey is set to trigger on the specific custom event name being sent

Visit Attentive documentation for full API reference and subscriber management details.