Knowledge Base

Prerequisites

• A Narrative dataset containing offline conversion events normalized to the Yahoo Conversion Event attribute (object shape), plus identifiers as available.
• A Yahoo DSP Pixel ID created in the Yahoo DSP UI (Tracking → Create Pixel). Do not reuse a website pixel.
• Conversion rules created in Yahoo DSP to use the incoming events.

Reference: Yahoo Standard Conversion API.

Step 1 — Map your raw data into the conversion_event attribute (object)

Use the UI or API to create a mapping to the conversion event attribute to your convrsion dataset: https://app.narrative.io/platform/discover/data/attributes/conversion_event

Step 2 — Materialize the delivery dataset with the correct schema

Expose the object column as-is in the final dataset that will be connected. The connector expects the conversion_event object column.

CREATE MATERIALIZED VIEW "yahoo_conversion_feed"
  REFRESH_SCHEDULE = '@daily'
  WRITE_MODE = 'append'
AS
SELECT
  "conversion_event"
FROM company_data."normalized_conversion_events";

• The refresh cadence governs daily delivery; when new rows exist, they are sent automatically.
• Keep this dataset focused on the conversion_event object column.

Step 3 — Create the connection

Use Narrative’s Connections API to link the delivery dataset to a Yahoo CAPI profile.

curl --location 'https://app.narrative.io/openapi/connections' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <token>' \
--data '{
  "dataset_id": <DATASET_ID>,
  "profile_id": "<YAHOO_PROFILE_ID>",
  "quick_settings": {
    "type": "conversion_quick_settings",
    "historical_data_enabled": true
  }
}'

Notes:

• Pixel IDs can be configured per dataset or per connection; a dataset may target multiple Pixel IDs.
• Attach each Pixel ID only once to avoid duplicate deliveries.

Delivery, retries, and deduplication

• Delivery is server‑to‑server, aligned to your view’s refresh schedule.
• Basic retry is enabled; duplicate prevention is best‑effort. Avoid attaching the same Pixel ID multiple times to prevent duplicates.

Troubleshooting

• Partial success responses from Yahoo typically indicate invalid events in the batch; validate required fields and types in the conversion_event object.
• Ensure identifiers (when included elsewhere in your pipeline) are lowercased and SHA256 hashed where applicable.
• Verify your Pixel ID is correct and associated rules exist in Yahoo DSP.

Related reading