> ## Documentation Index
> Fetch the complete documentation index at: https://docs.masivo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Ads Remarketing

> Sync Masivo audiences to Google Ads customer match lists via the Data Manager API

## 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](/guides/CDP/integrations/google-ads/overview). Remarketing syncs **audience
membership**; conversion upload sends **purchase and event conversions**.

<Info>
  Remarketing uses the **Google Data Manager API** with OAuth and a GCP project.
  It does **not** require a Google Ads **developer token**.
</Info>

## Key Features

<CardGroup cols={2}>
  <Card title="Audience sync" icon="users">
    Add and remove customers when Masivo audiences change
  </Card>

  <Card title="Customer Match" icon="bullseye">
    Populate a Google Ads user list for remarketing campaigns
  </Card>

  <Card title="Privacy-first identifiers" icon="shield">
    Email, phone, and name are hashed with SHA-256 before upload
  </Card>

  <Card title="MCC support" icon="building">
    Optional Login customer ID for Manager (MCC) / client account setups
  </Card>
</CardGroup>

## 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-remarketing` queue in batches

## Data flow

```mermaid theme={null}
flowchart LR
  A[Audience change in Masivo] --> B[Queue message]
  B --> C[Remarketing cron]
  C --> D[Hash PII]
  D --> E[Data Manager API]
  E --> F[Google Ads user list]
```

<Steps>
  <Step title="Audience update">
    A Masivo audience is created, recalculated, or a member is added/removed.
  </Step>

  <Step title="Enqueue">
    Destination jobs are enqueued on the `google-ads-remarketing` queue.
  </Step>

  <Step title="Process">
    The cron batches members, hashes identifiers, and calls Data Manager
    `audienceMembers:ingest` or `audienceMembers:remove`.
  </Step>

  <Step title="Google Ads">
    Members appear in your Customer Match user list for campaign targeting.
  </Step>
</Steps>

## Identifiers sent

| Field             | Treatment                      | When used               |
| ----------------- | ------------------------------ | ----------------------- |
| Email             | 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) |

At least one of **email** or **phone** is required for an add. Removals require
**email** only.

## Requirements

<Card title="Google & GCP" icon="cloud">
  <AccordionGroup>
    <Accordion title="Google Ads">
      * Active Google Ads account - Customer Match user list (Audience Manager) -
        Numeric Customer ID and User List ID
    </Accordion>

    <Accordion title="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`
    </Accordion>

    <Accordion title="Not required">
      * Google Ads API developer token - Google Ads API enablement for this
        destination (Data Manager is used instead)
    </Accordion>
  </AccordionGroup>
</Card>

## 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

<CardGroup cols={2}>
  <Card title="Setup guide" icon="wrench" href="/guides/CDP/integrations/google-ads-remarketing/setup">
    Configure credentials, OAuth scope, and verify the connection
  </Card>

  <Card title="Google Ads conversions" icon="bullseye" href="/guides/CDP/integrations/google-ads/overview">
    Track purchases and events as Google Ads conversions
  </Card>
</CardGroup>