Adform

Datafly Signal delivers events to Adform Site Tracking server-to-server using the tracking-points API. Page views and conversions are sent as named tracking points scoped to your advertiser’s Tracking Setup, with cookie- and click-id-based attribution — no client-side Adform pixel required.

Prerequisites

Before configuring Adform in Signal you need:

• An Adform Ad Server or DSP account with Site Tracking enabled.
• A Tracking Setup ID for the advertiser (see below).
• Your tracking domain (the global default is a1.adform.net; you may have a custom or regional domain).
• One or more tracking points configured in Adform, with names that match the event names Signal will send (tracking-point names are case-sensitive).

Find your Tracking Setup ID

1. In the Adform UI, open Site Tracking for your advertiser.
2. Note the Tracking Setup ID — this is the advertiser’s tracking identifier used in every API request.

Find your tracking domain

The global tracking domain is a1.adform.net. If your advertiser uses a custom or regional tracking domain, use that value instead — it must match the domain configured for your tracking points and ad serving.

Configure your tracking points

Each conversion or event you want to record must exist as a tracking point in Adform Site Tracking. The tracking-point name you set in Adform is the value Signal sends in the name field, so keep the names aligned with the blueprint’s event mapping (e.g. Purchase, Add To Cart).

Configure in Signal

Configuration Fields

Management UI Setup

API Endpoint

POST https://{tracking_domain}/v2/sitetracking/{tracking_setup_id}/trackingpoints/

Requests are sent as JSON with Content-Type: application/json. The tracking-points ingestion endpoint is public — attribution is established by the cookie and click-id values carried in the payload, so no API key or access token is required.

Identity Signals

Adform attributes server-side tracking points using cookie and click identifiers, plus the request context. Signal sends these automatically:

Consent

Signal forwards consent to Adform’s compliance block:

Delivery is also gated by the consent categories you select on the integration, so events are only sent when the visitor has granted the relevant category.

Event Mapping

The Default preset maps Signal’s standard events to Adform tracking points:

Conversion data is sent under Adform’s advertiser-defined variables object (for example variables.orderid, variables.sales, variables.currency). The variable names must match the variables configured on your Adform tracking point. To customise, edit the integration’s Field Mappings in the Management UI.

Example: Purchase Event

Datafly.js call:

datafly.track("Order Completed", {
  order_id: "ORD-001",
  revenue: 129.99,
  currency: "GBP",
  products: [
    { product_id: "SKU-A", name: "Widget", price: 49.99, quantity: 2 },
    { product_id: "SKU-B", name: "Gadget", price: 30.01, quantity: 1 }
  ]
});

Adform tracking-point payload sent by Signal:

{
  "name": "Purchase",
  "pageUrl": "https://example.com/checkout/confirmation",
  "identity": {
    "cookieId": "8f3c1a2b-...",
    "clickId": "AbCdEfGhIjKl"
  },
  "userContext": {
    "userAgent": "Mozilla/5.0 ...",
    "userIp": "203.0.113.50",
    "browserLanguage": "en-GB"
  },
  "compliance": {
    "gdpr": true,
    "gdprConsent": "CPx..."
  },
  "variables": {
    "orderid": "ORD-001",
    "sales": 129.99,
    "currency": "GBP",
    "subVariables": [
      { "product_id": "SKU-A", "name": "Widget", "price": 49.99, "quantity": 2 },
      { "product_id": "SKU-B", "name": "Gadget", "price": 30.01, "quantity": 1 }
    ]
  }
}

Testing Your Integration

Troubleshooting