Debug Taboola in Chrome DevTools

What Taboola traffic looks like

Taboola runs two workloads that look similar on the wire: the publisher recommendation widget and the advertiser conversion pixel.

Endpoint pattern

Widget loader from cdn.taboola.com (typically libtrc/<publisher-id>/loader.js) talking to trc.taboola.com to fetch and log recommendations; the advertiser pixel reuses the same loader but reports conversions and page views through trc.taboola.com and trc-events.taboola.com; nr.taboola.com handles user-sync and notifications; api.taboola.com serves the JSON recommendation API on publisher pages

Transport

Script load plus beacon requests: widget logging and conversion reporting share the trc hosts

Data layer object

_tfa.push({ notify: 'event', name: 'page_view', id: ... }) drives the pixel. id is the Taboola account ID, name is page_view or a custom conversion name like lead or purchase

Key parameters

event name in en or name · account ID in the URL path or id · page URL on each beacon

Cookies

t_gid carries Taboola's user identity and shows up on every beacon, useful when tracing whether a user is recognized across pages

Debugging Taboola with Event Watcher

• Matches all of these hosts and names each request as Taboola with its ad-tech category badge.
• No dedicated Taboola parser. You work from the raw request view: parsed query and body parameters, cookies set and sent (including t_gid), and the consent verdict per event.
• Script Tree shows whether the loader came from the site's own code, GTM, or another third-party script.
• Grouped view by Endpoint separates trc.taboola.com widget logging from trc-events.taboola.com conversion traffic.

Taboola and consent

Event Watcher checks Taboola against marketing consent. The publisher trap: sites treat the widget as "content" and load it unconditionally, so every trc.taboola.com request lands pre-consent. It is still a marketing platform setting a cross-site ID, so the extension flags it.

On the advertiser side the pixel is usually behind a GTM marketing trigger: deny marketing, reload, confirm no trc-events beacons fire. Widget traffic is a common source of pre-consent findings in a full pixel audit.

Common debugging scenarios

• Conversions not matching in Taboola Ads. Find the conversion beacon and check the event name against the conversion rule configured in Taboola. A typo'd custom event name silently reports zero.
• Widget fires before consent. Filter to Taboola with the consent filter on only violations; if trc.taboola.com requests carry the pre-consent badge, the loader is outside the CMP's control.
• Duplicate page_view events. Grouped by Event Name shows whether two scripts push _tfa events; Script Tree identifies both initiators.
• Is the user being ID'd? Inspect the Cookies section on any Taboola event for t_gid and whether it was sent, set, or both.
• Publisher and advertiser tags on the same page. Group by Endpoint to keep widget logging separate from conversion beacons before drawing conclusions.