Overview

Use the Testing Tool to verify that your Taboola pixel conversion tracking is working smoothly.

🚧
The Testing Tool does not support S2S (server to server) conversion tracking.

Start a test

Open Realize, and select the account (top, left) that you are using to track conversions.

Alternatively, select your network account.
In the sidebar (left), select Tracking.
Under Conversions, select the Test Events tab.
Enter the URL of the page that you want to test, and click on Generate QR Code.

The URL must be a page that contains your Taboola pixel.

🚧
Enter the URL exactly as it appears in your ad (including any tracking params). This will mimic real-world conditions.

(In some cases, if the URL redirects to another domain, you may need to enter the destination URL.)
Test your site on mobile or desktop:
1. To test on mobile, scan the QR Code with your phone.
2. To test on desktop, click on the link provided. (Your site will open in a new browser tab.)
  👍
  Tip: For best results, test on both desktop and mobile.

Browse your site, making sure to move through the various stages of your conversion funnel, as described below.

Test your events

👍
Guidelines

Disable all ad blockers for the page that you are testing.

Enter the URL exactly as it appears in your ad (including any tracking params).

In some cases, if the URL redirects to another domain, you may need to enter the destination URL.

If prompted, make sure to consent to cookies.

Note that Safari's strict privacy settings may block third party cookies.

For best results, test on both desktop and mobile.

Make sure that all expected events are received and that no errors are shown. *

* If no events appear - and the above steps are not effective - try testing with our Chrome extension. This will indicate if the event is fired at all.

Testing flow

Once you have started the test (previous section), it's time to verify that the expected events are received:

Browse your site, making sure to move through the various stages of your conversion funnel.
Make sure that all expected events are received and that no errors are shown.
As each event is triggered, it will appear in the Events Received pane (right):

If any events have issues, an error icon displays in the pane header (top, right) - and alongside each event with an issue.

🚧
If no events are shown, refer to the Testing Guidelines above. If the above steps are not effective, try testing with our Chrome extension. This will indicate if the event is fired at all.
To view event details (including error details) click on the arrow to expand.

📘
Examples of different events are provided in the sections that follow.

Example events

The following examples illustrate different events. Each example is followed by a short table, with an explanation of the information provided.

Example: page view (collapsed view)

Element	Description
	Triggered by an `Event` .
`Automatically Fired`	This event is handled automatically .
`Event: page_view`	Event is called `page_view`
`June 29, 2025 at 11:17:19 AM`	A timestamp when the event occurred
`Issue icon` (not present)	There were no validation errors or issues

Example: URL visit (collapsed view)

Element	Description
	Triggered by a `URL` visit.
`Event: contact_us`	Event is called `contact_us`
`June 30, 2025 at 04:40:40 PM`	A timestamp when the event occurred
`Issue icon` (not present)	There were no validation errors or issues

Example: Issue detected (collapsed view)

Element	Description
	Triggered by an `Event` .
`Undefined conversion`	No conversion was found for this event.
`Event: lead_contact_us`	Event is called `lead_contact_us`
`June 30, 2025 at 04:40:37 AM`	A timestamp when the event occurred
	An issue occurred. (Expand the event for more detail.)

Expanded details

To view event details, click on the arrow to expand. The following fields are available:

📘
Examples of expanded events are provided below.

Element	Description
`Account ID`	The Taboola Account ID referenced in the pixel. Typically, this matches the currently selected account in Realize (or a subaccount under your network account).
`Type`	Possible values: `Event` - triggered by an event `URL` - triggered by a URL visit
`Event name`	The event name - e.g. `page_view`
`Page URL`	The URL of the page that triggered this event.
`Parameters`	This field is shown only if the event passes additional parameters - e.g. `value` and `currency`.
`Condition`	This field is shown for a `URL visit` event only. It is the condition that triggers the event. E.g `"."`- every page triggers this event.
`Contents`	The specific data passed for this event. This data is used for technical troubleshooting - you can typically ignore it.

Example: page view (expanded view)

Example: URL visit (expanded view)

Example: Issue detected (expanded view)

Manage the view

To temporarily clear the Events Received pane, click on Clear Activity (top, right).

As new events are received, the pane will start to fill up again.

Check for issues

If the testing tool detects any issues:
1. The Events Received pane displays a total count of events with issues (top, right) - e.g.:
2. Each event with an issue is tagged with an error icon - e.g.:
To see details of a given issue, expand the relevant event and mouse over the error icon shown - e.g.:
Examples:
1. Unmatched conversion: The event received does not have a matching conversion in Realize.
2. Parameter errors: Additional parameters in the event have issues. E.g.
  1. Incorrect format for currency
  2. Invalid amount for value