# Meta pixel and Conversions API on PrestaShop

> The Meta pixel alone misses a growing share of visitors because of blockers and browser restrictions. The Conversions API (CAPI) fills that gap by sending events from the server: on PrestaShop, the principle is the same as everywhere else, but the module ecosystem is less standardised.

- Source canonique : [https://allaux.fr/en/services/tracking/pixel-meta-api-conversions-prestashop](https://allaux.fr/en/services/tracking/pixel-meta-api-conversions-prestashop)
- Langue : EN
- Dernière mise à jour : 2026-09-30

## Direct answer

> In Meta Events Manager, under Conversions API, generate an access token dedicated to server-side sending, separate from the browser pixel. On the shop side, look first in Modules > Module Manager to see which module already installs the pixel, so no second copy ends up in a theme template. The same event_id must accompany both the browser and the server call, otherwise Purchase is counted twice.

## What I see most often

- A Meta pixel in place for years, never complemented by the Conversions API
- A tracking module claiming to "do everything", with no clear picture of what it actually sends server-side
- A Meta Events Manager showing duplicate events: one from the browser, one from a badly configured module
- A visible drop in Purchase events reported since iOS 14 restrictions and ad blockers became common
- An access token to generate, with no clear idea where or how

## What I check and configure

1. **Access to Meta Events Manager** — I check access to the Meta Business account and the Events Manager tied to the existing pixel’s data source before touching anything on the shop.
2. **State of the browser pixel** — I check which events the pixel already sends (PageView, AddToCart, Purchase...) and with which parameters, using the Meta Pixel Helper extension.
3. **Generating the server access token** — In Events Manager, under Conversions API, I generate a system access token dedicated to server-side sending, separate from the browser pixel.
4. **Choosing the server-side channel** — Depending on what’s already in place on the shop, I assess the existing tracking module or a dedicated server-side implementation to send the same events as the pixel.
5. **Shared event ID** — I make sure every event sent by the pixel and the server carries the same event_id, so Meta deduplicates the event received twice instead of counting it twice.
6. **Final check** — In the Events Manager’s Test Events / event overview tab, I confirm key events appear with two sources (browser and server) merged into a single deduplicated event.

## A less standardised module ecosystem than elsewhere

On PrestaShop, at the time of writing there’s no official equivalent as tightly integrated as the "Meta for WooCommerce" extension available on WooCommerce. Several third-party modules let you set up a pixel and connect the Conversions API, with very variable levels of maturity and maintenance depending on the vendor.

I stay deliberately generic on this point: the principle (browser pixel + server token + shared event_id) doesn’t change depending on the module chosen, but I always check what the installed module actually does — some only set up the pixel and present the Conversions API as a poorly implemented side feature, others handle both channels correctly with deduplication.

Either way, the final check happens in the same place: Meta Events Manager, not the module’s documentation.

## A module doesn’t replace the check

> A module claiming to handle "pixel and Conversions API" isn’t enough to take at face value. I always verify in Meta Events Manager that both sources appear and that deduplication is working before considering the setup done.

## Related pages

- **The same topic on WooCommerce** — The official Meta for WooCommerce extension enables pixel and Conversions API together, with automatic deduplication. ([/services/tracking/pixel-meta-api-conversions-woocommerce](/services/tracking/pixel-meta-api-conversions-woocommerce))
- **The same topic on Shopify** — Native Meta channel or custom pixels: the constraints shift with Shopify’s checkout changes. ([/services/tracking/pixel-meta-api-conversions-shopify](/services/tracking/pixel-meta-api-conversions-shopify))
- **The ecommerce events that matter** — The same prioritisation logic applies on the GA4 side: a few reliable events beat many approximate ones. ([/services/tracking/evenements-ecommerce-qui-comptent](/services/tracking/evenements-ecommerce-qui-comptent))
- **Duplicate statistics** — A pixel set up twice (theme and module) is a common cause of duplicates. ([/services/tracking/doublons-statistiques-causes](/services/tracking/doublons-statistiques-causes))
- **PrestaShop** — The hub for PrestaShop work: modules, migrations, performance, integrations. ([/prestashop](/prestashop))
- **ChatGPT Ads conversion tracking** — OpenAI pixel, Conversions API, oppref and consent: the same pixel-plus-server logic, applied to ChatGPT ads. ([/services/tracking/suivi-conversions-chatgpt-ads](/services/tracking/suivi-conversions-chatgpt-ads))
- **ChatGPT Ads module for PrestaShop** — Deduplicated OpenAI pixel and Conversions API, oppref kept until the order, consent respected: built and installed by me. ([/prestashop/module-chatgpt-ads](/prestashop/module-chatgpt-ads))

## FAQ

### Isn’t the Meta pixel alone enough?

It used to be, before browser restrictions and ad blockers became widespread. Today, a share of events set up browser-side only never reach Meta; the Conversions API fills that gap from the server.

### Do I need a specific module for the Conversions API on PrestaShop?

There’s no official equivalent as integrated as on WooCommerce at the time of writing. I look at what’s already in place on the shop and assess case by case rather than defaulting to one module.

### What is event_id, in practice?

A unique identifier generated for each event (for example, for every confirmed order), sent by both the pixel and the server for the same event. Meta uses it to recognise it’s the same event received twice, not two separate events.

### How do I know deduplication is actually working?

In Meta Events Manager, the event overview tab shows, for each event, which sources reported it. If browser and server appear merged into a single line, deduplication is working.

### Where do I find the server access token?

In Meta Events Manager, on the pixel’s data source, under Conversions API, a system access token can be generated directly from the interface.