Skip to main content
Connect Google Ads to keep a Customer Match list in sync with a Senderz segment. Like Meta, it’s outbound only — Senderz pushes membership continuously and reads nothing back.

​
How it works

1

Connect Google (OAuth)

Authorise Senderz through a dedicated OAuth flow. Manager (MCC) accounts are supported, not just direct-admin.
2

Link a segment

Map a Senderz segment to a Google customer list (1:1).
3

Hourly sync

Senderz diffs the segment against the last snapshot and applies joins and removes.

​
The Data Manager API

Membership ingestion goes through the Data Manager API (datamanager.googleapis.com), not the legacy Google Ads API upload path. Since April 2026, the Ads upload path rejects developer tokens that weren’t already sending Customer Match traffic — so it’s permanently closed to new integrations. The Ads API is still used for the list entity and account metadata.

​
Identity & hashing

Members are matched on hashed email and phone only (Google’s address matching needs given name, family name, region and postal code as a unit, which Senderz contacts don’t carry). Normalisation is Google-specific:
  • Gmail / googlemail addresses have dots and +suffix stripped; other domains keep them.
  • Phones are E.164 with the +.
  • Un-normalisable input is skipped, not hashed as-is.

​
Limits worth knowing

Match rate is available after processing. Manager (MCC) account support is a differentiator — many tools are direct-admin only. This connector is in progress; OAuth and the API clients are being built on top of the shared ad-sync foundation.