ActionIQ

Enterprise customer data platform for audience management, journey orchestration, and real-time personalisation at scale.

Prerequisites

Complete these steps in ActionIQ before configuring Signal.

Create or access your ActionIQ account

Log in to the ActionIQ platform at app.actioniq.com. If you do not have an account, contact your ActionIQ representative to provision one.

Create a server-side destination

Navigate to Connections > Destinations and click Add Destination. Select Server-Side API as the destination type. Give it a descriptive name (e.g. “Datafly Signal Ingest”) and save.

Note the Destination ID shown after creation — you will need this for Signal configuration.

Generate an API key

Go to Settings > API Keys and click Create API Key. Assign the key appropriate permissions for data ingestion (at minimum, write access to the destination you created). Copy the API key immediately — it will not be shown again.

Find your Account ID

Your Account ID is displayed in Settings > Account or in the URL bar when logged in (e.g. app.actioniq.com/account/ABC123). Copy this value.

Configuration

Field	Type	Required	Description
`api_key`	secret	Yes	Your ActionIQ API key for server-side data ingestion. Generated in Settings > API Keys.
`account_id`	string	Yes	Your ActionIQ account identifier. Found in Settings > Account.
`destination_id`	string	Yes	The destination identifier for this data source. Created when configuring a new inbound data connection.

Signal Setup

Quick Setup

Navigate to Integrations in the sidebar.
Open the Integration Library tab.
Find ActionIQ under the CDP category.
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/actioniq/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "ActionIQ",
    "variant": "default",
    "config": {
      "api_key": "aiq_xxxxxxxxxxxxxxxxxxxx",
      "account_id": "your-account-id",
      "destination_id": "dest-12345"
    },
    "delivery_mode": "server_side"
  }'

Event Mapping

The default ActionIQ blueprint (Retail preset) maps:

Datafly Event	ActionIQ Event	Notes
`page`	`page_view`	URL and page title sent as record attributes
`Product Viewed`	`product_viewed`	Product ID, name, and price
`Order Completed`	`purchase`	Order ID, revenue, and currency
Custom events	Dropped by default	Enable the event in the blueprint to forward

All events include the ActionIQ destination_id so they are routed to the correct inbound connection. Identity resolution is handled by ActionIQ based on the identifiers you include in your event payloads (e.g. email, user ID).

Identity

Signal forwards two identifiers to ActionIQ on every event:

Field	Source	Notes
`user_id`	`datafly.identify()` user ID	The customer ID used by ActionIQ to merge into a single profile.
`email`	`properties.email`	Email address (plain text) used as a deterministic identity key.

Call datafly.identify() whenever a user logs in or submits a form so subsequent events carry a stable user_id:

datafly.identify("user-123", { email: "jane@example.com" });

ActionIQ events should be sent under the marketing consent category by default. If your CMP exposes a separate analytics category, you can broaden the consent categories on the integration to include both.

Visitors who have not granted the required consent are filtered out of delivery by Signal — ActionIQ never receives their events.

Delivery

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

Verify it’s working

After installing the integration, trigger a test event from your website or via the Signal event API.
In ActionIQ, navigate to Connections > Destinations and select your destination. Check the Activity Log for recently received records.
Verify that event attributes (event name, properties, user identifiers) appear correctly.
In Signal, check Live Events to confirm delivery with a 200 response status.

Troubleshooting

Symptom	Possible Cause	Resolution
`401 Unauthorized`	Invalid or expired API key	Regenerate the API key in ActionIQ Settings > API Keys and update the integration config
`404 Not Found`	Incorrect destination ID or account ID	Verify the destination ID and account ID in the ActionIQ dashboard
`429 Too Many Requests`	Rate limit exceeded	ActionIQ applies rate limits per destination. Contact ActionIQ support to increase limits if needed
Events delivered but not visible	Destination not active	Ensure the destination status is Active in ActionIQ Connections

Visit ActionIQ documentation for full API reference and advanced configuration options.