Overview
Back to topThe Meta Pixel (Facebook Pixel) is a piece of JavaScript code for your website that enables you to measure, optimize, and build audiences for your ad campaigns. Using the Meta Pixel (Facebook Pixel), you can leverage the actions people take on your website across devices to inform more effective Facebook advertising campaigns.
The Meta Conversions API (Facebook Conversions API / Facebook Server-Side API) for web allows advertisers to send web events from their servers directly to Meta (Facebook). Server-side events are linked to a pixel and are processed like browser pixel events. This means that server-side events are used in measurement, reporting, and optimization in the same way as browser pixel events.
Apptrian's Meta Pixel (Facebook Pixel) and Conversions API extension for Magento adds Meta Pixel (Facebook Pixel) with Dynamic Ads code on CMS pages (including the home page), category pages, product pages, catalog search pages, catalog advanced search pages, customer registration page, checkout page (default Magento one but also any other without any coding, only by typing page handle (full action name) into our extension config.), and checkout success page. The extension supports Advanced Matching (if the customer is logged in) and has the ability to add custom parameters.
Optionally Meta Pixel (Facebook Pixel) block can be added to any other Magento page or any other extension page (blogs, form pages, etc.) via our extension config by typing page handle (full action name). The Meta Pixel (Facebook Pixel) allows you to place a single pixel on your entire website to report conversions, build audiences, and get rich insights into how people use your website.
Conversion measurement lets you track actions people take after viewing your Meta (Facebook) Ads across multiple devices, including mobile phones, tablets, and desktop computers. By creating a Meta Pixel (Facebook Pixel) and adding it to the pages of your website where conversions happen, like the checkout page, you will see who converts as a result of your Meta (Facebook) Ads. The pixel will continue to monitor the actions people take after clicking on your ad. You can see which device they saw the ad on and which device they ultimately converted on.
Account & Pricing
To use this extension, a free Meta Business Suite (Facebook Business Suite) account is required.
NOTE: Meta (Facebook) advertising service is not free; additional charges apply to users running Meta (Facebook) Ad Campaigns.
Features
Meta Pixel (Facebook Pixel)
- An easy way to enable or disable Meta Pixel (Facebook Pixel).
- Advanced Matching (if the customer is logged in).
- Works out of the box just type your Pixel ID (or comma-separated IDs for multipixel setups) in our extension config.
- Option to type page handles (full action names) where you want Meta Pixel (Facebook Pixel). Using this option Meta Pixel (Facebook Pixel) can be added to any other Magento page or any other extension page (blogs, form pages, etc.).
- Option to enable or disable the Meta Pixel (Facebook Pixel) base code.
- Option to enable or disable the Meta Pixel (Facebook Pixel) noscript tag.
- Individual options to enable or disable AddToCart, AddToWishlist, CompleteRegistration, InitiateCheckout, PageView, Purchase, Search, and ViewContent events.
- Option to fire PageView event with other events: CompleteRegistration, InitiateCheckout, Purchase, Search, and ViewContent.
- Option to move parameters outside contents.
- Options to detect selected SKUs for all product types including bundle, configurable, and grouped products. WARNING! *
* WARNING! Meta Pixel (Facebook Pixel) client-side detection of selected SKUs feature is heavily dependent on the theme you are using and its customization. It is impossible to predict all possible themes and customizations. Because of this detection will not work on every theme. This is why extension default configuration comes with this feature turned off. You can turn it on and try it out. If it is working for you leave it on otherwise, turn it off. If you are a developer you will be pleased to know that everything is conveniently located in code.phtml file. To make it work, in some cases only the adjustment of a few jQuery selectors is needed in others complete rewrite of the detection code is needed. Because of this, we do not give any warranty for the detection feature, nor it is covered by our support service.
Unlike Meta Pixel (Facebook Pixel) client-side detection, the Meta (Facebook) Server-Side detection is not dependent on the theme you are using and its customization. Therefore if you want to use detection, we recommend you server-side detection and events.
Meta Conversions API (Facebook Conversions API / Facebook Server-Side API)
- An easy way to enable or disable Meta Conversions API (Facebook Conversions API / Facebook Server-Side API).
- Advanced Matching (if the customer is logged in).
- Option to type your Meta Access Token (Facebook Access Token) in our extension config.
- Option to type your Meta API Version (Facebook API Version) in our extension config.
- Option to type your Test Event Code in our extension config.
- Option to log server-side fired events in the Magento log file.
- Individual options to enable or disable AddToCart, AddToWishlist, CompleteRegistration, InitiateCheckout, PageView, Purchase, Search, and ViewContent events. * Notice
- Option to fire PageView event with other events: CompleteRegistration, InitiateCheckout, Purchase, Search, and ViewContent.
- Option to move parameters outside contents.
- Options to detect selected SKUs for all product types including bundle, configurable, and grouped products.
* Notice Since version 4.4.0 you can send both the Meta Pixel (Facebook Pixel) event and Meta Conversions API (Facebook Conversions API) event simultaneously. The server-side events are not visible in the Meta Pixel Helper (Facebook Pixel Helper) extension for Chrome. You can see server-side events in your Meta Business Suite (Facebook Business Suite).
Category Page
- Option to type page handles (full action names) where you want category-related code.
- Option to type the event name you want to use for category tracking.
- Options to add custom parameters to your category-related event with parameters to attributes mapping. Example: google_product_category=google_product_category|name=name. The format is simple param1=attribute1|param2=attribute2 Meta Pixel (Facebook Pixel) custom parameter and Magento category attribute are connected by = sign and pairs are separated by | sign.
AddToCart, AddToWishlist, ViewContent Events
- Option to type page handles (full action names) where you want product-related code.
- Option to select SKU you want to use for bundle products. Options: Product SKU as (id), Children SKUs as (id)s, Children SKUs as (id)s and Product SKU as (item_group_id)
- Option for content_type to use product_group instead of product for bundle products.
- Option to select SKU you want to use for configurable products. Options: Product SKU as (id), Child SKU as (id), Child SKU as (id) and Product SKU as (item_group_id)
- Option for content_type to use product_group instead of product for configurable products.
- Option to select SKU you want to use for downloadable products. Options: Product SKU as (id), Product SKU as (id) and Parent SKU as (item_group_id)
- Option to select SKU you want to use for grouped products. Options: Product SKU as (id), Children SKUs as (id)s, Children SKUs as (id)s and Product SKU as (item_group_id)
- Option for content_type to use product_group instead of product for grouped products.
- Option to select SKU you want to use for simple products. Options: Product SKU as (id), Product SKU as (id) and Parent SKU as (item_group_id)
- Option to select SKU you want to use for virtual products. Options: Product SKU as (id), Product SKU as (id) and Parent SKU as (item_group_id)
- Option to use content_ids instead of contents for the ViewContent event.
- Option to type the Magento product attribute code you want to use for the global content_name parameter.
- Option to type the Magento product attribute code you want to use for the global content_category parameter.
- Options to add custom parameters to your product-related events with parameters to attributes mapping. Example: google_product_category=google_product_category|color=color. The format is simple param1=attribute1|param2=attribute2 Meta Pixel (Facebook Pixel) custom parameter and Magento product attribute are connected by = sign and pairs are separated by | sign.
Checkout Page - InitiateCheckout Event
- Option to type page handles (full action names) where you want quote-related code.
- Option to select SKU you want to use for bundle products. Options: Product SKU as (id), Children SKUs as (id)s, Children SKUs as (id)s and Product SKU as (item_group_id)
- Option to select SKU you want to use for configurable products. Options: Product SKU as (id), Child SKU as (id), Child SKU as (id) and Product SKU as (item_group_id)
- Option to select SKU you want to use for downloadable products. Options: Product SKU as (id), Product SKU as (id) and Parent SKU as (item_group_id)
- Option to select SKU you want to use for grouped products. Options: Children SKUs as (id)s, Children SKUs as (id)s and Product SKU as (item_group_id)
- Option to select SKU you want to use for simple products. Options: Product SKU as (id), Product SKU as (id) and Parent SKU as (item_group_id)
- Option to select SKU you want to use for virtual products. Options: Product SKU as (id), Product SKU as (id) and Parent SKU as (item_group_id)
- Option to type parameter name if you want to use Magento quote ID.
- Options to add custom parameters to your quote-related event with parameters to attributes mapping. Example: google_product_category=google_product_category|color=color. The format is simple param1=attribute1|param2=attribute2 Meta Pixel (Facebook Pixel) custom parameter and Magento product attribute are connected by = sign and pairs are separated by | sign.
Checkout Success Page - Purchase Event
- Option to type page handles (full action names) where you want order-related code.
- Option to select SKU you want to use for bundle products. Options: Product SKU as (id), Children SKUs as (id)s, Children SKUs as (id)s and Product SKU as (item_group_id)
- Option to select SKU you want to use for configurable products. Options: Product SKU as (id), Child SKU as (id), Child SKU as (id) and Product SKU as (item_group_id)
- Option to select SKU you want to use for downloadable products. Options: Product SKU as (id), Product SKU as (id) and Parent SKU as (item_group_id)
- Option to select SKU you want to use for grouped products. Options: Children SKUs as (id)s, Children SKUs as (id)s and Product SKU as (item_group_id)
- Option to select SKU you want to use for simple products. Options: Product SKU as (id), Product SKU as (id) and Parent SKU as (item_group_id)
- Option to select SKU you want to use for virtual products. Options: Product SKU as (id), Product SKU as (id) and Parent SKU as (item_group_id)
- Option to type parameter name if you want to use Magento order ID.
- Option to type parameter name if you want to use Magento order increment ID.
- Option to type parameter name if you want to use Magento quote ID.
- Options to add custom parameters to your order-related event with parameters to attributes mapping. Example: google_product_category=google_product_category|color=color. The format is simple param1=attribute1|param2=attribute2 Meta Pixel (Facebook Pixel) custom parameter and Magento product attribute are connected by = sign and pairs are separated by | sign.
Search Result Page - Search Event
- Option to type page handles (full action names) where you want search-related code.
- Option to type the event name you want to use for search tracking.
- Option to type the parameter name you want to use for search tracking.
- Option to type request parameters you want to include for search tracking.
Data Processing Options
- An easy way to enable or disable Data Processing Options.
- Option to type Data Processing Options as a comma-separated list.
- Option to type Data Processing Options Country
- Option to type Data Processing Options State
Miscellaneous
- Option to select Meta (Facebook) product identifier. Magento product SKU (Recommended) or Magento product ID.
- Option for Advanced Matching data mapping. Example: external_id=external_id|em=em|ph=ph. The format is simple param1=key1|param2=key2 Meta (Facebook) parameter and data key are connected by = sign and pairs are separated by | sign. Available customer data keys are: em, ph, fn, ln, ge, db, ct, st, zp, country, external_id.
- Options to connect default Magento "Cookie Restriction Mode" cookie or any third-party cookie consent extension or theme customization via following options: Enable Cookie Consent, Consent Cookie Name, Consent Cookie Key, Consent Cookie Value, and Consent Button.
FAQ
Q: How do I get Meta Access Token (Facebook Access Token)?
A: There are two ways of getting your Access Token:
- Via Events Manager (Recommended)
- Using Your Own App
To get Access Token via Events Manager (Recommended), go to Meta Business Suite (Facebook Business Suite) and Events Manager. Choose the pixel you want to implement. Select the Settings tab. Find the Conversions API section and click on Create Access Token under Set up manually, and follow the instructions pop up. Once you have your token (save it to your computer because you will not be able to see it again). The Events Manager gives you access to a new tab called Implementation. Navigate to the Implementation tab and follow the instructions displayed on the screen. This way, Meta (Facebook) automatically creates a Conversions API App and Conversions API System User for you. There is no need to go through the app review or request any permissions.
Q: Meta Conversions API (Facebook Conversions API / Facebook Server-Side API) does not work?
A: Meta (Facebook) deprecated v6.0 of the Server-Side API. Go to our extension config and for the Meta API Version (Facebook API Version) option type v16.0 or newer, then refresh your Magento cache (System > Cache Management) and you are done.
Q: In Facebook Event Manager, there are errors "(X) Event Missing Deduplication Parameter"?
A: This error is caused by using other Meta Pixel (Facebook Pixel) solutions in parallel with ours. You need to remove all other implementations of Meta Pixel (Facebook Pixel) and use only our extension. That means:
- Remove all other extensions that fire Meta Pixel (Facebook Pixel).
- Remove all theme customizations that fire Meta Pixel (Facebook Pixel).
- If you are using GTM (Google Tag Manager), make sure it is not firing Meta Pixel (Facebook Pixel) events.
- If you have set "Event Triggers" in the "Event Setup Tool", you need to remove them all and then disable the "Track Events Automatically Without Code" option.
Q: Why am I getting "Server Sending Invalid Match Key Parameters for X event" in the Meta Business Manager?
A: If you get a "Server Sending Invalid Match Key Parameters" warning in your Business Manager, this is due to the use by some of your customers of a cookie blocker like "AdBlock". Some data (IP, state, country, etc.) are then incorrectly formatted according to Facebook guidelines. These are only warnings and can be ignored.
Q: Is it possible to add the Meta Pixel (Facebook Pixel) to other Magento pages or extension pages?
A: Yes it is. In our extension, config just uses the option "Add Meta Pixel (Facebook Pixel) To" and type your page handle (full action name). For example, if you want to add Meta Pixel (Facebook Pixel) to a blog page and that blog page handle is "blog_post_view", you would type this into "Add Meta Pixel (Facebook Pixel) To" at the end. Page handle depends on a particular extension this is just an example. Do not forget to Refresh your Magento Cache.
Q: When I check my product pages with the "Meta Pixel Helper (Facebook Pixel Helper)" extension for Chrome the AddToCart and AddToWishlist events have orange triangles with warnings?
A: The "Meta Pixel Helper (Facebook Pixel Helper)" extension for Chrome does not understand JavaScript/jQuery that is why on page load you have orange triangles for AddToCart and AddToWishlist events. If you read the warnings of the "Meta Pixel Helper (Facebook Pixel Helper)" there is an explanation: "We detected event code but the pixel has not activated for this event, so no information was sent to Facebook. This could be due to an error in the code, but could also occur if the pixel fires on a dynamic event such as a button click." AddToCart and AddToWishlist are dynamic events triggered by a button click. After you click a button they will become green. This has nothing to do with our extension nor Meta Pixel (Facebook Pixel), it is the behavior of the "Meta Pixel Helper (Facebook Pixel Helper)" extension for Chrome. In short, this is normal.
Q: When I check my pages with the "Meta Pixel Helper (Facebook Pixel Helper)" extension for Chrome there is a "grant" event with an orange triangle and warning?
A: The "grant" event is part of Meta's General Data Protection Regulation where sending events and data is paused until consent is given by the customer/visitor. The "Meta Pixel Helper (Facebook Pixel Helper)" extension for Chrome does not understand JavaScript/jQuery which is why on page load you have an orange triangle. If you read the warning of the "Meta Pixel Helper (Facebook Pixel Helper)" there is an explanation: "We detected event code but the pixel has not activated for this event, so no information was sent to Meta (Facebook). This could be due to an error in the code, but could also occur if the pixel fires on a dynamic event such as a button click." The "grant" is a dynamic event triggered by Javascript code that checks for customer/visitor consent. This has nothing to do with our extension nor Meta Pixel (Facebook Pixel), it is the behavior of the "Meta Pixel Helper (Facebook Pixel Helper)" extension for Chrome. In short, this is normal.
Q: Why is the Advanced Matching score low?
A: Some events like PageView or ViewContent have a very low score because anyone can access CMS, Category, and Product pages. On the other hand, the Purchase event has a high score because the customer is logged in, or if it is a guest customer, the data is read from the order billing/shipping address. In short, this is normal. 1. If a customer is not logged in or it is a visitor that does not have an account on your site only IP address, browser Info, fbp and/or fbc will be sent for Advance Matching. 2. If a customer is logged in to your Magento store beside the above-mentioned parameters all other parameters are sent: em, ph, fn, ln, ge, db, ct, st, zp, country, external_id. Of course, all the information is read from the Magento database. If for example, the customer did not provide a phone number, the "ph" will not be sent because it is empty. Another example is if your Magento does not have a gender field enabled in Magento then the customer could not select it and subsequently, our extension cannot send it to Facebook via Advanced Matching. Bottom line is, if information exists in your Magento database it will be sent. 3. The "Purchase" event is different. The customer does not have to be logged in or have an account. The information is read from the order billing/shipping address and everything is sent for Advanced Matching.
Q: Why CompleteRegistration event does not work?
A: If you updated the extension from any previous version to version 4.6.5 or newer in our extension config option "Stores > Configuration > Apptrian Extensions > Facebook Pixel and Conversions API > Facebook Pixel (Client-Side Settings) > Add Facebook Pixel To" replace page handle "customer_account_create" with "customer_account_index".
Technical Specifications
Back to topSeller profile
Seller contact
Integrator
Current Version
4.6.6
Adobe Commerce platform compatibility
Open Source (CE): 2.4 (current), 2.0 (obsolete), 2.1 (obsolete), 2.2 (obsolete), 2.3 (obsolete)
Commerce on prem (EE): 2.4 (current), 2.2 (obsolete), 2.3 (obsolete)
Commerce on Cloud (ECE): 2.4 (current), 2.2 (obsolete), 2.3 (obsolete)
Type
Stable Build
Updated
31 March, 2023
Categories
Extensions, Marketing, Marketing Automation, Advertising
Documentation
License Type
Policy
Quality Report
Back to topAll tests were conducted on the latest versions of Adobe Commerce that existed for the compatible release lines at the moment of the extension submission. Latest versions of all other software were used, as applicable.
Release Notes
Back to top4.6.6:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3 2.4
- Compatible with Commerce on prem (EE) : 2.2 2.3 2.4
- Compatible with Commerce on Cloud (ECE) : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
* Fixed compatibility with Magento 2.4.6
4.6.5:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3 2.4
- Compatible with Commerce on prem (EE) : 2.2 2.3 2.4
- Compatible with Commerce on Cloud (ECE) : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
* CompleteRegistration event dependency on button/theme removed
* Template fix regarding cached ajax calls
4.6.4:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3 2.4
- Compatible with Commerce on prem (EE) : 2.2 2.3 2.4
- Compatible with Commerce on Cloud (ECE) : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
* Fixed bug with the price and number_format function
4.6.3:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3 2.4
- Compatible with Commerce on prem (EE) : 2.2 2.3 2.4
- Compatible with Commerce on Cloud (ECE) : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
* Fixed issue when remote address has more than one IP address
4.6.2:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3 2.4
- Compatible with Commerce on prem (EE) : 2.2 2.3 2.4
- Compatible with Commerce on Cloud (ECE) : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
* Fixed compatibility with PHP 8.1
4.6.1:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3 2.4
- Compatible with Commerce on prem (EE) : 2.2 2.3 2.4
- Compatible with Commerce on Cloud (ECE) : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
* Improved compatibility with older versions of Magento and PHP
* Fixed validation regex for ConsentButton to allow space
4.6.0:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3 2.4
- Compatible with Commerce on prem (EE) : 2.2 2.3 2.4
- Compatible with Commerce on Cloud (ECE) : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
+ Added Cookie Consent options: Enable Cookie Consent, Consent Cookie Name, Consent Cookie Key, Consent Cookie Value, and Consent Button
+ Added Advanced Matching Mapping option with granular control and the following data keys: em, ph, fn, ln, ge, db, ct, st, zp, country, and external_id
- Removed Enable Customer external_id option and functionality is merged with Advanced Matching Mapping option
* Fixed fbclid query parameter
* Fixed frontend product page system messages disappearing too fast
* Fixed issue when sending multiple FB Pixels and FB Access Tokens on the same store view
* Fixed Undefined index: data bug
* The latest EQP Magento Coding Standard improvements
4.5.2:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3 2.4
- Compatible with Commerce on prem (EE) : 2.2 2.3 2.4
- Compatible with Commerce on Cloud (ECE) : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
* Fixed Code Sniffer warning Line exceeds 120 characters
4.5.1:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3 2.4
- Compatible with Commerce on prem (EE) : 2.2 2.3 2.4
- Compatible with Commerce on Cloud (ECE) : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
* Fixed small JavaScript bug in the template regarding customer data retrieval
4.5.0:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3 2.4
- Compatible with Commerce on prem (EE) : 2.2 2.3 2.4
- Compatible with Commerce on Cloud (ECE) : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
+ Added option to choose Facebook product identifier (Magento Product SKU or Magento Product ID)
+ Added option to enable or disable customer external_id (Magento Customer ID)
4.4.3:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3 2.4
- Compatible with Commerce on prem (EE) : 2.2 2.3 2.4
- Compatible with Commerce on Cloud (ECE) : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
* Improved Advanced Matching for Purchase event and guest checkout
* CSP whitelist improvement
* Small configuration visual improvement
4.4.2:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3 2.4
- Compatible with Commerce on prem (EE) : 2.2 2.3 2.4
- Compatible with Commerce on Cloud (ECE) : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
* Small code EQP improvement
4.4.1:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3 2.4
- Compatible with Commerce on prem (EE) : 2.2 2.3 2.4
- Compatible with Commerce on Cloud (ECE) : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
* Event validation methods implemented
4.4.0:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3 2.4
- Compatible with Commerce on prem (EE) : 2.2 2.3 2.4
- Compatible with Commerce on Cloud (ECE) : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
+ Added option to enable/disable Facebook Pixel base code
+ Added option to enable/disable Facebook Pixel noscript tag
+ Added options to enable/disable PageView for both FB Pixel and Conversions API
+ Added options to enable/disable PageView to fire with other events for both FB Pixel and Conversions API
+ Added option for two event firing modes
* Extension now uses Magento private content for customer info
* Extension does not use deprecated Magento Registry class anymore
4.3.0:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3 2.4
- Compatible with Commerce on prem (EE) : 2.2 2.3 2.4
- Compatible with Commerce on Cloud (ECE) : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
+ Added system message to remind user to provide Facebook Pixel ID
+ Added system message to remind user to provide Facebook Access Token
* Changed extension name to Facebook Pixel and Conversions API
4.2.1:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3 2.4
- Compatible with Commerce on prem (EE) : 2.2 2.3 2.4
- Compatible with Commerce on Cloud (ECE) : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
* Fixed Registry key already exists bug
4.2.0:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3 2.4
- Compatible with Commerce on prem (EE) : 2.2 2.3 2.4
- Compatible with Commerce on Cloud (ECE) : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
+ Added Facebook Conversions API ViewContent and Search events
+ Added action_source to server events
* Facebook Server-Side API renamed to Facebook Conversions API
4.1.0:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3 2.4
- Compatible with Commerce on prem (EE) : 2.2 2.3 2.4
- Compatible with Commerce on Cloud (ECE) : 2.2 2.3 2.4
- Stability: Stable Build
-
Description:
+ Added Facebook Data Processing Options
* Compatibility with CSP (Content Security Policies)
4.0.1:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3
- Compatible with Commerce on prem (EE) : 2.2 2.3
- Compatible with Commerce on Cloud (ECE) : 2.2 2.3
- Stability: Stable Build
-
Description:
* Fixed edge case issue when someone comes to the checkout page with an empty cart
4.0.0:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3
- Compatible with Commerce on prem (EE) : 2.2 2.3
- Compatible with Commerce on Cloud (ECE) : 2.2 2.3
- Stability: Stable Build
-
Description:
* Complete rewrite
* Fixed CompleteRegistration event
* Improved detection of selected SKUs with selected quantity and price
+ Added Facebook Server-Side API
+ Added options to enable or disable individual events for both pixel and server-side API
+ Added options to move parameters outside contents
3.0.1:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3
- Compatible with Commerce on prem (EE) : 2.2 2.3
- Compatible with Commerce on Cloud (ECE) : 2.2 2.3
- Stability: Stable Build
-
Description:
* Fixed quote and order item_price to include or exclude tax based on Magento config
* Fixed detection of SKU prices when both include and exclude tax prices are present
3.0.0:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3
- Compatible with Commerce on prem (EE) : 2.2 2.3
- Compatible with Commerce on Cloud (ECE) : 2.2 2.3
- Stability: Stable Build
-
Description:
* Complete rewrite
+ Track with multiple FB Pixels
+ Add FB Pixel to any page via Magento admin without coding.
+ Option to choose a category event name
+ Option to map Magento category attributes to custom parameters
+ Option to select SKU you want to use for bundle products (Product SKU, Children SKUs, or Both) (For Product, Quote, and Order)
+ Option to detect selected SKUs for bundle products
+ Option to select SKU you want to use for configurable products (Product SKU, Child SKUs, or Both) (For Product, Quote, and Order)
+ Option to detect selected SKU for configurable products
+ Option to select SKU you want to use for downloadable products (Product SKU, or Product SKU and Parent SKU) (For Product, Quote, and Order)
+ Option to select SKU you want to use for grouped products (Product SKU, Children SKUs, or Both) (For Product, Quote, and Order)
+ Option to detect selected SKUs for grouped products
+ Option to select SKU you want to use for simple products (Product SKU, or Product SKU and Parent SKU) (For Product, Quote, and Order)
+ Option to select SKU you want to use for virtual products (Product SKU, or Product SKU and Parent SKU) (For Product, Quote, and Order)
+ Options for content_type to use product_group instead of product for the bundle, configurable, and grouped products
+ Option to use content_ids instead of contents for ViewContent event
+ Options to type Magento product attributes code you want to use for the global content_name and content_category parameters
+ Option to map Magento product attributes to custom parameters
+ Options to type parameter name if you want to use Magento order ID, order increment ID, quote ID
+ Options to type event and parameter name you want to use for search tracking
+ Option to type request parameters you want to include for search tracking
+ Added external_id that maps to customer ID for Advanced Matching
2.2.3:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3
- Stability: Stable Build
-
Description:
* Fixed Advanced Matching and Magento v2.3
* Improved validation of config input fields
* Improved config according to latest Magento guidelines
2.2.2:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3
- Stability: Stable Build
-
Description:
* Fixed new line issue in JSON objects
* JavaScript and RequireJS improvements
2.2.1:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3
- Stability: Stable Build
-
Description:
* Fixed template file Advanced Matching JSON object quotes
2.2.0:
- Compatible with Open Source (CE) : 2.0 2.1 2.2 2.3
- Stability: Stable Build
-
Description:
+ Added Advanced Matching (if the customer is logged in)
+ Added Options to add custom parameters to your product related events with parameters to attributes mapping
* Updated code comments
2.1.6:
- Compatible with Open Source (CE) : 2.0 2.1 2.2
- Stability: Stable Build
-
Description:
* Small alteration recommended by Facebook
2.1.5:
- Compatible with Open Source (CE) : 2.0 2.1 2.2
- Stability: Stable Build
-
Description:
* Fixed small bug regarding configurable products price
* Small code improvements
2.1.4:
- Compatible with Open Source (CE) : 2.0 2.1 2.2
- Stability: Stable Build
-
Description:
* Fixed product prices to include/exclude tax depending on Magento configuration
* Fixed currency conversion if currency is different than base currency
2.1.3:
- Compatible with Open Source (CE) : 2.0 2.1 2.2
- Stability: Stable Build
-
Description:
* Fixed event code on checkout success page (double escaping of content_ids)
* Fixed event code on CMS and Category pages
2.1.2:
- Compatible with Open Source (CE) : 2.0 2.1 2.2
- Stability: Stable Build
-
Description:
* Compatibility with Magento 2.2
2.1.1:
- Compatible with Open Source (CE) : 2.0 2.1
- Stability: Stable Build
-
Description:
+ Compatibility with onepagecheckout extension
* Fixed composer.json file PHP version requirements
2.1.0:
- Compatible with Open Source (CE) : 2.0 2.1
- Stability: Stable Build
-
Description:
+ Facebook Dynamic Ads code
+ Compliance with Magento's Extension Quality Program (EQP)
2.0.1:
- Compatible with Open Source (CE) : 2.0 2.1
- Stability: Stable Build
-
Description:
* Fixed small bug in admin blocks
* Fixed composer.json file
2.0.0:
- Compatible with Open Source (CE) : 2.0
- Stability: Stable Build
-
Description:
* Complete rewrite from the ground up
Support
Back to topThe best place to start if you need help with a specific extension is to contact the developer. All Adobe Commerce developers have both a contact email and a support email listed.
Contact Vendor