Amnet

Send conversion events to Amnet (Dentsu’s programmatic buying arm) for campaign measurement and audience optimisation across programmatic channels.

⚠️

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

Prerequisites

Complete these steps with your Amnet/Dentsu team before configuring the integration in Signal.

Create or access your Amnet/Dentsu account

Ensure you have an active account with Amnet, Dentsu’s programmatic buying division. If you don’t have an account, contact your Dentsu agency representative to set one up. You’ll need advertiser-level access to your DSP seat.

Get your Seat ID from the Amnet team

Your Seat ID is the unique identifier for your DSP seat within the Amnet platform. This is provided by your Amnet account manager. Contact your Amnet team directly to obtain this value — it is not typically self-service.

Request an API key from your Dentsu account team

API keys for server-side event delivery are provisioned by the Amnet/Dentsu team. Contact your Dentsu account manager to request API access. Provide them with your use case (server-side conversion tracking) so they can provision the appropriate permissions.

Configuration

Field	Type	Required	Description
`seat_id`	string	Yes	Your Amnet DSP seat ID. Provided by your Amnet account manager.
`api_key`	secret	Yes	API key for authenticating server-side event delivery. Provided by your Amnet account manager.

Signal Setup

Quick Setup

Navigate to Integrations in the sidebar.
Open the Integration Library tab.
Find Amnet 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/amnet/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Amnet",
    "variant": "default",
    "config": {
      "seat_id": "seat-12345",
      "api_key": "ak_amnet_abc123..."
    },
    "delivery_mode": "server_side"
  }'

Event Mapping

Signal Event	Amnet Event	Description
`purchase`	`conversion`	Completed transaction with revenue
`add_to_cart`	`add_to_cart`	Product added to shopping cart
`page_view`	`impression`	Page or content view
`sign_up`	`lead`	New user registration or lead
Custom events	Custom conversion	Map any Signal event to an Amnet conversion type 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 Amnet API. No client-side scripts are loaded for this integration.

Testing

Install the integration with your Seat ID and API key.
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 event appears in Amnet’s reporting through your account manager.
Check the Delivery Log in Signal for confirmation of successful delivery (HTTP 200 response).

⚠️

As a beta integration, please report any unexpected behaviour to both the Datafly Signal team and your Dentsu account manager.

Troubleshooting

Issue	Resolution
`401 Unauthorized`	Verify your API key is correct. Contact your Amnet account manager to confirm the key is still active.
`403 Forbidden`	Your seat may not have API access enabled. Contact your Dentsu account team to verify permissions.
Events not appearing in Amnet reports	Confirm the integration is enabled in Signal and check the Delivery Log for errors. Contact your Amnet rep if events are delivered successfully but not appearing in reports.
`400 Bad Request`	Check that the Seat ID is in the correct format as provided by your Amnet account manager.

Visit Dentsu documentation for more information about Amnet programmatic services.

Amazon DSP Events Amobee