PrestaShop Meta Pixel Conversions API tracking connects your store to Meta Ads with browser events and optional server-side purchase delivery. It helps store owners and agencies see whether Facebook and Instagram traffic becomes product views, carts, checkouts, registrations or orders, so ad decisions are based on store actions instead of page visits alone.
The module tracks PageView, ViewContent, AddToCart, InitiateCheckout, Search, saved-item intent, CompleteRegistration and Purchase events, with switches for each event and extra rules based on clicks, page URLs, page types or storefront actions. When Conversions API is configured, purchase events can also be sent from the store and matched with browser events, helping Meta count each sale once.
Tracking requires a numeric Pixel ID and can respect supported consent signals, exclude employee sessions, show setup warnings and keep configuration visible in the Back Office.
- Pixel ID and tracking check. Tracking requires the module to be enabled and a numeric Pixel ID to be configured. Storefront tracking also respects the module's consent and employee-exclusion decisions before sending events.
- Built-in commerce events. The module can send PageView, ViewContent, AddToCart, InitiateCheckout, Search, saved-item intent, CompleteRegistration, and Purchase events. Configuration stores toggles for the optional events so merchants can decide which configurable signals to use.
- Consent-aware loading. The module can follow consent choices from supported cookie modules when respect-consent is enabled. If no supported consent module is present, tracking follows the module's default behavior instead of creating a separate consent system.
- Employee exclusion. A setting prevents tracking when an employee is logged into the shop. That helps keep staff testing and Back Office browsing out of Meta event data.
- Custom event rules. Custom rules can trigger from clicks, page URLs, page types, or storefront actions, and reserved standard event names are blocked during setup. This lets merchants add extra signals without overwriting core Meta event names.
- Server-side sale sending. When enabled and configured, each sale can pass through Meta's server connection with test-mode support and matching identifiers so Meta counts it once.
Meta Pixel and Conversions API for PrestaShop
This PrestaShop Meta Pixel Conversions API module connects your store to Meta Ads with browser pixel events and optional store-side purchase delivery. Merchants pay heavily for Facebook and Instagram ads, and that spend is wasted when Meta cannot see which clicks became product views, carts, checkouts or orders. The module sends the shopping events Meta needs, pairs browser and store-side events so each sale is counted once, and gives you controls for consent, staff exclusion, custom events and diagnostics.
Spend ad budget with better measurement
Ad reporting is dangerous when purchases are missing or counted incorrectly, because the store may keep funding campaigns that do not earn their spend. Meta campaigns need product IDs, prices, currency and purchase values to judge which shoppers and products are worth targeting. This module tracks PageView, product views, add-to-cart, saved-item intent, checkout starts, purchases and registrations so ad decisions are tied to real store actions rather than incomplete browser signals.
Help reduce missed conversions
Browser tracking can be blocked by iOS restrictions, ad blockers and other privacy controls, which means some real orders may be missing from ad reporting. When those conversions are missing, merchants misjudge return on ad spend and may cut campaigns or products that were actually working. With the Conversions API enabled, purchases can also be sent from the store and matched to browser events by shared event IDs, helping reduce missed conversions without double-counting the same sale.
Keep control over what gets tracked
Too much uncontrolled tracking creates messy reports and privacy risk, while too little tracking leaves paid media without the data it needs. The module lets you configure the Pixel ID, Meta connection key, event switches, custom storefront events, marketing-consent gating and employee exclusion from one PrestaShop settings area. That saves time for merchants and freelancers because tracking changes do not require editing theme files or hunting through several snippets.
Deduplicated purchase events with consent controls
The module is built for stores that want Meta tracking handled inside PrestaShop rather than pasted into a theme footer. It includes browser events, optional store-side Conversions API support, event matching, readiness warnings and a diagnostic monitor, which are useful when ad spend depends on trustworthy conversion data. It requires no coding, can respect marketing consent, can leave employee sessions out of tracking, and keeps configuration visible in the Back Office.
-
Referencemprfacebookpixel
-
In stock2147483647 Items
-
PrestaShop CompatibilityPS 1.6 – 9.x
-
Pricing ModelOne-time Purchase
-
Module TypeFront-office
-
GDPR RelevantYes
-
Business GoalMarketing & Retargeting
-
External Account NeededYes
-
Module ComplexityLightweight Widget
-
Customer Journey StageAttract Visitors
-
Works With PlatformMeta / Facebook
What customers say about us
Be the first to share your experience with this module.
Write a Review
Meta Pixel for PrestaShop sends ecommerce tracking data from your store to Meta, so Facebook and Instagram ads can learn from real shopper activity. It tracks key browser events and can also send completed purchases through Meta Conversions API for better purchase reporting.
- AddedAdd Facebook custom event telemetry
- AddedUse shared conversions package
- AddedMake facebook pixel monitor resizable
Works Well With Facebook Pixel
Modules our team genuinely pairs with this one — and exactly why each belongs in the same setup.
Facebook Pixel connects your store to Meta Ads with browser events and optional server-side purchase delivery, so you can judge Facebook and Instagram traffic by store actions. That covers Meta attribution, but not the broader, platform-neutral ecommerce reporting you need to understand overall performance.
Google Analytics GA4 covers that, sending product views, cart activity, checkout starts, purchases, searches and account creation built from PrestaShop actions, with a validated Measurement ID. It complements the pixel: one focuses on Meta ad attribution, the other on general ecommerce analytics, each its own setup.
Together you can attribute Meta campaigns and still see the whole funnel independently of any single ad platform. The pixel reports actions back to Meta while GA4 gives you a platform-neutral view of how shoppers move toward purchase, so paid-social decisions and overall performance analysis each have a tool suited to them.
Facebook Pixel handles Meta tracking specifically, with its own browser events and optional Conversions API delivery. Stores usually run several other tags too, and keeping each as a separate theme snippet gets harder to maintain as the marketing stack expands.
Google Tag Manager helps organise the rest, adding your GTM container and feeding it ecommerce shopping events from real behaviour so tags work with product views, cart changes and purchases. Importantly, GTM does not run or migrate the Facebook Pixel from a shared container; the pixel stays in its own dedicated module while GTM manages its own tag ecosystem.
Used together, your Meta tracking remains in a purpose-built module while GTM tidies the other tags with shared ecommerce events. You get reliable, focused pixel measurement and a cleaner home for everything else, with each tool doing its own job rather than one trying to control the other.
Facebook Pixel tells you whether Meta traffic becomes product views, carts, checkouts and orders, which is strong attribution but says nothing about why visitors who do not convert drop off along the way.
Hotjar covers that behavioural gap, connecting recordings and heatmaps with real shopping context so you can study friction on product pages, checkout steps, forms and calls to action instead of guessing from revenue. It complements the pixel: one measures conversion and attribution, the other reveals on-page behaviour, each set up separately.
Together you get both attribution and explanation. The pixel shows which Meta campaigns drive actions while Hotjar shows where shoppers hesitate on the pages those campaigns lead to, so you can connect a weak conversion rate to an actual friction point and address it, with each tool answering a different question about the same visitors.
Facebook Pixel fires browser events and can send server-side purchase data to Meta, which is precisely the kind of marketing tracking that needs a clear consent basis in many regions. Running it without a consent layer leaves a compliance gap.
Cookies Revolution covers that, collecting and enforcing shopper choices for necessary, functional, analytics and marketing cookies. It blocks matching external and inline scripts before consent, reactivates allowed ones once it is granted, and records each decision. It complements the pixel by managing the consent framework around tracking, a separate job from the tracking itself.
Together you can run Meta tracking within a managed consent setup. The pixel handles attribution while Cookies Revolution records choices and holds matching scripts until consent is given, reactivating them afterwards, so your marketing tracking operates on a clearer consent footing, each tool owning its own responsibility.
Easy return - no questions asked
Install, set up and take profit
Priority Help & Satisfaction Over Sales