Knowledge Base

Overview

Yahoo’s Conversion API (CAPI) enables advertisers to send offline conversion events (e.g., in‑store purchases, phone call conversions) for measurement, attribution, and optimization in Yahoo DSP. Narrative’s connector streamlines this by transforming your dataset and delivering compliant payloads automatically on a daily cadence.

• Server‑to‑server delivery; no pixels or browser tracking required.
• Works with and without a product catalog.
• Multiple identifiers supported (hashed email/phone, device IDs, PXID) to improve match rates.

Reference: Yahoo Standard Conversion API.

How it works with Narrative

• You provide a dataset of offline conversion events in Narrative.
• Narrative normalizes and formats the data (via Rosetta Stone) to Yahoo’s schema.
• Narrative handles authentication, scheduling, batching, and delivery to Yahoo.
• Delivery cadence follows the materialized view refresh; when new rows exist, they are sent automatically.

Key capabilities

• Supports SHA256 hashed email/phone, gpsaid, idfa, and pxid.
• Per‑dataset or per‑connection Pixel ID configuration; a dataset may target multiple Pixel IDs.
• Daily batch delivery aligned to your view’s refresh schedule.
• Built‑in retry with basic deduplication safeguards on retries.

Important considerations

• Attach each Pixel ID to a dataset/connection only once. Multiple attachments for the same Pixel can produce duplicate event delivery.
• This connector targets batch delivery (not real‑time streaming).

Related reading