Guides
Log In
Guides
Start typing to search…

Validation and common issues

DCO Pixel > Validation and common Issues

📍

This section refers to the Taboola DCO solution. For the standard e-commerce solution, see here.

Overview

After implementing the pixel, it is critical to verify that it is firing correctly.

We provide multiple validation methods. Choose the one that works best for your workflow:

  1. Browser DevTools (recommended) - Most reliable method for technical users
  2. Taboola Pixel Helper - Quick browser extension check
  3. Realize dashboard - Verify events are being received (requires dashboard access)
  4. GTM debugging - Preview mode for GTM implementations only
Browser DevTools validation (recommended)

This method provides the most detailed view of pixel behavior and is recommended for thorough validation.

👍

Best for technical users

This method requires familiarity with Chrome DevTools but provides the most comprehensive validation.

Verify the base pixel

  1. Open Chrome DevTools:

    • Mac: Cmd + Option + I
    • Windows: Ctrl + Shift + I

  2. Select the Network tab.

  3. In the Filter field (top left), type taboola:

  4. Browse to your website and reload the page if needed.

  5. Verify that tfa.js is being called:

Verify e-commerce events

  1. With Chrome DevTools still open, select the Network tab.

  2. In the Filter field, type unip?ce=ecomm:

  3. Perform various e-commerce operations on your website (e.g., view a product, add to cart, make a purchase).

  4. For each operation, check that a corresponding network call appears with unip?ce=ecomm:

  5. Click on the entry and select the Headers tab (right panel):

  6. Scroll down to the Query String Parameters section and verify that all event parameters (e.g., ce, en, data) are correct:

  7. If the expected entry is not present, select the Console tab and check for JavaScript errors.

👍

Pro tip: Preserve log

If the page reloads or redirects during testing, check the Preserve log option (top of Network tab) to retain network traffic across page loads.

Taboola Pixel Helper validation

  1. Add the Taboola Pixel Helper extension to your browser from the Chrome Web Store.

  2. Navigate to your website and perform the actions that should trigger the events (e.g., view a product, add to cart, make a purchase).

  3. Click the Taboola Pixel Helper icon in your browser's toolbar.

  4. Verify that the events are firing correctly. Under PRODUCT_VIEW (or the corresponding event), the second line should display ce=ecomm after unip?.

  5. If you see ce=ecomm, the pixel is working correctly:

Realize dashboard validation

This validation method allows you to verify that Taboola is receiving your events. Note that it may take a few hours after publishing for events to appear in the dashboard.

📘

Dashboard access required

This method requires access to the Realize dashboard. Contact your Taboola account manager if you need access.

Verify events are being received

  1. Open the Realize dashboard.

  2. Select your account (top right).

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

  4. Verify that at least the mandatory events (PRODUCT_VIEW, ADD_TO_CART, PURCHASE) show as Active:

  5. Note the Last received status to confirm recent event activity.

📘

Allow up to 1 hour for conversion events to appear in Realize after firing on your website.

GTM debugging

This validation method is only relevant for GTM implementations:

  1. In your GTM workspace, click Preview from the top right.
  2. Open your website in a new tab.
  3. Verify that your Taboola pixel has fired correctly.

Common issues

Wrong Advertiser ID

Ensure that you're using the Advertiser ID supplied by your DCO Account Manager. This is NOT the same as your DCO Seat ID.

Using wrong GTM template

When implementing the pixel, ensure you're using the Taboola E-Commerce Events Tracking Pixel template (not the Taboola Pixel template).

Using 'event' instead of 'ecevent'

When implementing the pixel using JavaScript, only the page_view event should have notify: 'event'. All other events must have notify: 'ecevent'.

Example:

// page_view event (correct)
window._tfa.push({
  notify: 'event',
  name: 'page_view',
  id: ACCOUNT_ID,
  unified_id: hashed_email
});

// PRODUCT_VIEW event (correct)
window._tfa.push({
  id: ACCOUNT_ID,
  notify: 'ecevent',
  name: 'PRODUCT_VIEW',
  unified_id: hashed_email,
  productIds: ['sku1']
});

Changes not published

After creating and verifying tags in GTM, you must submit and publish the changes to apply them to your live environment:

  1. Click Submit.
  2. Click Publish.
  3. Verify that your changes are live.

Product ID mismatch

Ensure that you're sending the correct Product ID, otherwise the system won't be able to recommend the proper items to users.

🚧

Important

The Product ID value must match one of the product identifier columns (e.g., GTIN, SKU, MPN, etc.) in your feed. Product ID values passed for Product View event should be consistently passed across all other events (e.g., Purchase event, Add to Cart event, Category View event, etc.).

Example:

  • ✅ Correct: Product feed ID: PROD123, Pixel event: ['PROD123']
  • ❌ Incorrect: Product feed ID: PROD123, Pixel event: ['prod123'] or ['PROD-123']

Updated 21 days ago