Trader Information
Back to topOverview
Back to topProvides Apptrian Pinterest Tag and Conversions API extension functionality to PWA Studio (Venia) storefront. Requires both the original (base) extension and the GraphQL (add-on) extension to be installed. Adds Pinterest Tag (Pinterest Pixel) and Pinterest API for Conversions (Pinterest Conversions API / Pinterest Server-Side API) with standard events on appropriate pages. Supports Enhanced Match and has the ability to add custom parameters. Easy to install and use.
WARNING! This extension is not a standalone extension. It is an add-on extension. Requires both original (base) extension and GraphQL (add-on) extension.
Requires Pinterest Tag and Conversions API v4.2.4 or newer.
Requires Pinterest Tag and Conversions API GraphQL v1.0.0 or newer.
Compatible with PWA Studio (Venia) frontend!
The Pinterest Tag (Pinterest 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 Pinterest pixel, you can leverage the actions people take on your website across devices to inform more effective Pinterest advertising campaigns.
The Pinterest API for Conversions (Pinterest Conversions API / Pinterest Server-Side API) (for web) allows advertisers to send web events from their servers directly to Pinterest. 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.
Optionally Pinterest Tag block can be added to any other Magento page or any other extension page (blogs, form pages, etc.) via our extension config by typing the page handle (full action name). The Pinterest Tag 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 Pinterest Ads across multiple devices, including mobile phones, tablets, and desktop computers. By creating a Pinterest Tag 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 Pinterest 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 PWA Studio (Venia) frontend without the need for any additional coding. It works out of the box.
Account & Pricing
To use this extension, a free Pinterest Ads Manager account is required.
NOTE: Pinterest Advertising service is not free; additional charges apply to users running Pinterest Ad Campaigns.
Features
Pinterest Tag (Pinterest Pixel)
- An easy way to enable or disable Pinterest Tag.
- Optimized loading of the base code.
- Enhanced Match
- Works out of the box just type your Pinterest Tag ID (or comma-separated IDs for multipixel setups) in our extension config.
- Option to type page handles (full action names) where you want Pinterest Tag. Using this option Pinterest Tag can be added to any other Magento page or any other extension page (blogs, form pages, etc.).
- Option to enable or disable Pinterest Tag base code.
- Option to enable or disable Pinterest Tag noscript tag.
- Option to enable or disable Pinterest Tag first-party cookies.
- Option to enable or disable Pinterest Tag metadata enrichment.
- Individual options to enable or disable AddToCart, AddToWishlist, Signup, InitiateCheckout, Lead, Checkout, Search, PageVisit, and ViewContent events.
- Option to fire Lead event with other events: Signup, InitiateCheckout, Checkout, Search, PageVisit, and ViewContent.
- Options to detect selected SKU for configurable products.
Pinterest API for Conversions (Pinterest Conversions API / Pinterest Server-Side API)
- An easy way to enable or disable Pinterest API for Conversions (Pinterest Conversions API / Pinterest Server-Side API).
- Enhanced Match
- Option to type your Pinterest Access Token in our extension config.
- Option to type your Pinterest Ad Account ID in our extension config.
- Option to type your Pinterest 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, Signup, InitiateCheckout, Lead, Checkout, Search, PageVisit, and ViewContent events.
- Option to fire Lead event with other events: Signup, InitiateCheckout, Checkout, Search, PageVisit, and ViewContent.
- Options to detect selected SKU for configurable products.
Category (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: product_category=name|google_product_category=google_product_category. The format is simple param1=attribute1|param2=attribute2 Pinterest Tag custom parameter and Magento category attribute are connected by = sign and pairs are separated by | sign.
Product (Product Page - AddToCart, AddToWishlist, PageVisit, 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 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: 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 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: product_category=product_category|google_product_category=google_product_category|color=color. The format is simple param1=attribute1|param2=attribute2 Pinterest Tag custom parameter and Magento product attribute are connected by = sign and pairs are separated by | sign.
Quote (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: product_category=product_category|google_product_category=google_product_category|color=color. The format is simple param1=attribute1|param2=attribute2 Pinterest Tag custom parameter and Magento product attribute are connected by = sign and pairs are separated by | sign.
Order (Checkout Success Page - Checkout 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: product_category=product_category|google_product_category=google_product_category|color=color. The format is simple param1=attribute1|param2=attribute2 Pinterest Tag custom parameter and Magento product attribute are connected by = sign and pairs are separated by | sign.
Search (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.
Miscellaneous
- Option to select Pinterest product identifier. Magento product SKU (Recommended) or Magento product ID.
- Option for Enhanced Match data mapping. Example: external_id=external_id|em=em|ph=ph. The format is simple param1=key1|param2=key2 Pinterest 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, and external_id.
- Option to enable Limited Data Processing.
- Option to type the page event alternative. The page event does not exist in Conversions API. Alternative events are lead or custom.
- Options to connect default Magento "Cookie Restriction Mode" cookie or any third-party cookie consent extension or theme customization via the following options: Enable Cookie Consent, Consent Cookie Name, Consent Cookie Key, Consent Cookie Value, and Consent Button.
FAQ
Q: In the Pinterest Tag Helper extension for Chrome, I get "Warning - This event was sent via POST request. This is normal with large event data, but parsing event data for POST requests in Tag Helper is not supported. This does not indicate an issue with setup."?
A: This is a deficiency of a Pinterest Tag Helper extension for Chrome, not our extension. You can ignore this.
Q: Why is the Pinterest Tag Helper extension for Chrome reporting "More than one event was found for X" (where X is any of the Pinterest standard or custom events)?
A: The Pinterest Tag Helper extension for Chrome does not work well with PWA/SPA applications. In PWA/SPA applications, there is no reload of the web page when navigating from one page to another. As a result, the Pinterest Tag Helper extension for Chrome retains previously fired events in its panel. This is a deficiency in the Pinterest Tag Helper extension for Chrome, not in our implementation of Pinterest Tag.
Q: Why is the console reporting "Pinterest Tag Error: 'load' command was called multiple times."?
A: The Pinterest load function does not work well with PWA/SPA applications. In PWA/SPA applications, there is no reload of the web page when navigating from one page to another. As a result, whenever customer data changes (a new customer creates an account or logs in to an existing account), the Pinterest load function must be called with the new updated customer data. Since there are no page reloads in PWA/SPA applications, the load function is executed multiple times. This should not be reported by Pinterest as an error for PWA/SPA applications. We tested the real Pinterest Tag and Conversions API, and there is no error in the Pinterest Business account. The Conversions are reported properly without any issue. You can ignore this console log.
Q: Does the extension work with multi-store setups?
A: Yes, it does work with multi-store setups. It functions in the same way as the core Magento modules, and it is fully automated.
Technical Specifications
Back to topSeller profile
Seller contact
Current Version
1.0.1
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
31 October, 2025
Categories
Extensions, Marketing, SEO/SEM, 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 top1.0.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 bug with system messages
* Fixed composer.json and package.json files
1.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:
Initial release.
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