TL;DR
The tier boundary is cleaner than most feature tables make it look. STANDARD is a client-side integration: Magento computes ecommerce data, pushes it to the dataLayer, and a generated GTM container carries it to GA4 and Google Ads. PRO keeps all of that and adds a second path where your server talks to GA4 and to ad platform APIs directly, plus the pieces that only make sense once that path exists: refunds, the order grid validation column, multi-property sending, Enhanced Conversions, Hyvä compatibility, and the nine platform pixels, whose server-side addons are sold separately. This article gives you the tier split from the documentation, five questions that decide it for a specific store, and today's prices.
Key Takeaways
- STANDARD covers client-side ecommerce tracking end to end: dataLayer, generated GTM container, custom success page paths, multi-currency, multi-store, user ID and customer group dimensions, product custom dimensions, Google Ads conversion and remarketing tags [1].
- PRO adds the Measurement Protocol layer: 14 selectable server-side event types including purchase and refund, multi-property sending, Redis caching, the order grid validation column, UTM persistence for server-side purchases, and the gtag.js client ID fallback [1].
- Refund tracking is PRO only, and it fires from Magento credit memos [1]. A store correcting revenue by hand in GA4 is paying for the upgrade in labour already.
- Google Ads Enhanced Conversions, including pre-hashing and the include/exclude attribute picker, is PRO [1]. So is Hyvä theme, CSP and checkout compatibility [1].
- The nine ad and marketing platform pixels are PRO. Their server-side API addons are separate purchases on top [1].
- Prices checked on the product page on August 26, 2026: STANDARD is €249 for Open Source, €499 for Commerce, €749 for Cloud; PRO is €399, €699 and €999 for the same editions [2].
The line between the tiers is one sentence
The biggest single block of PRO is the server-side path: STANDARD tracks what the browser reports, and PRO also tracks what your server knows.
A lot follows from that. Refunds live in Magento, not in a browser, so refund tracking is PRO. An order created in the admin never renders a success page, so it belongs to the server path. A visitor running an ad blocker still creates a sales_order row, and only the server path can act on it.
PRO also holds a set of client-side features, the nine pixels, Enhanced Conversions and Hyvä compatibility among them, so the split is not purely browser versus server. Hold the server-side line in mind as the organizing idea and the feature table stops looking arbitrary, then check the client-side rows separately.
What STANDARD covers
More than the name suggests, and enough for a large number of stores.
The client side is generated rather than hand-built: the extension produces a GTM container JSON from your Magento configuration, you import it and publish. Ecommerce events run the full recommended set, from product impressions by position on category and search pages through checkout steps to purchase [1]. Beyond the events themselves, STANDARD carries the configuration surface that decides whether the numbers are correct: tax and shipping inclusion settings per event type, child versus parent identifiers for configurable products, order exclusion at zero value, and custom success page paths for checkouts that do not use checkout/onepage/success [1].
Dimension coverage is there too: Magento user ID, customer group, page type, page name, stock status, review count and score, sale flag, and up to five product attributes sent as custom dimensions [1]. Google Ads conversion tracking and remarketing tags are configured from the same screens. Multi-store and multi-currency are supported, and so are Varnish and full page cache [1].
Our overview of which ecommerce events the GA4 extension tracks covers that event list in detail.
What PRO adds
Grouped by what each family is for, rather than as one long list [1]:
| Family | What you get |
|---|---|
| Measurement Protocol | 14 selectable event types including purchase, refund, sign up, login, item view, search, cart events, checkout steps; user properties; customer group filtering; debug collect endpoint; var/log/ga4.log file logging |
| Operations at scale | Redis caching for extension data, sending to multiple GA4 properties, order grid Measurement Protocol validation column, exclude orders by status with cron catch-up, base or display currency scope |
| Attribution repair | UTM parameter persistence for server-side purchases, client ID fallback via gtag.js, GS2 cookie support |
| Google Ads | Enhanced Conversions, pre-hashed Enhanced Conversions data, the attribute picker, Enhanced Conversions for Leads, new customer data, cart data |
| Platform integrations | Meta, Reddit, TikTok, Microsoft Ads, X, Klaviyo, Pinterest, Snapchat and OpenAI Ads pixels; the server-side API addon for each platform is bought separately |
| Theme and delivery | Hyvä theme, Hyvä CSP and Hyvä Checkout compatibility; GTM server-side container JSON generation (BETA; requires an already-provisioned server container); first-party tracking through a Cloudflare Worker (requires your own Cloudflare Worker or equivalent proxy) |
| Privacy controls | Consent management method selection, consent state logging for Measurement Protocol events |
The server-side setup guide walks through configuring the first two rows.
Five questions that decide it
No percentages here, because your numbers are the ones that matter and I do not have them. Answer these instead.
1. What does a missing order cost you? Multiply your average order value by the orders that never produce a purchase event: payment redirects that skip the success page, admin-created orders, sessions where the tag never fired because the visitor runs an ad blocker or a tracking-restricted browser. If you do not know that count, that unknown is itself an argument for the tier that gives you the order grid validation column.
2. Do you run Google Ads with Enhanced Conversions? If yes, PRO is the tier that has them, and the pre-hash and attribute picker options come with it [1]. If your ad spend is meaningful and your match quality is poor, this is the fastest line item to justify.
3. How many store views and properties are involved? Sending to multiple GA4 properties through the Measurement Protocol is PRO [1]. A single-store single-property setup does not need it. A five-view European operation reporting into per-country properties does.
4. Are you on Hyvä, or moving to it? Compatibility is PRO, delivered as two modules with no configuration [1]. This one is binary.
5. Which ad platforms are you actually spending on? The nine client-side pixels are PRO, and their server-side API addons are separate purchases [1]. A store spending only on Google Ads can ignore this row entirely.
What it costs today
Prices on the product page as of August 26, 2026 [2]:
| Edition | STANDARD | PRO | Difference |
|---|---|---|---|
| Magento Open Source | €249 | €399 | €150 |
| Adobe Commerce | €499 | €699 | €200 |
| Adobe Commerce Cloud | €749 | €999 | €250 |
Set that difference against question 1. A store on Open Source doing an average order value of €80 covers the €150 gap with two recovered orders. That is illustrative arithmetic on made-up inputs, and the point of it is the shape rather than the number: for most stores the upgrade is not decided by the licence cost, it is decided by whether anyone will configure the server-side layer after buying it.
Both tiers install by Composer, which has been the only supported method since v1.16.0 in January 2026, and both run on Magento 2.3.0 through 2.4.9 across all editions [1].
When STANDARD is the right answer
Worth saying, since a vendor article that concludes "buy the expensive one" has told you nothing.
Take STANDARD if your store sells through one storefront, on Luma, with a standard checkout, at a volume where you can sanity check GA4 against Magento reports by eye each month, and your paid spend is small enough that Enhanced Conversions would not change a bid. That describes a lot of Magento stores, and for them the client-side layer configured properly beats a server-side layer configured badly.
Upgrade when the reconciliation stops being eyeballable, when refunds start distorting the revenue you report upward, or when the first ad platform beyond Google Ads gets a budget.
FAQ
Is refund tracking available on STANDARD?
No. Refund events are sent through the Measurement Protocol and are PRO only [1]. They fire from Magento credit memos, which is a server-side event with no browser involved.
Do I need the PRO tier to run the Meta or TikTok server-side addons?
Yes. The API addons install on top of GA4 PRO and are sold separately from it [1]. The client-side pixels for those platforms are also PRO features.
Can I start on STANDARD and upgrade later?
Yes, and the client-side configuration you have already done carries over, since PRO includes everything in STANDARD. Regenerate and re-import the GTM container JSON after any configuration change, which applies to both tiers [1].
Does PRO replace my GTM setup?
No. PRO adds a server-to-server path alongside the container. If you enable the same event on both sides you will double count, so either pause the corresponding GTM tags or use the setting that disables the dataLayer for events tracked server-side [1].
What does the order grid validation column show?
Which orders were sent to GA4 through the Measurement Protocol, as a filterable column in the Magento admin order grid [1]. Sort by it and the orders that never reached GA4 come to the top, which is where a monthly reconciliation should start.
The full feature split, screen by screen, is on the Magento 2 Google Analytics 4 extension page, where both tiers are listed per Magento edition.
One last practical note: if you already own STANDARD and you are weighing the upgrade, open your last three months of credit memos and check whether any of that refunded revenue was ever corrected in GA4. For most stores the answer is no, and that number is the honest start of the calculation.
Sources
- WeltPixel Google Analytics 4 User Guide, v1.17.3, August 3, 2026, https://docs.weltpixel.com/GA4/User-Guide-WeltPixel-Google-Analytics-4.html
- WeltPixel product page, Magento 2 Google Analytics 4 (GA4) Extension with GTM and Server-Side Tracking, prices observed August 26, 2026, https://weltpixel.com/products/magento-2-google-analytics-4-ga4-extension-with-gtm-server-side-tracking