Connect & manage Google Ads with Wevion — complete guide

Google Ads integration: OAuth connect, MCC accounts, AdWords API scope, sync, manage, cross-platform analytics, troubleshoot.

Written By Salvatore Sinigaglia

Last updated About 5 hours ago

Google Ads integration: OAuth connect, MCC accounts, AdWords API scope, sync, manage, cross-platform analytics, troubleshoot.

Connect & manage Google Ads with Wevion — complete guide

TL;DR: Wevion's Google Ads integration uses OAuth with 5 scopes (adwords, content, openid, email, profile). Connect → pick accounts (supports MCC parent + child accounts) → 15-min sync → manage alongside Meta / TikTok / Taboola / Snapchat / Outbrain in cross-platform analytics. Read + write supported; relaunch action is Meta-only.

Table of contents

Connect Google Ads account (OAuth)

/connect/google-ads → Google OAuth consent → grant the 5 scopes → tokens stored encrypted (access + refresh, GOOGLE_TOKEN_ENCRYPTION_KEY).

Pick ad accounts (MCC + child)

Google Ads has two account types:

  • MCC (My Client Center) — parent / management account
  • Child accounts — individual ad-running accounts under MCC

Wevion supports both. Connecting via MCC: gives access to all child accounts in one OAuth flow. Connecting via single child: only that account.

Agency use case: connect via MCC, pick child accounts per client.

Permissions + scopes (Google Ads API)

Verified scopes (per apps/backend/src/providers/google/core/constants.ts, GOOGLE_ADS_SCOPES):

ScopePurpose
https://www.googleapis.com/auth/adwordsFull Google Ads API access (campaigns, ads, performance, reports)
https://www.googleapis.com/auth/contentMerchant Center product data (Shopping)
openidOpenID identity
emailConnecting account email
profileConnecting account basic profile

login-customer-id header used for MCC routing (Google Ads API standard).

These scopes fall into three functional groups — the minimum an ad-management tool needs: manage campaigns (adwords), read product/performance data (content, for Shopping), and identify the account (openid, email, profile). No Gmail, Drive, or Calendar access is requested.

A background job auto-refreshes access tokens due to expire within ~15 minutes; the refresh token itself has no fixed expiry under normal use. During connection you'll pass through Google's standard OAuth consent screen, where you review and grant the scopes listed above before returning to Wevion.

Sync data

Same 15-min cron pattern as Meta. Insights flow into campaign_daily_insight + similar tables.

Google's attribution windows differ from Meta:

  • Default: 30-day click + 1-day view
  • Different from Meta (7-day click + 1-day view)

Cross-platform comparisons account for this in an-105 cross-channel overview.

Manage campaigns

Same Wevion tools as Meta:

Notable difference: relaunch rule action is Meta-only (Google Ads creative-cycle works differently).

Cross-platform analytics

Once you have Google + Meta (or others) connected:

Troubleshoot

Common Google-specific issues:

  • MCC routing wrong → check the login-customer-id header used for the account
  • Conversion tracking gap → verify GTM / pixel setup separately

FAQ

Can I connect multiple Google Ads accounts?

Yes — connect MCC for batch access, OR connect individual accounts via separate OAuth flows.

Do I need a Google Ads developer token?

No — Wevion has its own developer token + verifies your account during OAuth.

Does Wevion support Google Display + Search + YouTube?

Yes — all Google Ads campaign types supported. Specific campaign-creation flows may have variation per type.

How is Google Ads spend converted to my currency?

Per-day FX rates (per-day, not flat). See an-115 exchange rates.

Conversion tracking?

Google Ads tracks conversions natively. Combine with tracker integration (Keitaro / Voluum / etc.) for unified postback view across platforms.

GA4 integration?

Wevion doesn't directly integrate with GA4 as a data source. Use a tracker bridge if you need GA4 → Wevion attribution.

Next steps