Toggle Nav
Menu
Account
  • Sign In
    • Search

    Powered by Adobe Commerce 2.4.8-p3

    apptrian-meta-pixel-and-conversions-api-icon.jpg

    Meta Pixel and Conversions API

    by Apptrian LLC
    main product photo
    First year:
    0
    TOTAL DUE TODAY:
    Contact Vendor

    Trader Information

    Back to top

    Overview

    Back to top

    The 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 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, contact page, 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 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 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 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.

    Compatible with Breeze frontend ("Enable Turbo Feature" option set to "No") without the need for an additional compatibility module. It works out of the box via the convenient Compatibility Mode option in config.

    Compatible with Hyvä frontend without the need for an additional compatibility module. It works out of the box via the convenient Compatibility Mode option in config.

    Compatible with PWA Studio frontend via GraphQL and PWA add-ons.


    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).
    • Optimized loading of the base code.
    • Advanced Matching supported.
    • Works out of the box just type your Meta Pixel ID (Facebook 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 AddPaymentInfo, AddToCart, AddToWishlist, CompleteRegistration, Contact, CustomizeProduct, InitiateCheckout, PageView, Purchase, Search, and ViewContent events.
    • Option to fire PageView event with other events: CompleteRegistration, Contact, 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) (browser-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 JavaScript 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.


    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 supported.
    • 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 AddPaymentInfo, AddToCart, AddToWishlist, CompleteRegistration, Contact, CustomizeProduct, InitiateCheckout, PageView, Purchase, Search, and ViewContent events. * Notice
    • Option to fire PageView event with other events: CompleteRegistration, Contact, 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.

     

    Contact Page

    • Option to type page handles (full action names) where you want contact-related code.
    • Option to type the event name you want to use for contact tracking.
    • Option to type the contact form submit button selector.


    Product Page - 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)
    • 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, AddPaymentInfo Events

    • 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.
    • Option to type the AddPaymentInfo button selector.
    • Option to type the AddPaymentInfo URL hash string.

     

    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.
    • Option to select Compatibility Mode depending on which frontend you are using. (Official Magento Adobe Commerce, Breeze*, or Hyvä)
    • Options to track orders created in the backend by a store owner or administrator.

    * Breeze frontend works only if the "Enable Turbo Feature" option is set to "No".

     

    FAQ

    Q: After I replaced the old Facebook Pixel and Conversions API extension with the new Meta Pixel and Conversions API extension, my Meta Events Manager does not show any new events, and it seems the new extension does not work?

    A: If you replaced any previous version with version 5.0.0 or newer, please paste your Meta Pixel ID and Meta Access Token into the new extension config.

    Stores > Configuration > Apptrian Extensions > Meta Pixel and Conversions API > Meta Pixel (Browser-Side Settings) > Meta Pixel ID

    Stores > Configuration > Apptrian Extensions > Meta Pixel and Conversions API > Meta Conversions API (Server-Side Settings) > Meta Access Token


    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 Generate access token link under Set up direct integration, 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). Paste your access token into our extension configuration option Stores > Configuration > Apptrian Extensions > Meta Pixel and Conversions API > Meta Conversions API (Server-Side Settings) > Meta Access Token.

     

    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 v24.0 or newer, then refresh your Magento cache (System > Cache Management) and you are done.

     

    Q: In Meta Event Manager (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: 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 use 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: 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 is a visitor that does not have an account on your site, only IP address, browser Info, external_id, fbp, and/or fbc will be sent for Advanced Matching. 2. If a customer is logged in to your Magento store, besides 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 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 Config. Then the customer cannot select it, and subsequently, our extension cannot send it to Facebook via Advanced Matching. Bottom line is that if the information exists in your Magento database, it will be sent. 3. In the newer versions of the extension, it is sufficient that the customer has an account and is logged in at least once; after that, our extension will remember the customer, so the customer does not need to be logged in for Advanced Matching to be sent. 4. 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 > Meta Pixel and Conversions API > Meta Pixel (Browser-Side Settings) > Add Meta Pixel To" replace page handle "customer_account_create" with "customer_account_index".


    Q: When the add to wishlist is clicked just before customer account registration, the CompleteRegistration event does not work. Why?

    A: If you updated the extension from any previous version to version 5.1.8 or newer in our extension config option "Stores > Configuration > Apptrian Extensions > Meta Pixel and Conversions API > Meta Pixel (Browser-Side Settings) > Add Meta Pixel To" add page handle "wishlist_index_index".


    Q: Is your extension compatible with Cookiebot?

    A: Yes, it is compatible with Cookiebot since extension version 5.1.4. To set it up configure our extension like below.

    Stores > Configuration > Apptrian Extensions > Meta Pixel and Conversions API > Miscellaneous > Enable Cookie Consent option set to Yes

    Stores > Configuration > Apptrian Extensions > Meta Pixel and Conversions API > Miscellaneous > Cookie Name option set to CookieConsent

    Stores > Configuration > Apptrian Extensions > Meta Pixel and Conversions API > Miscellaneous > Cookie Key option leave empty

    Stores > Configuration > Apptrian Extensions > Meta Pixel and Conversions API > Miscellaneous > Cookie Value option set to marketing:true

    Stores > Configuration > Apptrian Extensions > Meta Pixel and Conversions API > Miscellaneous > Consent Button option set to .CybotCookiebotDialogBodyButton

    The above is just an example. The Cookie Name and the Cookie Value depend on how you set up your Cookiebot.


    Q: The consent cookie implementation I use has multiple values that mean consent is given, one value is "accept-all", the other is "marketing". Can your Meta Pixel and Conversions API extension be configured to work with my cookie consent implementation?

    A: Yes. You will need to update our extension to v5.3.0 or newer. Then for

    Stores > Configuration > Apptrian Extensions > Meta Pixel and Conversions API > Miscellaneous > Cookie Value option type accept-all|marketing

    The values are separated by a | (pipe sign). There is no limit on the number of values you can add this way.


    Q: Why does the Contact event not work for me?

    A: If you updated from any prior version to v5.4.0 or newer, in the option: Stores > Configuration > Apptrian Extensions > Meta Pixel and Conversions API > Meta Pixel (Browser-Side Settings) > Add Meta Pixel To At the end, add:

    ,contact_index_index

    (It starts with a comma, no spaces.)

    If you are using Hyva, you also need to change Stores > Configuration > Apptrian Extensions > Meta Pixel and Conversions API > Contact (Contact Page) > Contact Form Button Selector option to:

    #contact button.btn-primary

    Then refresh your cache (System > Cache Management).


    Q: Why does the CustomizeProduct event fire only once?

    A: The CustomizeProduct event has two behaviors in our extension, depending on the Detect Selected SKU options configuration.

    - If the CustomizeProduct event is enabled and Detect Selected SKU options are disabled, the CustomizeProduct event will be fired only once per page load. The data sent with the event will be the product or parent product data (configurable/bundle/grouped).

    - If the CustomizeProduct event is enabled and Detect Selected SKU options are enabled, the CustomizeProduct event will fire every time a customer/visitor changes something. The data sent with the event will be the variant product data (configurable) or a set of multiple products (bundle/grouped), depending on the customer/visitor selection. There are reasonable safeguards in place to prevent overfiring of the event. For example, in the case of configurable products, the event will not fire until all required options are selected, and the selection can resolve to one particular variant product. Data from the previous event will be retained and compared with the current data; if there is no change, the event will not fire.


    Technical Specifications

    Back to top

    Seller profile

    Apptrian LLC

    Seller contact

    E-mail

    Current Version

    5.4.0

    Adobe Commerce platform compatibility

    Adobe Commerce (cloud): 2.4 (current)

    Adobe Commerce (on-prem): 2.4 (current)

    Magento Open Source: 2.4 (current)

    Type

    Stable Build

    Updated

    02 March, 2026

    Categories

    Extensions, Marketing, SEO/SEM, Marketing Automation, Advertising

    Documentation

    Reference Manuals

    Installation Guides

    User Guides

    License Type

    Custom License

    Policy

    Privacy Policy

    Quality Report

    Back to top

    Installation & Varnish Tests

    Passed

    Coding Standard

    Passed

    Plagiarism Check

    Passed

    Malware Check

    Passed

    Marketing Review

    Passed

    Manual Testing

    Passed

    All 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 top

    5.4.0:

    • Compatible with Adobe Commerce (cloud) : 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.4
    • Compatible with Magento Open Source : 2.4
    • Stability: Stable Build
    • Description:

      + Added AddPaymentInfo event
      + Added Contact event
      + Added CustomizeProduct event
      * Fixed the product detection custom parameters issue

    5.3.3:

    • Compatible with Adobe Commerce (cloud) : 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.4
    • Compatible with Magento Open Source : 2.4
    • Stability: Stable Build
    • Description:

      * Improved Advanced Matching for visitors
      * Optimized Conversions API event sending

    5.3.2:

    • Compatible with Adobe Commerce (cloud) : 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.4
    • Compatible with Magento Open Source : 2.4
    • Stability: Stable Build
    • Description:

      * Fixed cookie consent edge case when the value of the cookie is 0

    5.3.1:

    • Compatible with Adobe Commerce (cloud) : 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.4
    • Compatible with Magento Open Source : 2.4
    • Stability: Stable Build
    • Description:

      * Improved fbc/fbclid functionality

    5.3.0:

    • Compatible with Adobe Commerce (cloud) : 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.4
    • Compatible with Magento Open Source : 2.4
    • Stability: Stable Build
    • Description:

      + Added options to track orders created in the backend by a store owner or administrator
      + Added capability to check multiple consent cookie values
      * Fixed customer address bug when the default billing/shipping address is not selected
      * Fixed fbc and fbp bug with PWA Studio

    5.2.2:

    • Compatible with Adobe Commerce (cloud) : 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.4
    • Compatible with Magento Open Source : 2.4
    • Stability: Stable Build
    • Description:

      * Fixed automatic configuration

    5.2.1:

    • Compatible with Adobe Commerce (cloud) : 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.4
    • Compatible with Magento Open Source : 2.4
    • Stability: Stable Build
    • Description:

      * Small fix in getUserData method

    5.2.0:

    • Compatible with Adobe Commerce (cloud) : 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.4
    • Compatible with Magento Open Source : 2.4
    • Stability: Stable Build
    • Description:

      - Removed "Use content_ids instead of contents" option because now all applicable events are fired with both "content_ids" and "contents" parameters
      - Removed "For Global content_name Use" option because it is redundant, use "Product Parameters to Attributes Mapping" option instead
      - Removed "For Global content_category Use" option because it is redundant, use "Product Parameters to Attributes Mapping" option instead
      - Removed "For Global google_product_category Use" option because it is redundant, use "Product Parameters to Attributes Mapping" option instead
      * Fixed bug with cookie consent feature and logged-in customers
      * Fixed AddToCart and AddToWhishlist behavior with multiple different product option selections and the event buffer
      * Fixed bug with PageView cannot be disabled for Conversions API
      * Improved Advanced Matching
      * Improved Consent Button option to accept multiple selectors, now you can monitor multiple buttons to evaluate consent
      * The XMLHttpRequest has been replaced with fetch

    5.1.8:

    • Compatible with Adobe Commerce (cloud) : 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.4
    • Compatible with Magento Open Source : 2.4
    • Stability: Stable Build
    • Description:

      * Fixed CompleteRegistration event edge case, when add to wishlist is clicked just before customer account registration

    5.1.7:

    • Compatible with Adobe Commerce (cloud) : 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.4
    • Compatible with Magento Open Source : 2.4
    • Stability: Stable Build
    • Description:

      * Fixed bug with the Cookie Consent feature that prevented events from firing because consent had not yet been given
      * Fixed bug with Mode 2 and PHP 8.3
      * Fixed bug with string related methods and PHP 8.3
      * Changed code to play nice with Meta Pixel Helper extension for Chrome

    5.1.6:

    • Compatible with Adobe Commerce (cloud) : 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.4
    • Compatible with Magento Open Source : 2.4
    • Stability: Stable Build
    • Description:

      * Fixed bug with CSP and Magento v2.4.7

    5.1.5:

    • Compatible with Adobe Commerce (cloud) : 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.4
    • Compatible with Magento Open Source : 2.4
    • Stability: Stable Build
    • Description:

      * Fixed bug with cookie retrieval

    5.1.4:

    • Compatible with Adobe Commerce (cloud) : 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.4
    • Compatible with Magento Open Source : 2.4
    • Stability: Stable Build
    • Description:

      * Fixed bug with Cookiebot

    5.1.3:

    • Compatible with Adobe Commerce (cloud) : 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.4
    • Compatible with Magento Open Source : 2.4
    • Stability: Stable Build
    • Description:

      * The content_ids parameter was added beside the contents parameter

    5.1.2:

    • Compatible with Adobe Commerce (cloud) : 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.4
    • Compatible with Magento Open Source : 2.4
    • Stability: Stable Build
    • Description:

      * Fixed bug with guest checkout

    5.1.1:

    • Compatible with Adobe Commerce (cloud) : 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.4
    • Compatible with Magento Open Source : 2.4
    • Stability: Stable Build
    • Description:

      * Fixed issue with checkout success

    5.1.0:

    • Compatible with Adobe Commerce (cloud) : 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.4
    • Compatible with Magento Open Source : 2.4
    • Stability: Stable Build
    • Description:

      + Compatibility with Breeze frontend
      + Compatibility with Hyvä frontend
      * Fixed bug with AddToWishlist event
      * Complete rewrite of the template file code.phtml
      * Optimized loading of initialization code
      - Removed jQuery and other lib dependencies. The extension now uses pure JavaScript

    5.0.0:

    • Compatible with Adobe Commerce (cloud) : 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.4
    • Compatible with Magento Open Source : 2.4
    • Stability: Stable Build
    • Description:

      * Extension changed the name from "Facebook Pixel and Conversions API" to "Meta Pixel and Conversions API"
      * Changed composer package name and namespace
      * Changed instances of "client" to "browser" for better and easier understanding

    Support

    Back to top

    The 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

    Q & A

    Back to top

    Reviews

    Back to top