Connect your first ad platform

Last updated: May 19, 2026

Connect your first ad platform

Open Connect → [platform] in the sidebar, click Connect, complete OAuth on the platform's site, pick which ad accounts to import. Same 3-step pattern for Meta, Google Ads, TikTok, Taboola, and Snapchat.

Who is this for

Anyone who has just finished the onboarding wizard and is ready to bring real ad data into Wevion. Without at least one connected platform, the dashboard is empty.

Before you start

You need three things:

  • An active ad account on the platform you want to connect (e.g. a Meta Business Manager with at least one ad account)

  • Admin or Advertiser permission on that ad account (Wevion needs read + write to launch campaigns)

  • Your browser allowed to open OAuth popups (disable popup blocker for app.wevion.ai)

The common 3-step pattern

All 5 platforms follow the same flow.

Step 1: Open the connector page

In the left sidebar, click Connect, then pick the platform: Meta, Google Ads, TikTok, Taboola, or Snapchat. You land on /connect/{platform}. The page shows what permissions Wevion will request, and a list of any already-connected accounts.

Step 2: Click Connect and complete OAuth

Click the Connect button (top right). A popup opens on the platform's official OAuth site. Sign in with the account that owns the ad accounts. Review the requested scopes and click Allow. The popup closes and returns you to Wevion.

Step 3: Select which ad accounts to import

Wevion fetches the list of ad accounts you have access to and shows them as a checklist. Check the ones you want to manage with Wevion. Click Import selected. Wevion starts a background sync — campaigns, ad sets, ads, creatives, pixels, audiences, and last 90 days of performance data flow in.

The initial sync takes 5-30 minutes depending on account size. You can leave the page and come back. Status shows on each ad account card: Syncing, Synced, Error.

Platform specifics

Platform

OAuth scope highlights

Typical sync time

Meta

Ads management, pages read, business management

10-30 min

Google Ads

AdWords API (read + write); MCC supported

5-20 min

TikTok Ads

Advertiser management, audience management

5-15 min

Taboola

Backstage API access

5-10 min

Snapchat

Ads management

5-10 min

For each platform there's a dedicated deep-dive article — start with Setting up your Meta connection if Meta is your primary, or pick the matching collection for your platform.

Token health and reconnection

Wevion stores an OAuth refresh token for each connected account. Tokens expire on the platform's schedule (Meta: 60 days; Google: never unless revoked; TikTok: 24 hours auto-refresh; Taboola: 60 days; Snapchat: 30 days).

Wevion auto-refreshes tokens silently. If a refresh fails (you changed password, revoked permissions, account suspended), the connector card turns yellow with a Reconnect button. Click it to redo OAuth without losing any data — same flow as the first connection.

What you'll see

After a successful first connection:

  • The connector card shows a green Connected badge and the account count

  • The dashboard at /dashboard populates within 5-15 minutes (KPI strip, spend chart, top campaigns)

  • The Ads Manager at /ads-manager shows your imported campaigns

  • A toast notification: "Imported [N] campaigns from [platform]"

Common issues

  • OAuth popup blocked: enable popups for app.wevion.ai in your browser settings, then retry.

  • "No ad accounts found": you signed in with an account that has no ad account access. Sign in with the account that owns the ads or ask the owner to grant you Advertiser access.

  • Sync stuck on "Syncing" > 1 hour: check the connector card for an error message. Most common: rate limit on the platform side. Wait 1 hour and retry from the card menu.

  • Connected but no data in dashboard: check if the imported accounts have spend in the last 90 days. Empty accounts show no rows.

  • Multiple Meta Business Managers: connect once with the master account that has access to all BMs. If they're under separate users, run the connector twice with different OAuth sessions.

Related