Yahoo Pixel API

Datafly Signal delivers conversion events to Yahoo server-to-server via the Pixel API for campaign attribution, audience measurement, and ad delivery optimisation across Yahoo DSP and native advertising.

Why route Yahoo Pixel 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 Yahoo Pixel 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 Yahoo Pixel 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 Yahoo Pixel needs to attribute the event to the right session.
• Delivery is batched, rate-limited, and retried. Signal buffers to Kafka, respects the Yahoo Pixel rate limit, and retries on 429 or transient failure rather than dropping the event.
• Token lifecycle is handled for you. Signal obtains and refreshes the OAuth credentials Yahoo Pixel requires, so nothing expires quietly in the middle of a campaign.
• One consent decision governs every destination. Yahoo Pixel 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 Yahoo Pixel API in Signal, you need a Yahoo DSP account with a Dot tag created and API credentials generated.

Configure in Signal

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

Configuration Fields

Management UI Setup

1. Go to Integrations > Add Integration > Yahoo Pixel API.
2. Enter your pixel_id, api_key, and dot_tag_id.
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": "yahoo_pixel",
    "name": "Yahoo Pixel API Production",
    "enabled": true,
    "config": {
      "pixel_id": "yahoo-px-12345",
      "api_key": "ak_yahoo_abc123...",
      "dot_tag_id": "dt-yahoo-67890"
    },
    "consent_categories": ["advertising"]
  }'

API endpoint

POST https://batch.datax.yahoo.com/v1/events/{{pixel_id}}

Allow egress to batch.datax.yahoo.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 Yahoo DSP Console

1. In the Yahoo DSP console, go to Measurement > Tags > your Dot tag.
2. Check the tag activity to confirm events are being received.
3. Navigate to Pixels > your pixel to review pixel-level event data.
4. Events should appear within a few minutes.

Step 3: Validate Campaign Attribution

1. Create a test campaign and associate it with your Dot tag.
2. Confirm that conversion events are attributed correctly in campaign reports.
3. Review audience measurement data to ensure ad delivery optimisation is working.

Troubleshooting