Connect Taboola

Taboola integration uses OAuth2 client_credentials grant — Wevion holds the TABOOLA_CLIENT_ID + TABOOLA_CLIENT_SECRET server-side (verified in apps/backend/src/services/taboola-auth.service.ts). You provide your Taboola Backstage account ID at /connect/taboola and grant Wevion access via Taboola Backstage UI (separate from OAuth). Sync imports campaigns + pixels.

Who is this for

Mediabuyers running native ads on Taboola's content-discovery network — premium publisher sites like Bloomberg, MSN, USA Today, where your ad blends in as a content recommendation.

How Taboola's auth differs from Meta/Google/TikTok

The other 3 platforms use user-facing OAuth flows (you authenticate via your own Meta/Google/TikTok account). Taboola is different:

• Uses client_credentials OAuth2 grant (server-to-server, no user OAuth)

• Wevion holds credentials at the platform level (TABOOLA_CLIENT_ID + TABOOLA_CLIENT_SECRET env vars)

• You provide your Backstage account ID in Wevion

• You grant Wevion access inside Taboola Backstage (separate UI step)

So the connect flow is shorter on the Wevion side, but requires additional configuration in Taboola Backstage.

Before you start

• A Taboola Backstage account (advertiser account on Taboola) — sign up at backstage.taboola.com

• Your Backstage account ID (visible in Backstage URL or Account Settings)

• Account in Active status (not pending review)

• Wevion role: manager, admin, owner, super_admin

How to connect

Step 1: Open the connector page

In the sidebar click Connect → Taboola or visit /connect/taboola. The page asks for your Taboola Backstage account ID.

Step 2: Enter your Backstage account ID

Format: numeric ID (e.g. 1234567). Find at:

• Taboola Backstage → top-right account menu → Account ID

• OR the URL: backstage.taboola.com/dashboard/?act=NNNNNNN

Step 3: Grant Wevion access in Taboola Backstage

This is the step that authorizes Wevion to access your account:

1. Taboola Backstage → Account Settings → API Access

2. Add Wevion's API client (your account manager at Taboola will provide the credentials, or use the form to request)

3. Wait for Taboola's confirmation (usually < 24h)

Step 4: Click Connect in Wevion

Click Connect. Wevion uses its server-side credentials to authenticate against Taboola's API on behalf of your account. Validates the account ID is reachable.

Step 5: First sync

15-min sync starts. Pulls campaigns, ad groups, ads, sites, pixels, last 90 days insights. Typical duration: 5-10 min.

What you'll see when it works

• Connector card: green Connected badge

• Account ID shown

• Dashboard populates with Taboola data

• Ads Manager shows imported Taboola campaigns

• Toast: "Imported N campaigns from Taboola"

Taboola pixel setup

Taboola has a tracking pixel (the Taboola Pixel) for conversion tracking:

1. Backstage → Tracking → Tracking Pixels → Create Pixel

2. Define conversions (Purchase, Lead, etc.)

3. Install pixel JS on your site (via GTM or manual)

4. Wevion picks up the pixel on next sync (taboola_pixel model)

Pixel events flow back to Taboola → optimize Sales/Lead campaigns.

Currency

Each Backstage account has its own currency, set at signup, not changeable. Cross-channel rollups in Wevion convert via daily FX rates to workspace currency (same as Meta/Google/TikTok).

Differences from social ads (Meta/TikTok)

See tbl-102 for picking the right objective.

Multiple Backstage accounts

If your agency manages multiple Taboola accounts, connect each in Wevion with its own account ID. Each appears as a separate connector card.

Token model

Server-side OAuth2 client_credentials:

• Access token issued by Taboola on demand

• Token cached by Wevion (~1 hour validity per Taboola)

• Auto-refreshed by Wevion as needed

• No user-side reconnect required under normal use

• Failure (Wevion credentials rotated): contact support — server-side issue, not user-fixable

Common issues

• "TABOOLA_CLIENT_ID not configured" error: Wevion's server-side credentials not set up (or rotated and not updated). Contact support@wevion.ai immediately — affects all customers, urgent.

• Account ID rejected: wrong format. Should be numeric only (no act_ prefix like Meta).

• No campaigns visible after connect: 15-min sync delay. Verify campaigns exist in Backstage.

• "Unauthorized" from Taboola API: server-side credentials issue OR Wevion not yet granted access in your Backstage (Step 3 above).

• Pixel events not tracked: Taboola pixel JS not installed on site. Install via Backstage instructions.

Wevion's Taboola provider

Verified vs codebase:

• apps/backend/src/services/taboola-auth.service.ts handles client_credentials flow

• apps/backend/src/providers/taboola/core/constants.ts holds TABOOLA_TOKEN_URL

• apps/backend/src/services/taboola-pixel.service.ts syncs pixels

• Models: taboola_token, taboola_ad_account, taboola_pixel

Related

• Taboola objectives and pricing — picking the right campaign type

• Taboola connection troubleshooting — issue list

• Connect your first ad platform — generic intro