Skip to main content
The Yahoo Conversions API (CAPI) Connector sends conversion events from Narrative directly to Yahoo’s conversion ingestion API, enabling Yahoo DSP to attribute conversions back to ad campaigns and optimize delivery against real outcomes.

​
Overview

The connector routes conversion data — purchases, signups, leads, and more — from any dataset in Narrative to a Yahoo pixel (dot tag). Events are matched against Yahoo user accounts using hashed emails, hashed phone numbers, mobile advertising IDs, and Yahoo PXIDs. Events are batched and delivered on a schedule you configure. PII fields are SHA-256 hashed before transmission in accordance with Yahoo’s requirements. The Conversions API is a second interface of the same Yahoo app that delivers audiences — one installed connector, one profile, two delivery paths.

​
Prerequisites

  • A Yahoo DSP account with a pixel (dot tag) configured. The pixel’s numeric ID is where your events are delivered.
  • A Narrative dataset containing the conversion data you want to send.

​
Sending conversion events

Delivering conversion events to Yahoo involves three steps: creating a connector profile, preparing your dataset, and adding a connection.

​
Step 1: Create a connector profile

If you already deliver audiences through the Yahoo DSP Connector, you can reuse your existing profile and skip this step.
1

Navigate to the connector

In Narrative, go to Installed Apps and select Yahoo DSP Connector.
2

Configure credentials

Enter your Yahoo DSP API credentials.

​
Step 2: Create your dataset

Your dataset must be mapped to the conversion_event Rosetta Stone attribute. The recommended approach is to map your source data to this attribute and then materialize it using Data Studio or NQL.
The connector requires your dataset to include conversion_event and at least one supported user identifier for user matching. Any dataset that contains the required attributes in the correct schema is eligible for delivery.
See the attribute schema below for the full list of event fields, and Supported user identifiers for the identity attributes your dataset must include.

​
Step 3: Add a connection

1

Open your connector profile

Navigate to the Yahoo connector profile you created in Step 1.
2

Add a new connection

Click Add Connection and select Deliver Conversion Events as the connection type.
3

Configure delivery options

  • Pixel ID (optional) — A default Yahoo pixel ID to deliver events to. Rows that carry their own yahoo_pixel_id route to that pixel instead.
  • Deliver all data — Toggle on to deliver all data currently in the dataset. If off, only new data written after the connection is created will be delivered.
4

Connect

Click Connect to activate. Events will begin delivering on the next scheduled run.

​
The conversion_event attribute

The conversion_event attribute is Narrative’s platform-neutral Rosetta Stone schema for conversion events. When you map your dataset columns to this attribute, Narrative handles transformation, hashing, batching, and delivery to Yahoo’s API.

​
Fields

Rows are validated individually: a row with a missing required field or malformed timestamp is skipped and counted, without blocking the rest of the delivery.

​
Supported user identifiers

In addition to the conversion_event attribute, your dataset must include at least one of the following Rosetta Stone identifier attributes. Yahoo uses these to match conversion events to user accounts. All PII values are SHA-256 hashed by Narrative before transmission.
Hashed identifiers must use SHA256. See Hashing PII for Upload for formatting requirements. PXIDs are automatically prefixed with Narrative’s Yahoo partner ID so Yahoo can attribute their source.

​
Reference

​
Routing

Events are grouped by pixel ID and delivered per pixel. A single dataset can serve multiple pixels: set yahoo_pixel_id on each row, or leave it off and set a default Pixel ID on the connection.

​
Deduplication

Narrative tracks the events already delivered for each connection and skips them on subsequent runs, so re-delivering a dataset does not double-count conversions. Provide a stable event_id (order number, transaction ID) per event.

​
Batching

Events are delivered in batches to Yahoo’s ingestion API. Batch sizes are tuned automatically based on the size of your events.

​
Data privacy

Narrative hashes all customer information fields (email, phone number) using SHA-256 before transmission. Raw PII is never sent to Yahoo.

​
Related content

Yahoo DSP Connector

Deliver audience data to Yahoo DSP for programmatic advertising

Meta Conversions API Connector

Send conversion events to Meta

Data Activation Overview

Understand how connectors deliver data

Hashing PII

Prepare identifiers for delivery