Before you connect

How MarketingLeague uses Google data

Permission is requested in context. Google Ads is the core connection; Search Console is optional and can be granted later from the dashboard.

Required

Google identity and Google Ads

openid, email, and https://www.googleapis.com/auth/adwords

Labels the connected Google identity; lists accessible Ads accounts; reads campaign, conversion, targeting, asset, budget, policy, search-term, and performance data; creates diagnostics, reports, monitoring results, and plans; and supports explicitly approved account changes. Google Ads offers one scope for both read and write API operations, so new connections remain read-only inside MarketingLeague until a user changes that mode.

Optional

Search Console

https://www.googleapis.com/auth/webmasters.readonly

Lists properties and reads search performance, sitemaps, and URL index status for landing-page diagnostics. This is a read-only permission.

Storage, sharing, and control

An encrypted refresh token permits scheduled monitoring and resumable reports while you are away. The token is never shown in reports or the dashboard.
Relevant data can be returned to a user-selected ChatGPT, Claude, Codex, or other agent client only when the user directs a MarketingLeague workflow.
Google data is not sold, used for our own advertising, or used to train generalized AI models.
You can keep the connection read-only, disconnect it, revoke Google access, or request deletion of retained reports and snapshots.

See the complete Privacy Policy and deletion instructions.

How MarketingLeague uses Google data

Google identity and Google Ads

Search Console

Storage, sharing, and control

Continue with the narrowest permission you need