Send Pinterest Ads real shopping signals from your PrestaShop visits, carts and purchases
Pinterest Tag reports shopping activity from your PrestaShop store to Pinterest Ads, from product interest to confirmed purchase. One numeric Tag identifier and the activation switch start browser measurement.
Pinterest is a visual discovery and advertising service. Its advertising panel uses shopping signals for conversion reports, audiences and campaign optimisation; campaign spending remains a separate Pinterest expense, without an intermediary analytics account.
You switch nine shopping actions separately, choose tracked pages and match product identifiers to your Pinterest catalogue. Server delivery additionally requires your advertising account identifier and conversion token. Browser and server copies share one event identity, and marketing consent governs both routes.
An order reported through both routes stays one conversion, keeping campaign reports from counting the same purchase twice.
Summary of what the module offers
Pinterest Tag connects a PrestaShop store to Pinterest Ads and gives the merchant control over the shopping signals sent from the browser and the server. Six features connect shopping signals, catalogue details and reliable delivery with Pinterest Ads.
- Connection: one validated Pinterest Tag identifier starts browser measurement without a theme change.
- Pinterest service: shopping signals feed conversion reports, audiences and campaign optimization in the Pinterest advertising panel.
- Commerce actions: nine separate controls cover the journey from page visit to registration and paid order.
- Catalogue detail: product, variant, brand, visible category items, cart value and order lines travel with the relevant action.
- Store control: custom rules, page scope, catalogue identity and separate shop settings fit the individual business.
- Delivery: coordinated browser and server routes, consent, a durable queue, testing and diagnostics keep the numbers trustworthy.
Which shopping decisions become visible to Pinterest?
Pinterest Ads works with the actions supplied by the store. The module sends page visits, product and category views, successful cart and wishlist additions, checkout starts, searches, registrations and confirmed purchases. Each action has its own switch, so the merchant decides whether the account learns from the entire journey or only the stages relevant to the current campaigns.
Pinterest turns these signals into conversion reporting, audience building and campaign optimization in its own advertising panel. The module owns the PrestaShop connection and the shopping context; Pinterest owns attribution and advertising decisions. Advertising spend remains in the Pinterest account, with no extra intermediary service between the shop and Pinterest.
Which product details keep catalogue reports accurate?
A product view carries the catalogue identity selected by the merchant, the product or combination, an optional prefix, localized name, brand, category, price and currency. A successful cart addition carries the selected variant and quantity. Category activity contains the exact products visible after sorting, filtering and pagination, so Pinterest receives the same selection the shopper saw.
Checkout start adds cart value, item count, currency and line items. A confirmed purchase adds order value, quantity, currency, order number and every ordered item, including guest orders. Known-customer email, customer identity and name are normalized and protected before matching, while anonymous activity receives the accepted visit signals needed for server delivery.
How does one order remain one conversion?
The browser and server versions of the same action leave the shop with one shared event identity. Pinterest therefore joins the two reports instead of presenting one order twice. The server purchase is created from the validated order, independently of the confirmation page, and a browser purchase missed on that page is delivered on the next consent-eligible visit with the same identity.
Server actions enter a durable queue, leave immediately where appropriate and return through a five-minute background cycle after a temporary failure. Exhausted rows are revived with a fresh attempt allowance, old completed rows are cleaned up, and another compatible module already responsible for the same Pinterest Tag suppresses duplicate delivery. Marketing consent governs both browser and server routes, including actions from anonymous visitors.
How closely does tracking follow the individual store?
Merchant-defined rules use up to fifteen custom conversion names for the steps outside the standard shopping set. A rule responds to a selected button or element, an address containing chosen text, a page type or a named action already produced by the store. It carries the business parameters chosen by the merchant, runs once or repeatedly and follows the browser route, the server route or both.
The base Tag has its own page scope, separate from custom actions. Measurement covers the whole store, selected stages of the buying journey or every page except chosen exclusions. Each shop keeps its own Tag, advertising account and catalogue identity settings, so languages, brands and markets remain separate inside one multistore installation.
How does setup stay simple and remain trustworthy?
The first launch needs installation, one numeric Pinterest Tag identifier and the activation switch. The module rejects an invalid identifier and stays silent until the connection is complete. The deeper server route adds the Pinterest advertising account identifier and conversion token, while the standard shopping actions already start with sensible defaults.
The same screen shows pending, sending, delivered and failed actions, recent errors and delivery attempts. A structurally valid test conversion checks the connection before campaign data depends on it, and the retry control truly returns failed rows to delivery. Employee exclusion keeps staff testing out of customer data, while MPR Cookies Revolution or MPR Cookie Banner makes the shopper's marketing choice effective for both routes.
-
Referencemprpinteresttag
-
PrestaShop CompatibilityPS 1.6 – 9.x
-
Pricing ModelOne-time Purchase
-
Module TypeFront-office
-
GDPR RelevantYes
-
Business GoalMarketing & Retargeting
-
External Account NeededYes
-
Module ComplexityLightweight Widget
-
Customer Journey StageAttract Visitors
-
Works With PlatformAd & Analytics Networks
What customers say about us
Company reviews
5.0
★
★
★
★
★
(4 reviews)
Loading customer reviews...
No product reviews yet
Be the first to share your experience with this module.
Write a Review
Pinterest Tag adds Pinterest advertising tracking to your PrestaShop store, including browser events and optional server-side Conversions API events. It helps Pinterest receive product, cart, checkout, search, signup, wishlist, and custom interaction signals for campaign attribution and audience building.
Have a question about this product?
Our experts are here to help. Ask anything about installation, compatibility, or specifications.
1343
questions
9
categories
v1.3.92026-05-27
- AddedTrack Pinterest category views
- AddedAdd Pinterest custom events
- AddedAdd Pinterest demo event monitor
Loading full changelog...
Works Well With Pinterest Tag
Modules our team genuinely pairs with this one, and exactly why each belongs in the same setup.
Measurement
Running the Pinterest Tag with its CAPI path, your store measures Pinterest Ads against real behaviour, seeing whether pin traffic becomes product and category views, searches, carts, wishlist actions, checkout steps, sign-ups or completed orders. That is strong single-channel attribution, but it only ever describes Pinterest in Pinterest's own terms and gives you no neutral vantage point to compare that channel fairly against the rest of your traffic.
Google Analytics GA4 is a separate module that sends ecommerce activity to your GA4 property after validating the Measurement ID, covering product views, cart activity, checkout starts, purchases, searches, logins and account creation. It supplies channel-agnostic reporting for the whole store, so Pinterest sits inside the same funnels and revenue view as everything else.
Used alongside the Pinterest Tag, GA4 lets you keep Pinterest's own conversion view for campaign tuning while judging its performance relative to your other sources. The payoff is grounded budget decisions: you optimise Pinterest campaigns with platform-native data yet allocate spend from a cross-channel report, so a channel that looks impressive in isolation is always weighed against how it truly contributes to the store as a whole.
Workflow
A store running the Pinterest Tag is already sending shopping events to Pinterest Ads and, in most cases, managing other marketing tags too. Keeping all of those organised by hand quickly becomes fiddly, and the Pinterest Tag only ever handles its own platform, so the broader collection of pixels and analytics snippets has no shared, dependable structure holding it together.
Google Tag Manager is a separate module that adds your GTM container and feeds it GA4-formatted ecommerce events from real shopping behaviour, giving the marketing and analytics tags around your store a consistent, event-aware delivery layer. GTM runs its own ecommerce events; you configure other marketing tags in its container, so your dedicated Pinterest Tag stays untouched.
Running both keeps the Pinterest Tag and its CAPI path in place while GTM tidies the surrounding tag landscape. The payoff is a cleaner operation: your Pinterest measurement remains intact and independent, the rest of your tracking sits inside a well-managed structure, and future changes to other tags become far less likely to break something, so you spend time acting on results rather than untangling snippets.
Complement
With the Pinterest Tag installed, your store is treating Pinterest as a real acquisition channel and measuring how pin-driven traffic converts. Measurement captures performance, but it does nothing to keep Pinterest content visible on your own storefront, where the same visual material could reinforce your brand and reassure shoppers at the point of decision rather than only being tracked as an ad source.
Pinterest Feed Integration is a separate module that brings selected Pinterest pins, boards or RSS content into your storefront, with optional product publishing to Pinterest when publishing details, board ID and a caption template are configured. It keeps that social proof close to the buying journey instead of sending shoppers away to check whether your brand is active on the platform.
Used together, they let you measure Pinterest performance and present Pinterest inspiration on-site as two complementary tools. The payoff is that the channel you already invest in tracking also earns visibility on your pages: visual shoppers see a consistent brand story while browsing, you reuse content you already create, and the effort you put into Pinterest works both in your reporting and on your storefront.
Governance
Because the Pinterest Tag loads browser tracking and can send Pinterest CAPI activity, a store using it is collecting marketing data that EU visitors should be able to accept or decline. The tag already applies marketing consent to both routes; a dedicated consent manager adds the choice interface, category controls and a record of each decision.
Cookies Revolution is a separate consent manager that collects and enforces choices across necessary, functional, analytics and marketing cookies. It blocks matching external and inline scripts before consent, reactivates allowed ones afterwards once it is granted, and records each decision.
Used alongside the Pinterest Tag, it holds marketing scripts until a shopper agrees and keeps a record of those choices, so your Pinterest measurement rests on a consent-respecting foundation. The payoff is tracking you can stand behind: you keep measuring shoppers who opt in, you can evidence how consent was captured, and compliance stays a separate, manageable layer rather than something patched into your campaign setup.
30 days return right
Easy return - no questions asked
Plug & Play Modules
Install, set up and take profit
Dedicated Support First
Priority Help & Satisfaction Over Sales
You might also like
Who builds and maintains this module
Built and maintained by David Miller and mypresta.rocks. David has worked with PrestaShop since 2013, and the company behind this shop has been registered since 3 December 2018. Every module in this catalogue is our own work, so your questions to support reach the people who wrote the code. The changelog on this page lists every update with its date.