Skip to main content
Use Google Ads Audiences to create and update Customer Match audiences from an approved first-party list. Plan consent, suppression, enrichment, and approval in Paid ads audiences; this page owns the Google-specific contract.

​
Connect and select an account

In the Deepline dashboard, open Integrations → Google Ads Audiences and complete OAuth with the Google account that signs in to Google Ads. Deepline requests only the Data Manager scope (https://www.googleapis.com/auth/datamanager), which cannot list the accounts you can access, so add each account by its customer ID (top right in Google Ads, e.g. 123-456-7890). Deepline verifies access before saving it. Add the manager (MCC) account ID too if you reach the account through one. Then enable the accounts Deepline may use and set a default when appropriate. With more than one enabled account, pass account_id explicitly. For an MCC relationship, pass login_account_id for the manager account.

​
Live actions and schema

Execute these IDs through the shared POST /api/v2/integrations/{toolId}/execute contract. The table lists payload fields. Substitute an Action ID from it into GET /api/v2/integrations/{toolId}/get to inspect the live schema. Each rows entry can carry a supported raw or SHA-256 identifier, such as email, phone, first_name plus last_name, or company/person identifiers. Deepline compiles supported raw identifiers before upload and reports invalid rows separately.

​
Google-specific safeguards

  • Create a list once and store its returned audience ID. Use mode: "replace" for a full refresh and mode: "append" for incremental additions.
  • Make Google consent and terms explicit. terms_of_service_accepted must be true for Customer Match uploads; its default does not substitute for review.
  • Use the live schema to choose membership_life_span_days; do not assume an older duration remains accepted.
  • Set validate_only: true to ask Google to validate a create, sync, or delete request without committing that write. Validate the payload first; confirm price and approval separately.
  • A sync returns request IDs, not proof that Google matched the list. Poll google_ads_audiences_get_audience_status before reporting completion.
  • Deleting an audience is irreversible. Read the ID and target account back before calling the delete action.