Skip to content

Google Ads Integration

Connect a Google Ads customer so Adwize can snapshot campaign structure and apply accepted mutates. This is a tool connector, not the Ads reporting API. We do not call reporting or metrics. fields.

What Adwize can do

  • List accessible customers
  • Snapshot campaigns, ad groups, ads, and conversion actions
  • Mutate structure after you accept the action in Adwize
  • Deliver a consented audience when the selected account is eligible for Customer Match

What Adwize does not do

  • Pull performance reports or spend via the Ads API
  • Publish GTM or change GA4 from this connector

Setup

On the Google Cloud project that owns the OAuth client:

  • Enable Google Ads API
  • Enable Data Manager API when Customer Match delivery is allowed
  • Add https://www.googleapis.com/auth/adwords and https://www.googleapis.com/auth/datamanager to the consent screen
  • Add the Ads callback URI

Connecting GTM first is not enough — Ads uses its own token.

  1. In Adwize, go to Settings > Integrations and open Google Ads.
  2. Click Connect with Google and grant access to Google Ads. If you already connected with only Tag Manager scopes, disconnect and connect again.
  3. Add a developer token from Google Ads API Center. Adwize stores it encrypted on this connection. A server GOOGLE_ADS_DEVELOPER_TOKEN is used automatically when set. A test token can list accounts but cannot snapshot a live Ads customer. Apply for Explorer, Basic, or Standard access, or pick a test account linked to that token.
  4. Load customers from Google and pick the account Adwize should manage.
  5. Refresh the snapshot when you want an updated copy of structure.

When Adwize proposes a mutate, it stays pending until you click Accept. Until then, nothing is written back to Google Ads.

Customer Match audience delivery

New audience uploads use Google's Data Manager API rather than a new Google Ads API upload workflow. The selected Ads account must have good policy/payment history and be eligible for the requested Customer Match use. The audience must contain first-party identifiers with required consent, satisfy Google's current minimum list requirements, and target an explicit customer account.

Adwize validates account eligibility, consent, list size, explicit account/resource ownership and OAuth scope readiness before enabling the executable action. Customer Match delivery is queued through the governed action worker and records every provider request ID. Automated rollback is intentionally unsupported; a recommendation remains advisory when execution requirements are not met. Performance facts still come from the client's warehouse export; connecting Customer Match does not provide reporting data.