Skip to Content
DestinationsAdvertisingGoogle Ad Manager

Google Ad Manager

Sync audience segments to Google Ad Manager for publisher ad targeting. Upload your warehouse segments as first-party audience segments.

Prerequisites

  • A Google Ad Manager account
  • Your Network Code (found in Admin > Network settings)
  • A Google account with API access to the Ad Manager network

Authentication

Google Ad Manager uses OAuth 2.0 with PKCE.

  1. Click Connect with OAuth in Zeotap
  2. Sign in with your Google account
  3. Authorize the requested permissions

OAuth scope: https://www.googleapis.com/auth/dfp.

Configuration

FieldTypeRequiredDescription
Network CodeTextYesYour Google Ad Manager network code (numeric). Found in Admin > Network settings. Example: 12345678

Target Settings

FieldTypeRequiredDescription
Audience Segment NameTextYesName for the first-party audience segment
Audience Segment IDTextNoExisting audience segment ID. Leave blank to create a new segment.

Per-row audience segments

Audience Segment Name can be taken from a column instead of being fixed for the sync, so one sync fans out across several first-party audience segments.

To set it up, open the sync’s Destination target overrides, switch the field from Fixed value to From column, and pick the column. The switch adds a row to the sync’s field mapping, so you can also see and edit the binding — including adding a transform — in the Map fields editor. The fixed value you leave behind becomes the fallback applied to rows whose column is empty.

Zeotap groups each batch by the resolved name and uploads once per distinct segment.

Limiting how many segments a run can create

Because a new Audience Segment Name creates a segment, binding a high-cardinality column by mistake — a user id, say — would create one per profile. Max distinct values per run (default 500) caps this: if a run needs to create more than the limit allows, it fails with an error naming the field and the offending value, and nothing further is created. Set it to 0 for no limit.

Ad Manager offers no lookup-by-name, so Zeotap cannot reuse a segment created by an earlier run — each run creates a new segment per distinct value. Keep the bound column’s cardinality low, and prefer setting Audience Segment ID when you have a single fixed target.

Mirror mode cannot express a move. A profile that moves from one segment to another appears in the diff as a changed row carrying only its current value, so it is added to the new one but never removed from the old. Prefer Add and Remove sync modes when Audience Segment Name comes from a column.

Supported Operations

Sync Modes: Upsert

Audience Sync Modes: Add, Remove, Mirror, Upsert

Features

  • Field Mapping: No
  • Schema Introspection: No

Match Keys

Google Ad Manager audience segments are populated with hashed identifiers. Map raw columns and Zeotap normalizes and hashes them at delivery, or map pre-hashed SHA-256 hex digests directly:

FieldTypeDescription
emailstringRaw email address — lowercased, trimmed, and SHA-256 hashed before upload
hashed_emailstringPre-hashed SHA-256 hex digest of the lowercase, trimmed email
phonestringRaw phone number — normalized to E.164 (digits with leading +) and SHA-256 hashed before upload
hashed_phonestringPre-hashed SHA-256 hex digest of the E.164 phone number

When both a raw field and its pre-hashed counterpart are mapped, the pre-hashed value wins. Values that are not valid 64-character hex digests are never uploaded — they are dropped (falling back to the raw column if mapped) and counted in the sync run logs. See Match Keys & Identifier Hashing for the full normalization contract, precedence, and validation rules.

Troubleshooting

Network Code not found

Find your Network Code in Google Ad Manager under Admin > Global settings > Network settings. It is a numeric value.

Insufficient API access

Ensure the authenticated Google account has API access enabled in the Ad Manager network settings (Admin > Global settings > Network settings > API access).

Last updated on