PubMatic

Register audience segments with PubMatic’s Register Audience API. PubMatic matches inventory to the registered audience through the bid-stream using your dataProviderId + providerAudienceId — this integration is registration-only and does not push member identifiers to PubMatic.

Prerequisites

A PubMatic account of type PUBLISHER, BUYER, or DEMAND_PARTNER
Your PubMatic-assigned numeric Account ID
Your PubMatic-assigned Data Provider ID
Access to PubMatic’s Developer Integration API to generate a Bearer token
A Provider Audience ID you control (unique per audience registration)

Authentication

PubMatic uses Bearer Token authentication obtained via the Developer Integration API:

Using your PubMatic userName, password, and apiProduct, call the token-generation endpoint to receive an accessToken and refreshToken.
Paste the accessToken into the Access Token field. The refreshToken can be pasted into the optional Refresh Token field for your records.
Refresh the access token every 55 days via PubMatic’s refresh endpoint (tokens expire at 60 days).

Do not exceed 200 token-generation attempts within any 20-minute window — exceeding this limit automatically disables the account.

Configuration

Field	Type	Required	Description
Account ID	Number	Yes	Numeric PubMatic account identifier.
Account Type	Select	Yes	`PUBLISHER`, `BUYER`, or `DEMAND_PARTNER`. Default: `PUBLISHER`.
Data Provider ID	Text	Yes	PubMatic-assigned identifier for the data feed.
Category	Select	Yes	Audience category. Set to `THIRD_PARTY_AUDIENCE`.

Target Settings

Field	Type	Required	Description
Provider Audience ID	Text	Yes	Unique identifier for this audience within your platform.
Audience Name	Text	Yes	Human-readable name. Max 256 chars.
Description	Textarea	No	Optional description. Max 1024 chars.
Definition	Textarea	No	Textual rule definition (label-only, no functional effect on PubMatic). Max 1024 chars.
Price (USD)	Number	Yes	Sale price. Must be ≥ 0.

Supported Operations

Sync Modes

PubMatic is audience-only; regular data-sync modes are not supported.

Audience Sync Modes

Mode	Supported
Add	Yes
Remove	No
Mirror	No
Upsert	No

Remove, Mirror, and Upsert are unsupported because PubMatic’s Register Audience API has no member-removal or upsert semantics — disabling an audience (enabled=0) permanently deletes its data and cannot be reversed.

Features

Field Mapping: No
Schema Introspection: No

How It Works

Register audience: On sync start, Zeotap POSTs your audience metadata to https://api.pubmatic.com/v1/audience/audiences. PubMatic returns the registered audience record.
Bid-stream matching: PubMatic matches inventory to your registered audience during the bid-stream flow using your dataProviderId + providerAudienceId. No per-row identifiers are uploaded through this API.
Idempotent retries: Re-running the sync re-POSTs the registration; duplicate registrations are treated as success.

Rate Limits

Token generation: at most 200 attempts per 20-minute window (exceeding disables the account).
Audience registration: contact your PubMatic account manager for tier-specific throughput limits.

Troubleshooting

Invalid or expired bearer token

Your access token has expired or was not issued with access to the Register Audience API. Generate a fresh token via PubMatic’s Developer Integration API and update the Access Token field.

Audience not appearing in PubMatic UI

The Register Audience API returns 200 on successful registration. If the audience is registered but not visible in the UI, verify the accountId you provided matches the account you are logged into, and confirm the dataProviderId is recognised.

Rate-limit / account disabled

You exceeded the 200-token-generation-per-20-minute limit. Contact PubMatic support to re-enable your account.

Audience matches zero impressions

Matching depends on PubMatic’s bid-stream enrichment using your dataProviderId + providerAudienceId — ensure both IDs have been set up with PubMatic and that your provider pipeline is publishing matching signals.