Amobee

Send conversion events to Amobee (now Nexxen) for programmatic campaign attribution, audience insights, and cross-channel performance measurement.

Prerequisites

Complete these steps in the Nexxen (formerly Amobee) platform before configuring the integration in Signal.

Create or access your Nexxen (formerly Amobee) account

Log in to the Nexxen platform (formerly Amobee). If you don’t have an account, contact Nexxen sales to set up an advertiser account. You’ll need advertiser-level access with pixel management permissions.

Create a conversion pixel in the Nexxen platform

Navigate to Pixels > Manage Pixels in the Nexxen platform. Click Create Pixel to set up a new conversion tracking pixel. Configure the pixel type (e.g. purchase, lead, page view) to match the conversions you want to track server-side through Signal.

Find your Advertiser ID and Pixel ID

Your Advertiser ID is found under Advertiser Settings in the Nexxen DSP platform. The Pixel ID is shown in the pixel management interface next to the pixel you created in the previous step. Note both values for the Signal configuration.

Generate an API key from Settings

Navigate to Settings > API Access in the Nexxen platform to generate an API key. This key authenticates server-side event delivery from Signal. If you don’t see API Access in Settings, contact your Nexxen account manager to have it enabled.

Configuration

Field	Type	Required	Description
`advertiser_id`	string	Yes	Your Amobee/Nexxen advertiser ID. Found in the Nexxen platform under Advertiser Settings.
`api_key`	secret	Yes	API key for authenticating server-side event delivery. Generate in the Nexxen platform under Settings > API Access.
`pixel_id`	string	Yes	Your Amobee/Nexxen tracking pixel ID. Found in the Nexxen platform under Pixels > Manage Pixels.

Signal Setup

Quick Setup

Navigate to Integrations in the sidebar.
Open the Integration Library tab.
Find Amobee or filter by Advertising.
Click Install, select a variant if available, and fill in the required fields.
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/amobee/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Amobee",
    "variant": "default",
    "config": {
      "advertiser_id": "adv-amobee-12345",
      "api_key": "ak_amobee_abc123...",
      "pixel_id": "px-amobee-67890"
    },
    "delivery_mode": "server_side"
  }'

Event Mapping

Signal Event	Amobee/Nexxen Event	Description
`purchase`	`Purchase`	Completed transaction with revenue
`add_to_cart`	`AddToCart`	Product added to shopping cart
`page_view`	`PageView`	Standard page view tracking
`sign_up`	`SignUp`	New user registration
Custom events	Custom pixel fire	Map any Signal event to a custom Amobee pixel event via blueprint configuration

Event mappings are fully configurable through blueprints. The table above shows common default mappings — you can customise these to match your campaign goals.

Delivery

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

Testing

Install the integration with your Advertiser ID, API key, and Pixel ID.
Trigger a test event (e.g. a purchase) on your site with the Datafly.js collector active.
Check the Live Events view in Signal to confirm the event was captured.
Verify the pixel fire appears in the Nexxen platform under Pixels > Reporting.
Check the Delivery Log in Signal for confirmation of successful delivery (HTTP 200 response).

⚠️

Conversion data may take up to 30 minutes to appear in Nexxen reporting due to processing delays on the platform side.

Troubleshooting

Issue	Resolution
`401 Unauthorized`	Verify your API key is correct and has not been revoked. Regenerate in Nexxen Settings > API Access if needed.
`404 Not Found`	Check that the Advertiser ID and Pixel ID match your account exactly. Ensure the pixel has not been deleted.
Events not appearing in Nexxen	Confirm the integration is enabled in Signal and check the Delivery Log for errors. Conversions may take up to 30 minutes to appear.
`400 Bad Request`	Verify the Pixel ID is valid and the pixel type matches the event type being sent.
`429 Too Many Requests`	Nexxen rate limits are being hit. Signal will automatically retry with backoff.

Visit Nexxen documentation for full API documentation and credential setup instructions.

Amnet Clinch