Teads

Datafly Signal delivers conversion events to Teads server-to-server for outstream video and display ad attribution, viewability measurement, and campaign performance optimisation.

Why route Teads 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 Teads 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 Teads 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 Teads needs to attribute the event to the right session.
• One consent decision governs every destination. Teads 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 Teads in Signal, you need a Teads account with a tracking pixel created and API credentials generated.

Configure in Signal

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

Configuration Fields

Management UI Setup

1. Go to Integrations > Add Integration > Teads.
2. Enter your 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": "teads",
    "name": "Teads Production",
    "enabled": true,
    "config": {
      "advertiser_id": "teads-adv-12345",
      "pixel_id": "teads-px-67890",
      "api_key": "ak_teads_abc123..."
    },
    "consent_categories": ["advertising"]
  }'

API endpoint

POST https://ca.teads.tv/v1/event

Allow egress to ca.teads.tv 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 Teads Ad Manager

1. In Teads Ad Manager, go to Pixels > your pixel.
2. Check the pixel activity log to confirm events are being received.
3. Events should appear within a few minutes of delivery.

Step 3: Validate Campaign Attribution

1. Create a test campaign and associate it with your pixel.
2. Confirm that conversion events are attributed correctly in campaign reports.
3. Review viewability metrics to ensure ad impressions are tracked alongside conversions.

Troubleshooting