The five Google connectors, which Google product each one reaches, and the consent rules common to all of them.
Google is the only vendor mediarithmics reaches across more than one kind of platform:
Google Ads - a buying platform;
Google Ad Manager - an ad server and exchange;
DV360 - a DSP;
BigQuery - a cloud data warehouse, documented under Sources.
Which connector to use
Google Ads
Server-side, offline hashed data. Reaches identified visitors, and is the only route that can exclude existing customers from acquisition campaigns.
Google Ads
Client-side. Reaches visitors who are not logged in. The audience grows only from setup onwards.
Ad Exchange, Ad Manager, DV360 Advertiser, DV360 Partner
The Google Audience API partner connector, shown as DDP connector in the interface. The broadest reach of the five.
What each connector sends
Server-side
Mobile IDs, Hashed emails (SHA-256), Hashed phone numbers (SHA-256), Profile data
Server-side
Mobile and TV advertising IDs, network IDs, PPIDs, user account IDs
Consent applies to all of them
Since March 2024 Google requires a confirmation of user consent status whenever audiences are shared to its advertising products. What you must set depends on your datamart's region and on the connector - including one case where the fields must be left empty.
Beyond advertising
Google BigQuery is not an advertising connector. It connects a BigQuery project to mediarithmics for data warehouse synchronisation, and lives under Sources.
Partner documentation
Google Ads documents its own platform at https://support.google.com/google-ads/. Use it for anything that happens on the partner side of this connector: account setup, the fields the partner expects, and its own limits.
Last updated
Was this helpful?