Track views, carts, searches and purchases for X Ads with Web Conversions API
PrestaShop X Pixel tracking connects X ads with the shopper actions that matter in your store, so you can judge campaigns by product interest, checkout intent and purchases instead of clicks alone. It supports PageView, ViewContent, AddToCart, InitiateCheckout, Purchase, Search, AddToWishlist, SignUp and custom events.
The module only runs X tracking after you enable it with a valid X Pixel ID, and it can wait for supported marketing cookie consent before events fire. It can exclude employee sessions, track add-to-cart, wishlist and custom on-page actions through a protected store connection, and use generated conversion IDs to help avoid duplicate purchase reporting.
Optional Web Conversions API sending queues eligible events when credentials are configured and sends them in controlled batches. Diagnostics, test values, delivery stats and retry tools help agencies and store teams verify tracking before relying on campaign reports.
- Event Source setup. The module requires an enabled switch and a valid X Pixel ID before browser tracking can run.
- Selectable browser events. Settings control PageView, ViewContent, AddToCart, InitiateCheckout, Purchase, Search, AddToWishlist and SignUp event generation.
- Consent-aware loading. When consent respect is enabled, the module checks supported cookie consent signals and can wait for marketing consent before loading X tracking.
- Employee exclusion. A configuration switch can suppress tracking for logged-in employees, so staff testing does not pollute campaign reports.
- Purchase deduplication. Purchase events use a generated conversion ID, and the same order event can be queued for server-side sending when Conversions API is configured.
- API batch delivery. The remote endpoint option checks credentials, queues eligible event data and delivers a controlled batch size.
- Protected event capture. Add-to-cart, wishlist and custom browser events can also be tracked through a protected store connection.
- Custom event rules. Custom tracking rules can be configured for clicks, URL matches, page types or storefront interactions.
PrestaShop X Pixel and Web Conversions API
PrestaShop X (Twitter) Pixel & Ads Tracking adds X website tracking and Web Conversions API support for the shopper actions that matter in your PrestaShop store. Ad budgets are wasted when reports miss product views, add-to-cart actions, checkout starts or purchases, because managers may keep funding campaigns that look better or worse than they really are. This module sends selected browser events, can queue eligible server-side conversion events, avoids double-counting purchases and includes diagnostics so you can check the setup before trusting the numbers.
Measure X ads against real store behaviour
Advertising on X needs more than clicks to show whether campaigns are moving customers toward revenue. The module can track page views, product views, add to cart, checkout starts, searches, wishlist adds, sign-ups and purchases, with your own staff excluded and shopper consent respected before anything fires. That helps merchants connect campaign activity to the actions that show buying intent.
Protect purchase reporting from duplicate sales
Double-counted sales can make a campaign look profitable when it is actually wasting money. The module tracks purchases at order confirmation and tags them so the same sale is not counted twice across browser and server-side reporting. Cleaner purchase data helps you judge budgets, products and audiences with less distortion.
Use server-side sending to reduce missed conversions
Browser tracking can be blocked or interrupted, which means some valuable orders may not appear in ad reports. When the Web Conversions option is configured, eligible events are queued and sent directly from the store as a backup to browser tracking. This helps reduce missed conversions, while still depending on consent, credentials, matching data and X accepting the event.
Track custom actions that matter to your business
Stores often have important actions beyond the standard funnel, such as landing-page clicks, special page visits or on-page interactions. The module lets you define custom events by page, address or on-page action. That gives campaign managers better insight into the moments that influence revenue without adding scattered tracking code across the theme.
Deduplicated purchases for X ads reporting
The module keeps X tracking, event toggles, staff exclusion, consent-aware firing, purchase deduplication, Web Conversions setup, custom events and diagnostics in one PrestaShop settings area. This is safer and easier to maintain than scattered snippets because the team can see whether credentials and rules are ready. Diagnostics, test events, delivery stats and retry tools help protect ad spend from silent tracking failures.
-
Referencemprxpixel
-
In stock2147483647 Items
-
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
X Pixel + Web Conversions API adds X Ads tracking to your PrestaShop store, including browser Pixel events and optional server-side conversion delivery. It helps you measure product views, carts, checkout starts, purchases, sign-ups, searches, wishlist activity, and custom actions from one back-office module.
Have a question about this product?
Our experts are here to help. Ask anything about installation, compatibility, or specifications.
1258
questions
9
categories
2014
building modules since
1.7–9
PrestaShop versions
v1.4.52026-05-27
- AddedAdd X Pixel conversions tracking
- Addedcomplete FR/DE/ES/IT/PL translations
- FixedHarden X Pixel readiness
Loading full changelog...
Works Well With X Pixel + Web Conversions API
Modules our team genuinely pairs with this one — and exactly why each belongs in the same setup.
Measurement
Running the X Pixel with its Web Conversions API, your store attributes X ads to shopper actions, supporting PageView, ViewContent, AddToCart, InitiateCheckout, Purchase, Search, AddToWishlist, SignUp and custom events. That gives X its own conversion view for optimisation, but it is a single-platform lens; it cannot show you how X compares to your other channels or the full funnel those visitors travel once they reach the store.
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 provides channel-agnostic reporting across the store, placing X inside the same funnels and revenue view as everything else.
Used alongside the X Pixel, GA4 keeps X's conversion signals for campaign tuning while showing how the channel performs relative to your other sources. The payoff is cross-channel context for budget decisions: you optimise X campaigns with platform-native data yet allocate spend from a neutral report, so a channel that looks strong in isolation is always weighed against its real contribution to the store.
Workflow
A store using the X Pixel and its Web Conversions API sends shopping events to X ads and usually runs other marketing tags too. Managing those by hand across the theme is fiddly and easy to get wrong, and the X Pixel only handles its own platform, so the broader set of pixels and analytics snippets lacks any shared, event-aware structure to keep it consistent as the stack grows.
Google Tag Manager is a separate module that adds your GTM container and feeds it GA4-formatted ecommerce events from real shopping behaviour, giving surrounding marketing and analytics tags a consistent delivery layer. GTM runs its own ecommerce events and does not control third-party pixels from a shared container, so your dedicated X Pixel and its conversions path stay exactly as configured.
Running both keeps the X Pixel intact while GTM organises the wider tag landscape. The payoff is a more maintainable setup: your X measurement stays independent and reliable, other tags live in a tidy structure, and future changes are far less likely to break existing tracking, so your effort goes into campaign results rather than snippet maintenance.
Governance
Because the X Pixel loads browser tracking and can send Web Conversions API activity, a store using it collects marketing data EU visitors should be able to accept or decline, with no consent gate in the pixel itself. Without a dedicated layer you cannot reliably hold that tracking until a shopper agrees, leaving both a compliance exposure and uncertainty about the provenance of your campaign data.
Cookies Revolution is a separate consent manager that collects and enforces choices for 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 X Pixel, it holds marketing scripts until a shopper agrees and keeps a record of those choices, so your X 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 distinct, manageable layer rather than something wired 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
