PrestaShop
Check your PrestaShop store's Meta tracking
Paste your store URL to see every Pixel and tag helper in the HTML. PrestaShop tracking is module-driven, and the failure mode is predictable: an abandoned module still firing an old Pixel next to a new one, or a paid module that mirrors the browser and calls it Conversions API.
Real browser. Pro and Team from a workspace. Static scan stays free, no login.
Module archaeology
Years of themes and modules leave duplicate fbq('init') calls with different Pixel IDs. The scanner lists every ID it finds — clean up before you optimize.
Hook-based injection is fragile across updates
Modules inject via displayHeader/displayOrderConfirmation hooks. A theme update that drops a hook silently removes Purchase tracking while the rest of the site looks fine.
Server-side without another module
Caply works from one snippet plus server-delivered money events with hashed customer data — no marketplace module to keep compatible with your PrestaShop version.
PrestaShop tracking questions
- Why does Meta count more sales than PrestaShop orders?
- Duplicate Pixel modules, or browser + server events without a shared event_id. Both are visible in this scan and in Meta Events Manager's deduplication diagnostics.
- Which PrestaShop hook fires on the order confirmation page?
- displayOrderConfirmation. If your Pixel module doesn't register it, Purchase never fires in the browser — one more reason to send it server-side.
- Does Caply need FTP or module installation?
- No. Add the snippet to your theme header (or via a custom-code module) and connect your Pixel token in the Caply dashboard.
After the scan
Send PrestaShop sales from the server. Count each one once.
Caply sends Purchase and Lead from managed servers with hashed customer data, deduplicated against your Pixel by event_id. Pro $29 or Team $99, 14-day trial (card required).
Other platforms: Shopify · WooCommerce · Wix · Squarespace · Webflow · Framer · Full scanner