How to test my Pixel code?

Check storefront triggering, Meta reception and catalog matching separately. A green Pixel Helper check alone does not validate all three.

Prepare the test

1. Check the Pixel ID and activation. Avoid two integrations sending the same events.
2. Test in a fresh session with consent withheld or refused, then granted. Inspect actual requests and cookies; the module configuration must match your banner's controls.
3. If you use Pixel Helper, open its panel on the page under test and read each event's details and warnings.

Which events should you expect?

• PageView: a page view after tracking is activated.
• ViewContent: a product page. Compare content_ids, price, currency, name and category with the product and feed.
• ViewCategory: a custom event sent only when its option is enabled. Do not expect it when disabled.
• AddToCart: test an actual addition to the cart. Sending it when the cart page loads is a separate setting, disabled by default; opening the cart does not always produce this event.
• Purchase: use a test order with a demonstration payment method. Check amount, currency, items and whether reloading causes duplicate counting.

Check the ViewCategory setting

In the module configuration, go to Facebook Pixel → Advanced options → Emit the custom "ViewCategory" event. This option is enabled by default. Select Yes if you want the module to report category and product-list visits, or No to stop sending this custom event. Save any change and reload the storefront page.

For your test, open a category containing products with tracking activated and the required consent granted. Check that ViewCategory appears when the option is enabled. If it is disabled, its absence is expected; this setting does not disable the Pixel's other events. Also check category pagination if your shop uses it. This option only controls events sent by this module.

Check reception

In Events Manager, select the source's name and ID, open Test events and open the website to test. Follow the official browser event testing instructions. For Conversions API, check server events separately with the temporary test code described in this FAQ.

An entry in a JavaScript variable, a dataLayer, a Pixel queue or a local AJAX request does not prove reception by Meta. Reception does not prove that all products match the catalog either: compare exact IDs, see product IDs.

Understand warnings

Read the affected field and message. Blockers, JavaScript errors, withheld consent, an incorrect ID, invalid data or missing catalog items can have different effects. An unmatched product does not necessarily mean the event was not received. Do not disregard Meta diagnostics because a local test is green. If the Pixel is missing, see troubleshooting.

The illustrations below show examples and navigation landmarks. Names, dates and layouts may differ in your installation; follow the checks described in the text.