Connect & manage Google Ads with Wevion — complete guide

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

Table of contents

• Connect Google Ads account (OAuth)

• Pick ad accounts (MCC + child)

• Permissions + scopes (AdWords API)

• Sync data

• Manage campaigns

• Cross-platform analytics

• Troubleshoot

• FAQ

• Next steps

Connect Google Ads account (OAuth)

/connect/google → Google OAuth consent → grant adwords scope → tokens stored encrypted.

• gog-101 connect Google account — full flow

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 (AdWords API)

Verified scope (per apps/backend/src/lib/google/):

login_customer_id header used for MCC routing (Google Ads API standard).

Refresh tokens auto-handle long-term access. Annual re-auth may be required by some Google account types.

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:

• cc-101 Campaign Creator — Google supported across modes

• am-101 Ads Manager — Google rows visible alongside Meta

• rul-101 Rules Engine — rules act on Google entities (some action types may be limited)

• ch-101 Creative Hub — files reusable across platforms

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:

• an-105 Cross-Channel overview — unified view (behind ENABLE_CROSS_CHANNEL_ANALYTICS flag)

• an-108 channel comparison — side-by-side Meta vs Google

• an-109 budget recommendation — rule-based allocation across platforms

Troubleshoot

• tr-109 token expired — re-auth via /connect/google

• tr-101 common issues hub

Common Google-specific issues:

• MCC routing wrong → check login_customer_id in account settings

• 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

• First-time Google setup: gog-101 connect Google account

• Add Meta alongside: meta-pillar Meta Ads integration

• Cross-platform view: an-105 Cross-Channel overview

• Launch Google campaign: cc-101 Campaign Creator

Related

• gog-101 connect Google account

• meta-pillar complete Meta Ads integration

• an-105 Cross-Channel overview

• tr-109 token expired