Module features and benefits
- 9 Facebook Pixel events — PageView, ViewContent, ViewCategory, AddToCart, InitiateCheckout, AddPaymentInfo, Purchase, Search, and CompleteRegistration. Registration depends on event configuration, consents, and supported store paths; it does not mean measuring every action.
- Conversions API (CAPI) and Purchase — In package 1.5.0, Purchase can enter the queue when configuration, paid order status and current cart consent conditions are met. CRON sends it to Meta without requiring the confirmation page; verify actual receipt separately.
- shared event identifier — Purchase from Pixel JS and CAPI shares an event_id intended for deduplication. Correct event receipt and attribution must be verified in Meta
- Advanced Matching — optional data for event matching. For CAPI, the module normalizes and hashes selected customer data with SHA-256; in the browser, it passes the available email, first name, and last name to fbq initialization without hashing them through the module’s PHP code
- 6 product identifier formats — product ID, ID-attribute, ID_attribute, EAN-13/GTIN, reference, MPN/supplier reference — for matching with the Facebook product catalog (Product Catalog)
- product identifier prefix — A configurable prefix such as ps_ can adapt identifiers to your feed. It must pass module validation; check that content_ids match the catalog.
- Paid order statuses — Choose statuses that qualify a Purchase. The code also checks the order status paid flag; selecting an arbitrary status alone does not trigger sending.
- Test Event Code — an optional test code attached to the CAPI request. After meeting the sending requirements, check the result in Meta test tools; entering the code alone does not confirm event receipt.
- tracks product combination changes — supports the ViewContent event after a recognized variant change and reading its data. The content_ids format results from the configuration: with the base product ID, the identifier may remain the same despite a price change. Check the behavior with the theme, consents, and variant export method you use.
- support for dynamic attribute combinations — supports selects, radio buttons, and color swatches in the theme — reading combinations from elements recognized by the module script; a custom theme requires testing
- CAPI readiness panel — Shows missing settings, queue states, the last attempt result and the last CRON run. Local readiness does not prove Meta receipt or attribution.
- 3 configuration tabs with icons — a clear settings division: Facebook Pixel, Conversions API, Advanced
- Send attempt history — CAPI attempt result codes and API acceptance confirmation are recorded in the database independently of debug mode, without customer data or Access Tokens in the attempt history. The browser flag records a queued call, not Meta receipt.
- supported checkout paths — the code recognizes, among others, TheCheckout, SuperCheckout, and OnepageCheckout; event receipt must be verified with the checkout version, theme, and payments you use
- Package selection for the store — Package 1.5.0 declares PrestaShop 1.7.0.0 as its minimum. Confirm a suitable legacy package for PrestaShop 1.6 and compatibility with PHP, theme and checkout separately; a version declaration does not replace store-specific acceptance checks.
- full Polish localization — the entire administrative interface in Polish
- Integration requirements — Pixel and CAPI require active PD Cookie Pro in live mode and verified advertising consent. CAPI also requires recorded cart consent, a Pixel ID, Access Token, selected paid statuses, PHP cURL, HTTPS to Meta and a running CRON job.
- Purchase queue and CRON — A token-protected CRON URL or integration with the cronjobs module processes server-side Purchase and limited retries. This does not guarantee complete measurement or advertising attribution.
Link to the module demo:
Admin panel demo:
https://moduly-prestashop.eu/fb-pixel/admin-dev
Front-end demo:
https://moduly-prestashop.eu/fb-pixel
You can find the license, trial copy, and update terms in §7 of the Store Terms and Conditions.
Check the browser, CAPI, and catalog separately
Matching product identifiers with the Meta catalog is a different issue than event deduplication. The guide to IDs, variants, and Pixel distinguishes both cases and shows a dated in-house test of two cards with explicit limitations.
What should you check before launch?
- Verify the Pixel ID and configured events. For the CAPI path, check the token, order statuses, and consent requirements described above.
- Compare content_ids for a specific variant with the IDs in the catalog; then check the event_id of the same action passed through two channels.
- Check the behavior after refusal and withdrawal of consent. Installing the module does not guarantee registration of every user action.
