Connect Google Ads accounts and verify manager account access

Consent, discovery and import

Start from the intended client on Integrations and authorize the Google identity that can access its advertising accounts. A unified connection can request Ads, Analytics and Search Console; the capabilities recorded by AdAce Ads depend on the permissions actually granted. Consent for Analytics alone does not enable Google Ads discovery. If analytics belongs to another Google identity, select that account through the separate analytics connection flow rather than assuming all resources share one login.

Google's directly accessible account list is not a complete manager hierarchy. AdAce Ads also queries client accounts beneath accessible manager accounts and carries the manager context into discovery. Google Ads API access additionally depends on the service's developer access, not only the user's consent. Therefore an empty or partial list needs investigation; signing in successfully does not guarantee that every agency account will appear.

For example, your agency identity may access an MCC containing North Store and South Service. Select North Store's advertising account for the North Store client. Compare the account name, displayed identifier, currency and manager label before importing. A similarly named account or a manager account is not interchangeable with the advertiser you intended. If the account is already assigned to another client, resolve that assignment rather than recreating the brand under a different name.

Account selection links a discovered account to the client; campaign import then reads selected campaign structure. It does not publish or alter advertising. Imported structure and performance collection are separate steps, so verify both a recognizable campaign and a report with an explicit date range. Fresh conversion numbers may still change. A missing report is a collection or access question, not evidence that the account spent nothing.

An account mapping your team can verify

• Use the Google account structure your agency already manages while checking the advertiser and client mapping explicitly.
• Select accounts from the provider list without entering customer IDs, advertising tokens or a shared Google password into AdAce Ads.
• Keep connection status, imported structure and report freshness visible as separate evidence for a reliable handoff to your team.

Connect and compare the result

1. Ask an owner or administrator to open Integrations for the correct client and choose the Google connection. Check that the Ads service is selected.
2. Allow the provider popup and review the identity and permissions on Google's page. Return to Integrations and check the connection result rather than treating a closed popup as success.
3. Open account discovery, review any warnings and select the intended advertiser. Confirm its displayed identifier, currency and manager context against Google Ads.
4. Import a small, recognizable set of campaigns. Check the import count and then open Campaigns to compare names and statuses with the provider.
5. Open Analytics after collection is available. Use the same date range, account currency and reporting context when comparing results; keep preliminary data labelled.

Missing accounts and incomplete connections

Sources and further reading

• Google Ads API: OAuth requirements
• Google Ads API: directly accessible accounts
• AdAce Ads: unified Google sign-in
• AdAce Ads: campaign import