How do I add Meta Pixel tracking events to PrestaShop?

The Meta (Facebook) Pixel tracks shopper actions so you can measure ad performance and build retargeting audiences. PrestaShop has no native Pixel, so you add it with a tracking module. With Facebook Pixel, enter your Pixel ID and enable browser tracking; the module then fires the standard ecommerce events – PageView, ViewContent, AddToCart, InitiateCheckout, Search, AddToWishlist, CompleteRegistration and Purchase – with individual switches so you can turn specific events on or off. For accurate conversions despite browser and ad-blocker loss, also enable the server-side Conversions API, which sends Purchase events to Meta with a matching event ID so browser and server hits are de-duplicated. Verify everything in Meta's Events Manager test tool before launching campaigns, and make sure Pixel firing respects your cookie-consent banner so tracking only runs after marketing consent is given.

The module installs with ENABLED off and an empty PIXEL_ID, so no browser tracking starts until you configure it. Pixel IDs are validated as digits only. Most standard event switches default to on once the module itself is enabled, while CAPI_ENABLED defaults to off and requires a Pixel ID plus CAPI_ACCESS_TOKEN. The default Graph API version in the module is v25.0, and an optional test event code can be sent while validating in Meta Events Manager.

Consent is checked before rendering the tracking template. If Cookies Revolution is active, the module reads the marketing value from mprcr_consent; if Lightweight Cookie Banner is active, it reads mprcookie_consent; if neither is active and consent-respect is enabled, the module treats marketing consent as available. Employee browsing can also be excluded. AddToCart is tracked through the PrestaShop updateCart event when available, with click fallbacks for older themes. Purchase is emitted on order confirmation with a deterministic order event id, and when CAPI is configured the same purchase is queued and processed through the shared conversion queue, including a cron task scheduled every 300 seconds for retry/processing.