What is Google Ads Remarketing?
The Google Ads Remarketing destination syncs customers from Masivo audiences into a Google Ads Customer Match user list. You can then use that list for remarketing and lookalike-style campaigns in Google Ads. This integration is separate from Google Ads conversion upload. Remarketing syncs audience membership; conversion upload sends purchase and event conversions.Remarketing uses the Google Data Manager API with OAuth and a GCP project.
It does not require a Google Ads developer token.
Key Features
Audience sync
Add and remove customers when Masivo audiences change
Customer Match
Populate a Google Ads user list for remarketing campaigns
Privacy-first identifiers
Email, phone, and name are hashed with SHA-256 before upload
MCC support
Optional Login customer ID for Manager (MCC) / client account setups
Integration type
Destination (audience sync)
When enabled as a destination on a Masivo audience:- Add: Customers entering the audience are uploaded to your Google Ads user list
- Remove: Customers leaving the audience (or delete signals) are removed by hashed email
- Background processing: A cron worker drains the
google-ads-remarketingqueue in batches
Data flow
Process
The cron batches members, hashes identifiers, and calls Data Manager
audienceMembers:ingest or audienceMembers:remove.Identifiers sent
| Field | Treatment | When used |
|---|---|---|
| Trim, lowercase, SHA-256 (HEX) | Add and remove | |
| Phone | Digits only, SHA-256 (HEX) | Add (if present) |
| First / last name | Trim, lowercase, SHA-256 (HEX) | Add (with full address) |
| Country code | Plain | Add (with full address) |
| Postal code | Plain | Add (with full address) |
Requirements
Google & GCP
Google Ads
Google Ads
- Active Google Ads account - Customer Match user list (Audience Manager) - Numeric Customer ID and User List ID
Google Cloud
Google Cloud
- GCP project with Data Manager API enabled - OAuth 2.0 Web client
(Client ID + Client Secret) - Refresh token with scope
https://www.googleapis.com/auth/datamanager
Not required
Not required
- Google Ads API developer token - Google Ads API enablement for this destination (Data Manager is used instead)
Comparison with Google Ads conversions
| Remarketing | Conversions | |
|---|---|---|
| Purpose | Sync audience lists | Upload conversion events |
| API | Data Manager | Google Ads API |
| Developer token | Not used | Required |
| Main IDs | User List ID, GCP Project ID | Conversion Action ID |
| Catalog ID | google-ads-remarketing | google-ads-destination |
Next step
Setup guide
Configure credentials, OAuth scope, and verify the connection
Google Ads conversions
Track purchases and events as Google Ads conversions