Overview

The Zeta DSP Conversions API (cAPI) is a secure, server-to-server (S2S) integration that allows advertisers to send conversion events directly from their own systems into the Zeta DSP in near real time. Unlike traditional JavaScript or pixel-based tracking, cAPI is designed for environments where:

• Browser cookies cannot be reliably used

• Conversions occur outside of a web browser

• Advertisers prefer not to deploy pixels on their sites

Examples include mobile applications, physical retail locations (POS systems), call centers, subscription renewals, and backend order management systems.

What Problems Does cAPI Solve

Many advertisers need to attribute conversions that happen beyond the browser. In these cases, conversion events may only be available within first-party systems such as CRM platforms, order databases, or point-of-sale systems.

The Zeta DSP cAPI enables advertisers to send conversion signals directly from their servers to Zeta, use alternative identifiers instead of cookies, log conversions close to the time of the event, and feed real-time performance signals into DSP

Use Cases Currently Supported:

Attribution reporting
Hashed PII-based resolution

Use Cases Coming Soon:

Real-time bidding algorithm optimization
IP/User agent based resolution

How the Zeta DSP cAPI Works

At a high level, the cAPI:

Accepts a conversion or event payload via REST API
Resolves provided identifiers into DSP-supported identifiers
Logs the conversion event into the Zeta DSP

Supported Event Types

While commonly referred to as a Conversions API, this integration can be used to send any event or signal into the DSP, not just purchase conversions. Examples include conversions, impressions, and custom business events.

Supported Identifiers

Supported identifiers include hashed email (MD5 and SHA-256), phone number, Mobile Advertising ID (MAID), Zeta ID, NonID, and multiple cookie-based identifiers.

Availability and Scope

The cAPI is available to DSP-enabled accounts only and complements existing pixel or JavaScript tracking.

Authorization

DSP cAPI uses a non-expiring, revokable token, which is available by request from your account team.