User Guides
Send query results to Google Customer Match (GDM)¶
Google Customer Match (GDM) syncs an Amperity audience to a Google Customer Match user list, so you can target those customers across Google Search, Shopping, Gmail, YouTube, and Display. Members are matched to Google users on a hashed email address or phone number, or on a mobile advertising ID. The connector uses Google’s Data Manager platform (GDM).
Note
This destination uses the Google Data Manager API .
Important
Google Customer Match (GDM) updates membership incrementally. Each run sends only the members who joined or left the audience since the last run: new members are added, and members who left are removed individually by name. Members already in the audience are left in place and reported as unchanged. Amperity tracks these membership changes itself, so it never resends the full audience.
Caution
A single identifier is sent per member — the Match identifier you configure applies to every member of the audience. Because that identifier is also how Amperity tracks membership, it cannot be changed without recreating the audience, and match rates are typically lower than a connector that sends several identifiers per person. Per-member consent signals are not sent, so a segment sent to Google Customer Match (GDM) must already exclude anyone who has denied ad personalization or ad user data.
Note
Membership changes are applied in the background and can take from minutes to days to take effect. Amperity reports members as delivered once Google accepts them. A successful orchestration means Google accepted the members, not that they are in the audience yet — confirm the audience member count in the Google Ads interface. Google also reports success for removing a member who was not in the audience, so only the member count in Google can confirm a removal. When Google rejects members within a batch, Amperity reports them as failed rows with Google’s explanation in the run’s error log, and the rest of the batch is still sent.
Caution
Amperity can only update an audience it created. If the configured Audience name matches an audience that was shared into the account from elsewhere, the run fails with an error that names the audience rather than writing to it.
Note
The connected Google account must directly administer the account named in Customer ID. Manager account (MCC) setups, where the login reaches the account indirectly through a manager account, are not supported. Google also refuses membership changes when the account is disabled, or when it has campaigns that are missing the required European Union political advertising declaration; both are resolved in the Google account.
The steps that are required to send audiences to Google Customer Match (GDM) from Amperity.
Caution
This destination is available for sending query results to Google Customer Match (GDM) after it is configured by a Datagrid Operator or your Amperity representative.
If this destination cannot be selected for orchestrations ask your Datagrid Operator or Amperity representative to configure a destination for sending query results to Google Customer Match (GDM).
Build query¶
Build a query that returns the column matching the Match identifier configured on the destination.
The query behind a Send to orchestration is not checked against the connector’s schema before it runs, so a query that returns the wrong column is not caught up front. Make sure the query returns:
Exactly one column, named for the configured Match identifier and spelled exactly as Amperity reads it:
email,phone, ormobile-id. Note thatmobile-idis hyphenated, notmobile_id.No other columns. Any extra column is ignored, not rejected.
That column is also the key Amperity uses to track audience membership, so it must stay fixed: changing the Match identifier after the audience exists means recreating the audience. A query that omits the configured column, or returns a different one, still runs — every member then fails to match, the audience is left unchanged, and the run reports every row as failed with no error raised beforehand.
The following example returns email addresses for a destination whose match identifier is email:
SELECT
email
FROM Customer_360
WHERE email IS NOT NULL
Amperity hashes email and phone values before sending them; do not hash them in the query. A member whose identifier value is missing or cannot be parsed is dropped and reported as a failed row.
Add orchestration¶
An orchestration defines the relationship between query results and a destination, including the destination and the frequency at which an orchestration runs.
Open the Activations page, select the Orchestrations tab, and then click the Add orchestration button. This opens the Add orchestration dialog box.
From the Object type dropdown, select Query.
From the Object dropdown, select the query for which results is sent to Google Customer Match (GDM).
From the Destination dropdown, select a destination that is configured for sending data to Google Customer Match (GDM).
Verify all settings.
Set the workflow to Manual. You can change this to automatic later, after verifying the end-to-end workflow.
Click Save.
Run orchestration¶
Run the orchestration manually to validate that it works.
Open the Activations page, select the Orchestrations tab, and then open the menu for the Google Customer Match (GDM) orchestration. Select Run.
The Status column for the orchestration updates to say “Waiting to start”, after which the notifications pane updates to include a notification that shows the current status.
When the orchestration has run successfully, the status is updated to “Completed”.