Overview

If you hit obstacles with the other testing methods, use Chrome DevTools for more advanced troubleshooting.

📘

Conversion types

Use this flow to verify event-based conversions (which use event pixels) on your web pages.

👍

This flow is suitable for more technical users.

The Network tab

Verify the base pixel

To verify that the base pixel is making a network call:

1. Browse to the relevant page in your conversion funnel.

2. Open Chrome DevTools.

   Cmd + Option + I (Mac)

   Ctrl + Shift + I (Windows)

3. In the DevTools panel, select the Network tab:

   

4. Type "tfa.js" in the Filter box. Then reload the page to capture all traffic:

   (Cmd + R or F5)

5. Verify that tfa.js is present, and select it:

   In the Headers panel (right), note the account-specific Request URL.

6. If you followed the steps successfully, the base pixel is working. You can now verify in Realize.

Verify event pixels

1. Browse to the relevant page in your conversion funnel.

2. Open Chrome DevTools.

   Cmd + Option + I (Mac)

   Ctrl + Shift + I (Windows)

3. In the DevTools panel, select the Network tab:

   

4. Type unip? in the Filter box. Then reload the page to capture all traffic:

   (Cmd + R or F5)

4. If necessary, perform the relevant on-page actions to trigger the event.
5. Under the Network tab, look for a unip? entry with an en param and the name of your event.

   In the above example, the event name is product_view_http.

👍

Pro tip: Preserve log

Occasionally, the the page you are testing may reload or redirect before you are able to observe the network traffic. In that case, check the Preserve log option (top), before testing.

With this option enabled, the Network tab will store a record of traffic accross all pages visited. If the log gets cluttered, click on the Clear network log icon (top, left) to clear the list.

📘

The en (event name) param

Note that the en (event name) param might appear later in the string.

For example, if your event name is complete_registration, look for an entry similar to the following:

unip?en=complete_registration...

unip?...&en=complete_registration...

---

You can ignore other unip? entries - these are used internally by Taboola.

(For example, en=pre_d_eng_tb is an engagement event, fired by Taboola.)

6. If you followed the steps successfully, your event pixel is working. You can now verify in Realize.