Xandr

Datafly Signal delivers conversion events to Xandr (Microsoft Invest) server-to-server for programmatic campaign attribution, audience targeting, and cross-channel performance measurement across the Xandr marketplace.

Why route Xandr 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 Xandr 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 Xandr 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 Xandr needs to attribute the event to the right session.
• One consent decision governs every destination. Xandr 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

Before configuring Xandr in Signal, you need a Xandr (Microsoft Invest) account with a conversion pixel created and API credentials generated.

Configure in Signal

Now that you have your Member ID, Advertiser ID, Pixel ID, and API key, configure the integration in Signal.

Configuration Fields

Vendor Click IDs

Signal automatically captures the following Xandr click identifiers from URL parameters:

This is captured automatically by the Datafly.js collector and forwarded with conversion events.

Management UI Setup

1. Go to Integrations > Add Integration > Xandr.
2. Enter your member_id, advertiser_id, pixel_id, and api_key.
3. Select consent categories (typically advertising).
4. Click Save.

Management API Setup

curl -X POST http://localhost:8084/v1/admin/integrations \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "source_id": "src_abc123",
    "vendor": "xandr",
    "name": "Xandr Production",
    "enabled": true,
    "config": {
      "member_id": "12345",
      "advertiser_id": "xandr-adv-67890",
      "pixel_id": "xandr-px-11223",
      "api_key": "ak_xandr_abc123..."
    },
    "consent_categories": ["advertising"]
  }'

API endpoint

GET https://secure.adnxs.com/sspx?id={{pixel_id}}

Allow egress to secure.adnxs.com from the network your delivery workers run on.

Event Mapping

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

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

Testing Your Integration

Step 1: Send a Test Event

1. Trigger a page view or conversion event on your website.
2. Check the Signal event debugger in the Management UI to confirm the event was captured and delivered.

Step 2: Verify in Xandr Console

1. In the Xandr console, go to Pixels > your pixel.
2. Check the pixel activity log to see received events.
3. Events should appear within a few minutes.

Step 3: Validate Campaign Attribution

1. Create a test campaign and associate it with your conversion pixel.
2. Confirm that conversion events are attributed correctly in campaign reports.
3. Verify that xandr_uid click IDs are being matched for user-level attribution.

Troubleshooting