Taboola connection troubleshooting

Top 6 Taboola issues — credentials missing, account ID format, sync delays, pixel install, currency. Fixes inline.

Written By Salvatore Sinigaglia

Last updated About 1 hour ago

Top 6 Taboola issues — credentials missing, account ID format, sync delays, pixel install, currency. Fixes inline.

Taboola connection troubleshooting

Top Taboola integration issues with cause + fix. Most Taboola problems trace to: the Client ID / Client Secret you pasted, sync delays, 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. "Invalid Taboola credentials" error

Symptom: pasting your Client ID + Client Secret at /connect/taboola, you get "Invalid Taboola credentials".

Cause: the Client ID / Client Secret didn't validate against Taboola's token endpoint — usually a typo, extra whitespace, or revoked credentials.

Fix:

  • Re-copy the Client ID and Client Secret exactly (no leading/trailing spaces)
  • If they still fail, request fresh API credentials from your Taboola account manager or support@taboola.com
  • Re-paste and connect again

2. Credentials revoked or rotated on Taboola side

Symptom: the connection worked before but now sync fails.

Cause: your Taboola Client ID / Client Secret were rotated or revoked in Taboola.

Fix:

  • Obtain the current Client ID + Client Secret from Taboola
  • Reconnect at /connect/taboola with the new credentials

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: your Taboola Client ID / Client Secret were revoked or rotated on the Taboola side, so Wevion can no longer mint access tokens.

Fix:

  • Obtain the current Client ID + Client Secret from Taboola
  • Reconnect at /connect/taboola
  • If the credentials are valid and it still fails, contact support@wevion.ai

When to contact support

support@wevion.ai for:

  • Issue not in this list
  • Credentials valid on Taboola but the connection still fails
  • Pixel installed but events not tracking after 7 days
  • Data discrepancy > 10% vs your Taboola account

Include:

  • Workspace ID
  • Your Taboola connection name (or Client ID prefix)
  • Approximate timestamp
  • Exact error message

Response: 1-2 business days; priority on Pro/Enterprise.

Useful diagnostics

  • /connect/taboola → connector card → Last sync timestamp + status
  • The workspace audit log (admin only)
  • Taboola Backstage → Reports → cross-reference numbers with Wevion's Ads Manager

FAQ

What does Wevion need to connect Taboola?

Your Taboola API Client ID + Client Secret, obtained from your Taboola account manager or support@taboola.com. You paste them at /connect/taboola; Wevion validates them against Taboola's token endpoint (client_credentials grant) and stores them encrypted. There is no separate "account ID" field or OAuth popup.

Why does Wevion show no Taboola campaigns after connecting?

Usually the 15-minute first-sync delay. Wevion pulls only active and paused campaigns (not archived) from your Taboola account. Wait 15-30 minutes and refresh, and confirm active campaigns exist in your Taboola account.

What causes an "Invalid Taboola credentials" error?

The Client ID / Client Secret you pasted didn't validate against Taboola's token endpoint — typically a typo, extra whitespace, or credentials that were revoked/rotated on the Taboola side. Re-copy them exactly, or request fresh credentials from Taboola, then reconnect at /connect/taboola.

Why is my Taboola pixel showing Inactive in Wevion?

The pixel JS may not be installed, may fire wrong event names, or Taboola simply hasn't marked it Active yet. Copy the snippet from Backstage → Tracking → Tracking Pixels → Implementation, install it before </head>, verify firing with Taboola's pixel debugger, then wait 24-72h for Taboola to recognize it as Active at /pixels.