How ADS Beast uses Google Ads OAuth

Requested scope

ADS Beast requests https://www.googleapis.com/auth/adwords to connect the user’s Google Ads accounts through Google OAuth.

Why access is needed

• list accessible Google Ads customer accounts after user consent;
• read account, campaign, customer, and conversion metadata for reporting, readiness, and audit workflows;
• create or update Google Ads campaigns only through operator workflows, checks, and approval gates.

OAuth workflow

• the user signs in to ADS Beast and opens Connections;
• the user selects Google Ads API and starts Google sign-in;
• Google shows the consent screen with Google Ads access;
• after consent, Google redirects to https://adsbeast.pro/api/auth/google/callback;
• ADS Beast stores the token server-side and lists accessible Google Ads accounts without exposing secrets.

Where access is used

• /connections - OAuth start and Google Ads account selection;
• /system/token-health - Google OAuth/API access status and reviewer evidence;
• /campaigns/google-launcher - prepare, validate, and launch Google Ads campaigns through a guarded workflow.

Demo video

Recorded production OAuth workflow and Google Ads functionality: https://adsbeast.pro/oauth-google-ads-demo.webm

Data and deletion

OAuth tokens are stored server-side and are not displayed to users. Users can revoke access in Google Account → Security → Third-party access or request deletion through ADS Beast Data Deletion.