Customer service and order packaging on your phone 馃摝

- Integrating Meta with PrestaShop Without Losing Data
- Facebook Conversion API for PrestaShop
- Integrating a Facebook Fan Page with a PrestaShop Store
- Place a Facebook box anywhere
- Facebook Reviews in PrestaShop
- Facebook Pixel and Conversion API in a single module
- XML FEED - Facebook Sales Manager
- Technical Requirements



Module configuration and connection to Facebook

What is the Conversion API?
Remarketing is effective only when the advertising system can track user behavior as accurately as possible
Our module supports the collection of events that help you retarget people interested in your offer.
The Facebook Conversion API (CAPI) is a solution from Meta that replaces the pixel and provides a seamless connection to Meta’s advertising and analytics tools.
CAPI tracks traffic and events on the server side, allowing it to monitor traffic more accurately and pass it on to advertising tools more effectively.
⚠️
Facebook CAPI requires PHP version 7.2 or higher.
A box with information about your Facebook fan page in your PrestaShop store.
- Anywhere using {Smart-Tags} or a side panel that slides out from the side of the page
- A link to a subpage in your store featuring Facebook reviews
- You can customize the appearance in the module settings.
The reviews of our services above are verified and come from PrestaShow customers. If you’d like to learn more about how we process reviews, please review our Terms of Service.
- In the module, you can configure the connection between your PrestaShop store and Facebook using the classic Facebook Pixel.
- You can track and analyze all events supported by the Facebook Pixel using the Meta Pixel Helper plugin for the Chrome browser.
An XML file is currently (2026) the best way to transfer product information from your PrestaShop store to Facebook Sales Manager.
PrestaShop Feeder is a module for exporting data from PrestaShop to XML feeds compatible with Meta, Google, and many others.
Technical Requirements
The module requires PHP 7.2 or higher.
### Fixed
* Browser Purchase no longer fires for unpaid orders - payment gateways that create the order before the payment (e.g. newer Przelewy24) could trigger premature Purchase events on the confirmation page
* Conversions API events are no longer sent for crawler/bot traffic, which diluted fbc/e-mail coverage on ViewContent and triggered Meta's "client IP shared by many users" diagnostic
## v1.13.81 - 2026-07-07
### Fixed
* `external_id` coverage on upper-funnel events (ViewContent/ViewCategory): visitors without a cart now also get a stable pseudonymous id
## v1.13.80 - 2026-07-04
### Fixed
* CAPI events sent by cron now carry the time the event actually happened, improving attribution
* `fbclid` is sanitized before building `fbc`, so malformed landing URLs no longer produce an unmatchable `fbc`
* More reliable browser/server event deduplication and cleaner user data on events sent by cron
### Added
* `content_type: product` on Purchase for product-catalog matching (dynamic ads)
## v1.13.79 - 2026-07-03
### Fixed
* `external_id` is now sent on (almost) every event, not only for logged-in customers
## v1.13.78 - 2026-07-02
### Added
* Browser Meta Pixel now also sends customer-matching data (advanced matching) for logged-in customers when `SEND_PERSONAL_DATA` is enabled
### Fixed
* email/country normalisation before hashing (email lower-cased + trimmed, country lower-cased 2-letter ISO) for both Pixel and CAPI, matching Meta's advanced-matching spec
## v1.13.77 - 2026-07-01
### Fixed
* Low/declining `fbp` and `fbc` coverage on Purchase for orders paid via a redirect gateway (Przelewy24/PayU/BLIK/Autopay)
## v1.13.76 - 2026-07-01
### Fixed
* Stop sending empty customer-matching parameters (email/phone/birthday/first name/last name/city/zip/country) on events where the data is unknown (e.g. anonymous PageView/ViewCategory).
## v1.13.75 - 2026-06-27
### Fixed
* Purchase events sometimes still had an empty `fbp` for orders finalised outside a normal browser session (express checkouts, customers who never return to the order-confirmation page, back-office / API orders). The order snapshot now guarantees a non-empty `fbp`: live `_fbp` cookie - most recent `fbp` captured for the same customer in an earlier session - as a last resort a freshly generated server-side `fbp` (allowed by Meta). This pushes `fbp` coverage on Purchase to ~100%.
## v1.13.74 - 2026-06-26
### Fixed
* Module packaging no longer aborts: removed an accidentally committed build artifact
## v1.13.73 - 2026-06-26
### Fixed
* Minimum PHP requirement is now 7.2 (required by the bundled Facebook Business SDK), fixing module packaging
## v1.13.72 - 2026-06-26
### Changed
* Move Facebook Business SDK (Guzzle, Monolog, PSR) from sdk/vendor/ into main composer.json, eliminating global namespace conflicts with other modules
* Remove legacy Facebook SDK manual require from Model/Module.php (now loaded via Composer autoloader)
### Fixed
* Currency codes are now always sent uppercase to Meta CAPI (e.g. PLN instead of pln) — applied via composer-patches on facebook/php-business-sdk 14.0.0; regression test added
* Add vendor-prefixed/autoload.php stub and spl_autoload_register fallback in config.php to fix "Attempted to load class IndexController" on module install
## v1.13.71 - 2026-06-26
### Changed
* Hardened `fbc` resolution on server-side (CAPI) events: fresh `_fbc` cookie first, then the `?fbclid=` URL fallback instead of reading the cookie only, so every code path that builds an event benefits from the fbclid fallback consistently
## v1.13.70 - 2026-06-20
### Fixed
* Low `fbp` coverage on server-side (CAPI) events, especially on entry pages (ViewCategory / ViewContent): the first page view had no `_fbp` yet (the Pixel sets it later, client-side). The module now generates a first-party `_fbp` cookie on the first visit, so server-side events carry it and the Pixel reuses the same value.
## v1.13.69 - 2026-06-19
### Fixed
* Missing `fbp` (and gateway/shared IP) on Purchase events for orders finalised server-side. With redirect payment gateways (Przelewy24/PayU/BLIK/Autopay) the order is often created/validated in a server-to-server callback where the `_fbp` cookie is absent and the request IP belongs to the gateway, so the Purchase snapshot saved an empty `fbp` and the gateway's IP. The module now captures `fbp`/`fbc`/IP/user-agent per cart during the customer's browser session and reuses those values for the Purchase snapshot, giving `fbp` the same resilience that `fbc` already had via its fbclid fallback.
## v1.13.68 - 2026-06-14
### Fixed
* The problem with the Meta Pixel failing to initialise (and therefore not setting the _fbp/_fbc cookies) when the visitor's user agent contained malformed UTF-8
* The problem with fbp/fbc leaking between events when sending via CRON (one visitor's Facebook IDs could be attributed to another visitor's event because the cookies were not cleared between queued events)
## v1.13.67 - 2026-06-12
### Fixed
* The problem with missing event source URL in Purchase events sent to the Conversions API via CRON (Facebook diagnostics reported "Send the missing event source URL for at least one event")
## v1.13.66 - 2026-06-10
### Fixed
* The problem with missing fbc parameter in events for returning visitors caused by an overly strict 30-day freshness window (now matches Meta's 90-day _fbc cookie lifetime)
## v1.13.65 - 2026-06-08
### Fixed
* The problem with a fatal error (Illegal offset type) in Conversions API CRON events caused by passing an array to `setExternalId()` instead of a scalar string
## v1.13.64 - 2026-06-03
### Fixed
* The problem with missing `contents` parameter in InitiateCheckout events sent via Conversions API
* The problem with incorrect event source URL in AddToCart events sent via Conversions API (cart URL was sent instead of product URL)
* The problem with `content_category` being incorrectly included in ViewCms events sent via Meta Pixel
* The problem with `content_ids` and `contents` being incorrectly included in Search events sent via Meta Pixel
* The problem with InitiateCheckout events being sent when the cart is empty
* The problem with missing user data in Lead (CompleteRegistration) events sent via Conversions API
* The problem with empty PageView events being sent on AJAX requests and pages with no controller context
* The problem with client IP address being shared across multiple users in Conversions API events (server IP was sent instead of the real client IP due to incorrect hashing)
* The problem with duplicate email addresses reported in Facebook Pixel diagnostics (raw unhashed email in sendLead/sendContact was overwriting the correctly hashed value set by setUserPersonalData)
## v1.13.63 - 2026-05-27
### Fixed
* The problem with missing fbp, fbc and client IP in Purchase events sent to Facebook
* The problem with incorrect event source type in Conversions API events
* The problem with incorrect phone number parameter in customer data sent to Facebook
* The problem with incorrect customer address data in Purchase events sent via CRON
## v1.13.62 - 2026-05-18
### Added
* fbc fallback: when _fbc cookie is missing or stale, build it from the fbclid URL parameter per Meta's Conversions API spec (fb.1.{ms}.{fbclid})
* Persist _fbc cookie for 90 days on landing pages that carry fbclid, matching Meta's recommended cookie lifetime
* Send external_id (sha256-hashed customer or cart ID) with Conversions API events to improve event match quality and deduplication
### Changed
* FacebookEvent::isFreshFbc now delegates to FbcResolver (single source of truth for freshness check)
## v1.13.61 - 2026-05-18
### Changed
* Improved detection of client IP sent to Facebook Conversion API.
## v1.13.60 - 2026-05-14
### Fixed
* Event deduplication between Meta Pixel and Conversions API (event_id now matches)
* The problem with outdated fbclid value of fbc parameter
* The problem with ViewContent events being sent incorrectly
* The problem with sending Pageview events via JavaScript despite disabling sending events via JavaScript in the module
## v1.13.59 - 2026-04-20
### Fixed
* The problem with the fbc variable in orders
## v1.13.58 - 2026-04-08
### Fixed
* The compatibility problem with prestashop 8.2
## v1.13.57 - 2026-04-07
### Fixed
* The problem with send events via conversion api
## v1.13.56 - 2026-04-02
### Fixed
* The problem with currency
## v1.13.55 - 2026-03-28
### Fixed
* The problem with send PageView event via conversion api
## v1.13.54 - 2026-03-26
### Fixed
* The problem with currency and price in Purchase event
* The problem with PageView event
## v1.13.53 - 2026-03-07
### Fixed
* The compatibility problem with prestashop 1.6
## v1.13.52 - 2026-03-03
### Fixed
* The compatibility problem with the latest fb pixel requirements
## v1.13.51 - 2026-02-26
### Fixed
* The problem with PageView event content
* The problem with missing category in ViewContent event
## v1.13.50 - 2026-01-30
### Fixed
* Compatibility
## v1.13.49 - 2026-01-27
### Fixed
* The problem with module update
## v1.13.48 - 2025-12-19
### Fixed
* The problem with invalid user ip in events
## v1.13.47 - 2025-12-12
### Fixed
* The problem with user data sent by Pixel Meta
## v1.13.46 - 2025-11-25
### Fixed
* The problem with client IPs sent to FB Pixel
## v1.13.45 - 2025-11-18
### Fixed
* The problem with curriences
* The problem with PageView event without parameters
## v1.13.44 - 2025-11-10
### Fixed
* The problem with duplicate class
## v1.13.43 - 2025-10-30
### Fixed
* The problem with capitalization of currency names in orders sent via conversion API
## v1.13.42 - 2025-10-17
### Fixed
* The problem with send events and orders to conversion API in multistore
## v1.13.41 - 2025-09-04
### Fixed
* Compatibility issue with Facebook SDK when using multiple modules
## v1.13.40 - 2025-08-05
### Fixed
* The problem with missing category in "add to cart" event sent via js code
* The problem with the difference in the capitalization of letters in currencies in events sent to FB Pixel
## v1.13.39 - 2025-07-30
### Fixed
* The problem with matching products in Facebook Pixel by product ID
## v1.13.38 - 2025-03-25
### Fixed
* The problem with event name "ViewCms"
## v1.13.37 - 2025-02-18
### Changed
* The optimization of collecting fb pixel events
## v1.13.36 - 2025-01-30
### Fixed
* The compatibility problem with php 8.1+
## v1.13.35 - 2024-11-06
### Fixed
* The problem with unused hook
## v1.13.34 - 2024-10-29
### Fixed
* The problem with cart page in prestashop 8.1
## v1.13.33 - 2024-10-25
### Fixed
* The problem with send PageView event on product page
## v1.13.32 - 2024-10-16
### Fixed
* The problem with disabling fb pixel
## v1.13.31 - 2024-10-11
### Added
* The ability to choose statuses that orders must have to be sent to fb pixel
## v1.13.30 - 2024-09-20
### Fixed
* The problem with send some events on product page
## v1.13.29 - 2024-09-04
### Fixed
* The problem with send add to cart event to fb pixel
## v1.13.28 - 2024-05-31
### Fixed
* The problem with missing ViewContent event on product page
* The problem with too many decimal in the order amount in the Purchase event
* The problem with missing variables in the Purchase event
## v1.13.27 - 2024-05-21
### Added
* The information about the most recently run cron job
### Fixed
- The compatibility problem with prestashop 1.7.5.2 and lower
## v1.13.26 - 2024-05-21
### Fixed
* The problem with date in events sent to Facebook Pixel
## v1.13.25 - 2024-05-20
### Fixed
* The problem with create the fbp variable in the cookie in the firefox browser
## v1.13.24 - 2024-02-21
### Fixed
* The problem with duplicate addtocart events
* The problem with missing fbp and fbc variables in cookies
## v1.13.23 - 2024-02-14
### Fixed
* The problem with send correct order value
## v1.13.22 - 2024-02-06
### Added
* The ability to send events simultaneously using javascript and conversion API
## v1.13.21 - 2024-01-29
### Fixed
* The compatibility problem with prestashop 1.6
## v1.13.20 - 2024-01-27
### Fixed
* The problem with display logs after sending events to fb pixel using cron
## v1.13.19 - 2024-01-27
### Fixed
* The problem with sending events to fb pixel
## v1.13.18 - 2024-01-25
### Fixed
* The problem with translations in the module
## v1.13.17 - 2024-01-18
### Changed
* The format of sent ip address to fb pixel from ipv4 to ipv6
## v1.13.16 - 2024-01-11
### Fixed
* The problem with duplicate pageview events
## v1.13.15 - 2023-12-19
### Fixed
* The problem with sending some events to fb pixel
## v1.13.14 - 2023-12-18
### Fixed
* The problem with too long variables
## v1.13.13 - 2023-12-15
### Fixed
* The compatibility problem with older versions of prestashop
## v1.13.12 - 2023-12-13
### Fixed
* The problem with logs when sending events to fb pixel
## v1.13.11 - 2023-12-09
### Added
* The support for more events, and more parameters added to events
## v1.13.10 - 2023-11-23
### Fixed
* The problem with sending the pageview event via browser pixel
## v1.13.9 - 2023-11-03
### Fixed
* The problem with cron job in prestashop 8.1
## v1.13.8 - 2023-10-11
### Added
* The ability to send all events via browser pixel
## v1.13.7 - 2023-08-28
### Fixed
* The problem with sending orders to fb on prestashop 1.6
## v1.13.6 - 2023-08-12
### Fixed
* The problem with undefined function on category page
## v1.13.5 - 2023-08-10
### Fixed
* The problem with products without a default category
## v1.13.4 - 2023-07-26
### Fixed
* The problem with duplicate class name
## v1.13.3 - 2023-07-21
### Added
- Set default option send events by CRON
## v1.13.2 - 2023-06-06
### Fixed
* The problem with token in urls from module
## v1.13.1 - 2023-05-29
### Fixed
* The problem with sending orders to fb pixel when the customer's email has an incorrect structure
## v1.13.0 - 2023-05-19
### Fixed
* The problem with missing fbp and fbc variables in orders sent to fb pixel
### Added
- Add support for Prestashop 8.0 and PHP 8.1
- Add support for themes with installed elementor module
## v1.12.0 - 2023-03-25
### NEW
* Improvements to Facebook API connection
* Better conversion and traffic sources tracking
## v1.11.12 - 2023-03-24
### Fixed
* The problem with sending events to fb pixel
## v1.11.11 - 2023-03-13
### Fixed
* The problem with module installation
* The problem with missing ip address in orders sent to fb pixel
### Added
* The ability to enable/disable sending information about the customer's ip address to fb pixel with orders
## v1.11.10 - 2023-03-01
### Fixed
* The problem with missing content id variable in content view event
## v1.11.9 - 2023-02-09
### Fixed
* The problem with missing fbp variable in cookies
* The problem with downloading all necessary variables to fb pixel when the display reviews function is enabled
## v1.11.8 - 2023-01-27
### Fixed
* The problem with sending page view event using cron
## v1.11.7 - 2023-01-23
### Added
* The ability to send events only using cron
## v1.11.6 - 2022-12-07
### Fixed
* The problem with events ids
## v1.11.5 - 2022-11-24
### Fixed
* The problem with sending events to fb pixel
## v1.11.4 - 2022-11-17
### Fixed
* The problem with adding products to the cart after configuring reviews
## v1.11.3 - 2022-11-09
### Fixed
* The problem with missing "event id" value in events
## v1.11.2 - 2022-08-19
### Fixed
* The problem with performance in sending events to fb pixel
## v1.11.1 - 2022-07-07
### Added
- Send personal customer data with 'purchase' event
## v1.11.0 - 2022-06-21
### Fixed
* The problem adding a product with an invalid category id to the cart.
### Added
* added ViewContent event
v1.10.0 - 23/07/2021
* improved server side event sending
* fixed reported bugs
v1.9.0 - 30/06/2021
* send events using conversion api (backend) to facebook
v1.8.0 - 14/06/2021
* fixed problems with conversions
v1.7.0 - 05/06/2021
* fb pixel support added
v1.6.0 - 05/08/2019
* fixed problems with download and display reviews from facebook
v1.5.0 - 23/05/2019
* the name of the module has been changed
* module settings have been expanded with additional functions
v1.4.0 - 09/02/2019
* adaptation of the module for the new feedback from facebook
v1.03.0 - 27/09/2018
* bug fixes
* new features
* new layout
v1.1 - 23/08/2018
*added compatibility with prestashop 1.7+
v1.0.0
* manage categories and entries
* assign category/entry to any hook from PrestaShop
* call module from tpl files and CMS pages
Technical requirements
Technical Requirements
- PHP 7.1 - 8.x
- Server extension ionCube Loader
- PrestaShop Importer only: PHP libxml version > 2.9.3
- PrestaShop Facebook Integrator only: PHP 7.2 or higher
- PrestaShop VAT Validator only: PHP SOAP
Support = Updates + HelpDesk
You get 90 days (3 months) access to the complete PrestaShow support package.
Module updates
Modules will inform you about available updates. Read the changelog and perform a 1-click module update directly from your store.
HelpDesk panel
This is the panel where we will provide you with help. On HelpDesk you can report problems, order free module installation and updates, and order modifications and custom programming work.
Extend support
After support expires, you can use the module without any restrictions. You can extend your support access at any time you need it.
Knowledge Base & FAQ
Free forever
The knowledge base is available to everyone. You will find module documentation as well as instructions, videos and answers to frequently asked questions.
Lifetime license for the module
- You can use the module without limitation in 1 store = 1 domain.
- You can use an additional domain, e.g. for developer copy.
- For a small fee you can change the domain for the module yourself.
Additional domains for Multistore
- All our modules support PrestaShop Multistore.
- Supporting unlimited domains for PrestaShop Multistore requires purchasing multistore support for the module.
Modifying the code
- The module code related to the integration with the store and the design (.tpl, .css, .js) has open source code and you can modify it freely.
- The module's source code (.php) is encrypted with ionCube, and modifying it will void the warranty.
Demo
Demo - test the module
- This module does not have a demo store
No entries yet.











i bada ruch server side?