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
| Field | Type | Required | Description |
|---|---|---|---|
api_key | secret | Yes | Your Attentive API key. Generated in Settings > API Keys. |
company_id | string | Yes | Your Attentive company identifier. Found in Settings > Account. |
sign_up_source_id | string | No | The sign-up source ID for attributing new subscriber sign-ups. Found in Sign-Up Units. |
Signal Setup
Quick Setup
- Navigate to Integrations in the sidebar.
- Open the Integration Library tab.
- Find Attentive or filter by CDP.
- Click Install, and fill in the required fields with the credentials gathered above.
- 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 Event | Attentive Concept | Notes |
|---|---|---|
page | Custom Event | Page view data sent as a custom event with URL and page properties |
track | Custom Event | Event name and properties forwarded as custom events for triggering journeys |
identify | Subscriber update | Email, phone, and traits used to create or update subscriber profiles |
track (purchase) | eCommerce Event | Purchase 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
- After installing the integration, trigger a test event from your website or via the Signal event API.
- In Attentive, navigate to Subscribers and search for the test user by email or phone number to verify the profile was created or updated.
- Check the Event Log (if available) or create a test journey triggered by your custom event to verify event delivery.
- In Signal, check the Live Events view to confirm the event was delivered with a
200response status.
Troubleshooting
| Symptom | Possible Cause | Resolution |
|---|---|---|
401 Unauthorized | Invalid or expired API key | Regenerate the API key in Attentive Settings > API Keys and update the integration config |
400 Bad Request | Missing or invalid company ID | Verify the company ID in Attentive Settings > Account |
| Subscribers not created | Missing phone number or email | Attentive requires at least a phone number or email to create a subscriber profile |
| Events not triggering journeys | Journey not configured for the event | Ensure 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.