adMarketplace

Send conversion events to adMarketplace for search advertising attribution and performance measurement across partner search channels.

Why route adMarketplace through Datafly Signal

  • Conversions survive ad blockers and tracking prevention. A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari’s ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions adMarketplace optimises against are not filtered by the browser.
  • Email is hashed before leaving your infrastructure. Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so adMarketplace receives match keys rather than raw personal data.
  • Client IP and user agent are carried in the payload. Both are taken from the original visitor request rather than your server, which is what adMarketplace needs to attribute the event to the right session.
  • One consent decision governs every destination. adMarketplace is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
  • No vendor tag on the page. Removing it removes its page weight and its independent access to your visitors.

Prerequisites

Complete these steps with adMarketplace before configuring the integration in Signal.

Create or access your adMarketplace account

Ensure you have an active adMarketplace account with advertiser access. If you don’t have an account, visit adMarketplace to get started or contact their sales team.

Get your Account ID from your adMarketplace rep

Your Account ID is provided by your adMarketplace account representative. This is the unique identifier for your advertiser account used for conversion attribution. If you don’t have it, reach out to your adMarketplace contact.

Request an API key from adMarketplace support

API keys for server-side conversion uploads are provisioned by adMarketplace support. Contact your account manager or submit a request through the adMarketplace support portal to receive your API key.

Configuration

FieldTypeRequiredDescription
account_idstringYesYour adMarketplace account ID. Provided by your adMarketplace account manager.
api_keysecretYesAPI key for authenticating server-side conversion uploads. Provided by your adMarketplace account manager.

Signal Setup

Quick Setup

  1. Navigate to Integrations in the sidebar.
  2. Open the Integration Library tab.
  3. Find adMarketplace or filter by Advertising.
  4. Click Install, select a variant if available, and fill in the required fields.
  5. 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/admarketplace/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "adMarketplace",
    "variant": "default",
    "config": {
      "account_id": "amp-12345",
      "api_key": "ak_amp_abc123..."
    },
    "delivery_mode": "server_side"
  }'

Event Mapping

The default Retail preset maps a minimal set of conversion events:

Signal eventadMarketplace event
pagepage_view
Product Viewedview_content
Product Addedadd_to_cart
Order Completedpurchase

To customise or extend, edit the integration’s Field Mappings in the Management UI.

Delivery

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

Testing

  1. Install the integration with your Account ID and API key.
  2. Trigger a test event (e.g. a purchase) on your site with the Datafly.js collector active.
  3. Check the Live Events view in Signal to confirm the event was captured.
  4. Verify the event appears in your adMarketplace reporting dashboard.
  5. Check the Delivery Log in Signal for confirmation of successful delivery (HTTP 200 response).
⚠️

Report any unexpected behaviour to both the Datafly Signal team and your adMarketplace account manager.

Troubleshooting

IssueResolution
401 UnauthorizedVerify your API key is correct. Contact your adMarketplace rep to confirm the key is still active.
403 ForbiddenYour account may not have API access enabled. Contact adMarketplace support to verify permissions.
Events not appearing in adMarketplaceConfirm the integration is enabled in Signal and check the Delivery Log for errors. Contact your adMarketplace rep if events are delivered successfully but not appearing in reports.
400 Bad RequestCheck that the Account ID is in the correct format as provided by adMarketplace.

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