Overview

Once you have set up conversion tracking for your web pages, use the Testing Tool to verify that the end-to-end flow is working smoothly.

📘

Conversion types

Use the Testing Tool to verify both event-based and URL-based conversions.

👍

S2S conversion tracking

You can also use the Testing Tool to verify your S2S (server to server) conversion tracking.

Start a test

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

   Alternatively, select your network account.

2. In the sidebar (left), select Tracking.

3. Under Conversions, select the Test Events tab.

4. 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.)

5. 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.

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

Test your events

👍

Guidelines

1. Disable all ad blockers for the page that you are testing.
2. 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.

3. Use a browser that supports third-party cookies, such as Google Chrome, for the most accurate testing results.

   Safari and other privacy-focused browsers often block third-party cookies by default, which may affect user matching.

4. If prompted, make sure to consent to cookies.

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

5. For best results, test on both desktop and mobile.
6. 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:

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

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

3. 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.

4. 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)

---

Example: URL visit (collapsed view)

---

Example: Issue detected (collapsed view)

Expanded details

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

📘

Examples of expanded events are provided below.

Example: page view (expanded view)

A page view event with no issues. The Page URL field indicates the URL visited.

Example: URL visit (expanded view)

A URL-triggered event (contact_us) with no issues. The Conditions field shows the URL pattern that triggered this event.

Example: Issue detected (expanded view)

The lead_contact_us event has several issues. Mouse over the currency and revenue alert icons for more information. This event is also missing a matching conversion - you need to create one in Realize.

Example: User matching (expanded view)

The User Matching section shows a success status with checkmarks for both Taboola Click ID (tblci) and Cookie ID, indicating that user tracking is working correctly.

User matching

Indicates if Taboola can track users for conversion attribution (see screenshot above).

👍

For best results, test with a browser that supports third-party cookies, e.g., Google Chrome.

Safari and other privacy-focused browsers typically block third-party cookies.

User matching status

For each event, the User Matching section shows a status flag:

• Success: All user identifiers are working correctly
• Issues: One or more user identifiers have problems

Click the arrow to expand and see a detailed status for each identifier.

Identifiers

• Taboola Click ID (tblci): Used for conversion tracking, especially in cookieless environments (Safari, iOS).
• Cookie ID: Used for retargeting and maximizing conversion match rates.

Identifier status icons

• ✅ Success: Identifier is present and valid.
• ❌ Alert: Identifier is missing or blocked.

Troubleshooting user matching issues

🚧

Click ID (tblci)

Click ID is essential for conversion tracking in cookieless environments (e.g. Safari, iOS). If you're experiencing problems, consider the following:

• Cross-Domain Tracking: If your funnel involves multiple domains, ensure the Click ID parameter is correctly passed between them.
• Parameter Integrity: Verify that the tblci parameter is not being modified or stripped by your website or any intermediate systems.

🚧

Cookie ID

Cookie ID is vital for effective retargeting and maximizing conversion match rates. If you're experiencing problems, consider the following:

• Browser Settings: Verify that your browser permits third-party cookies and. Chrome typically does, whereas Safari and iOS often block them.
• Cookie Consent: If a cookie banner is present, make sure you have accepted cookies.
• Ad Blockers: Disable any active ad blockers.
• Incognito/Private Mode: These browsing modes often block third-party cookies by default. For accurate testing, use a standard browsing session.

Manage the view

1. 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

1. If the testing tool detects any issues:

   1. The Events Received pane displays a total count of events with issues (top, right) - e.g.:

      1. 

   2. Each event with an issue is tagged with an error icon - e.g.:

      
      

2. To see details of a given issue, expand the relevant event and mouse over the error icon shown - e.g.:

   

3. 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