Taboola connection troubleshooting
Last updated: May 19, 2026
Taboola connection troubleshooting
Top 6 Taboola integration issues with cause + fix. Most Taboola problems trace to: server-side credentials (Wevion-managed), Backstage account ID format, or pixel installation on your site.
Who is this for
Mediabuyers hitting a Taboola issue. Most fixes are quick once you know what to look for.
1. "TABOOLA_CLIENT_ID not configured" error
Symptom: trying to connect, error mentions missing TABOOLA_CLIENT_ID or TABOOLA_CLIENT_SECRET.
Cause: Wevion's server-side Taboola credentials not set up (or rotated and not refreshed). This is a Wevion-side issue, not user-fixable.
Fix:
Contact
support@wevion.aiimmediately — this affects ALL Wevion customers using TaboolaTag the ticket as urgent — Taboola sync down for everyone until fixed
This is unusual; under normal operation Wevion's credentials are always valid. Reach support fast if you see it.
2. Account ID rejected — "Invalid format"
Symptom: entering your Taboola Backstage account ID at /connect/taboola, get format error.
Cause: wrong format. Taboola uses numeric account IDs only (no prefix like Meta's act_, no dashes like Google's 123-456-7890).
Fix:
Find your account ID in Taboola Backstage → top-right menu → Account ID
OR look at the URL:
backstage.taboola.com/dashboard/?act=NNNNNNN— copy the number afteract=Paste only the number into Wevion (e.g.
1234567, notact_1234567)
3. No campaigns visible after connect
Symptom: connect succeeds, but Ads Manager / Dashboard shows no Taboola data.
Cause:
15-min sync delay (first sync after connecting)
No active campaigns in your Backstage account (sync only pulls active+paused, not archived)
Account in Pending status on Taboola side
Fix:
Wait 15-30 min after connecting; refresh
Verify campaigns exist in Backstage at backstage.taboola.com
Check account status in Backstage Account Settings — must be Active
4. Pixel events not tracked
Symptom: Taboola pixel set up in Backstage, but /pixels shows the pixel as Inactive or 0 events.
Cause:
Pixel JS not installed on your site
Pixel installed but firing wrong events (wrong event names)
24-72h needed for Taboola to mark pixel Active after first events
Fix:
Backstage → Tracking → Tracking Pixels → click your pixel → Implementation → copy the snippet
Install on your site before
</head>(similar to Meta/TikTok pixels)Use Taboola's pixel debugger (browser DevTools) to verify firing
Wait 24-72h for Taboola to recognize the pixel as Active
5. Currency reported in wrong code
Symptom: Wevion shows Taboola spend in USD but you set up your Backstage account in EUR.
Cause: account currency is set at Backstage account creation and immutable. Wevion reads what Backstage reports.
Fix:
Verify Backstage account currency at Account Settings
If wrong: create a new Backstage account in the correct currency, archive the old, reconnect in Wevion
If matches Backstage but Wevion shows different: cross-channel rollup uses workspace currency (FX-converted). Per-account view should be native — refresh the cache.
6. Sync failed with "Unauthorized"
Symptom: sync fails repeatedly with 401 Unauthorized errors.
Cause:
Wevion's server-side credentials rotated (similar to issue #1)
OR: your Backstage account hasn't granted Wevion API access (Step 3 of connect)
Fix:
Verify Wevion is added to your Backstage API access list (Backstage → Account Settings → API Access)
If yes and still failing: server-side issue — contact
support@wevion.ai
When to contact support
support@wevion.ai for:
Issue not in this list
Server-side credentials issues (Taboola-wide)
Pixel installed but events not tracking after 7 days
Data discrepancy > 10% vs Taboola Backstage
Include:
Workspace ID
Backstage account ID
Approximate timestamp
Exact error message
Response: 1-2 business days; priority on Pro/Enterprise.
Useful diagnostics
/connect/taboola→ connector card → Last sync timestamp + statusAudit log filter:
action: taboola_sync_failed(admin only)Taboola Backstage → Reports → cross-reference numbers with Wevion's Ads Manager
Related
Connect Taboola — setup
Taboola objectives and pricing — picking the right campaign type
Meta connection troubleshooting — similar issue patterns across platforms