Blueshift
AI-powered customer data platform for predictive segmentation, personalised messaging, and cross-channel campaign orchestration.
Prerequisites
Complete these steps in Blueshift before configuring Signal.
Access your Blueshift account
Log in to the Blueshift dashboard at app.getblueshift.com. If you do not have an account, contact your Blueshift representative.
Find your Event API Key
Navigate to Account Settings > API Keys. Locate your Event API Key — this key is used for sending events server-side. Copy it for use in Signal.
Find your User API Key
On the same API Keys page, locate your User API Key — this key is used for creating and updating customer profiles. Copy it.
Note your Retailer ID (optional, for e-commerce)
If you are tracking e-commerce events (purchases, product views, cart activity), find your Retailer ID in Account Settings > Retailer. This links product catalog data to your events.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
event_api_key | secret | Yes | Your Blueshift Event API key for sending events. Found in Account Settings > API Keys. |
user_api_key | secret | Yes | Your Blueshift User API key for updating customer profiles. Found in Account Settings > API Keys. |
retailer_id | string | No | Your Blueshift retailer identifier. Required for e-commerce event tracking. |
Signal Setup
Quick Setup
- Navigate to Integrations in the sidebar.
- Open the Integration Library tab.
- Find Blueshift 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/blueshift/install \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"name": "Blueshift",
"variant": "default",
"config": {
"event_api_key": "xxxxxxxxxxxxxxxxxxxx",
"user_api_key": "xxxxxxxxxxxxxxxxxxxx",
"retailer_id": "your-retailer-id"
},
"delivery_mode": "server_side"
}'Event Mapping
Signal events are mapped to Blueshift API calls as follows:
| Signal Event | Blueshift Concept | Notes |
|---|---|---|
page | pageload event | URL, title, and referrer sent as event attributes |
track | Custom event | Event name and properties forwarded to the Blueshift Event API |
identify | Customer profile update | Traits sent via the User API to create or update customer records |
track (purchase) | purchase event | Order data, products, and revenue sent as structured purchase events. Requires retailer_id |
Blueshift identifies customers using customer_id or email. Include at least one identifier in every event for proper attribution.
Delivery
Events are delivered server-side from your Datafly Signal infrastructure directly to the Blueshift 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 Blueshift, navigate to Data > Event Stream to view recently received events.
- Search for the test customer under Customers to verify profile creation or update.
- 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 Event or User API key | Verify both API keys in Blueshift Account Settings > API Keys and update the integration config |
400 Bad Request | Missing required fields | Ensure events include at least one user identifier (customer_id or email) |
| Purchase events not tracked | Missing retailer ID | Add the retailer_id to the integration config for e-commerce event support |
| Events delivered but not in Event Stream | Processing delay | Blueshift may take a few minutes to process events. Wait and refresh the Event Stream |
Visit Blueshift documentation for full API reference and event tracking details.