Platform · Magento 2
A consent-gated analytics tag does not see the shoppers who reject the banner, so the channel behind their orders disappears from your reports. The Sealmetrics module for Magento 2.4+ tracks the funnel from product view to purchase, per store view and currency, without setting a cookie or collecting customer data.
Magento 2.4+ · Adobe Commerce · PHP 7.4+ · no cookies · EU-hosted in Dublin
Quick answer
Sealmetrics for Magento is a Magento 2.4+ module, including Adobe Commerce, that adds cookieless analytics to a store. It tracks product views, add-to-cart, checkout starts and purchases, assigns a content group to each page from Magento's layout handles and captures the selected options of configurable products, without setting a cookie or collecting customer data. You download it from the Sealmetrics dashboard, copy it into app/code, enable it with bin/magento and enter your Account ID under Stores, Configuration. The purchase is sent from the order success page with its revenue, currency, payment method, coupon and items, and each store view can be configured with its own currency. Order IDs are not stored outside Magento, so reconciliation is on totals and channels. Because the purchase depends on the success page loading, a custom pixel domain helps where ad blockers are common.
What it captures
Enabled with an Account ID, the module sends the standard eCommerce funnel and labels every page by Magento layout handle, with each event switchable in the admin.
| Event | When it fires | What it carries | Note |
|---|---|---|---|
| pageview | Every page | The page, its channel and its content group | home, product, catalog, search, cart, checkout, thankyou, account |
| view_item | Product page | Product name, ID, SKU, price, currency, category, brand | Can be switched off in the module settings |
| add_to_cart | When Magento updates the cart | Product, ID, price, quantity, currency | Captured through Magento's customer-data events; configurable options included |
| begin_checkout | Checkout | Cart total, currency, item count | The step before payment |
| purchase | Order success page | Revenue, currency, payment method, coupon, items with options | A conversion; the other events are microconversions |
Product, cart and checkout steps are events in a funnel; the purchase is the conversion that carries revenue. How conversions are modelled across platforms is covered in conversion tracking without cookies.
What a consent-gated setup loses
Magento knows every order. A cookie-based tag only knows the ones placed by visitors who accepted the banner and were not blocked.
On the one store we have measured side by side — a Shopify shop — GA4 did not record 29% of visits. The mechanism does not depend on the platform: a tag that waits for consent never sees the visitor who says no. The argument in full is on complete data.
On that store, Sealmetrics recorded 11% more direct traffic than GA4 but 37–52% more from paid campaigns, so a consent-based channel report tilts toward traffic you already had.
Each store view has its own audience, language and banner behaviour. A consent-gated tag loses a different share in each one, which makes comparing store views on channel performance unreliable.
Install on Magento
A standard Magento module install, no theme edits. The last step makes the comparison with Magento's own orders fair; the reasoning is the same as in one number for marketing and finance.
In the Sealmetrics dashboard, open Settings → Integrations and download the Magento module. Create app/code/SealMetrics/Analytics in your Magento installation and copy the module files into it. It needs Magento 2.4.0+ and PHP 7.4+ or 8.0+.
Run bin/magento module:enable SealMetrics_Analytics, then bin/magento setup:upgrade and bin/magento cache:clean. Check with bin/magento module:status that the module is enabled.
Go to Stores → Configuration → Sealmetrics → Analytics, enable the module, enter your Account ID and choose which events to track. Optionally set a custom pixel domain, then save and clear the cache. Configure per store view if you need to.
Open a product, add it to the cart and start checkout, and check the events arrive. Place a test order and confirm the purchase appears once the success page loads and the order status is complete.
Compare totals for the same period, store view, timezone and currency, and leave out orders with no web visit behind them, such as orders created in the admin or by phone.
What stays, what changes
Each tool keeps the job it does well. Sealmetrics takes the one a consent-gated tag cannot do: telling you which channels produced the orders.
Stay: the order and catalogue view.
Sales, products, customers and coupons stay in Magento, and Sealmetrics is checked against its order totals.
One number for marketing and financeCan stay, for Google Ads.
Many teams keep it as the Google Ads conduit while budget decisions move to the measured base.
GA4 migration planStay for bidding, behind consent.
Sealmetrics does not send conversions to ad platforms, so the platforms keep their own consent-gated setup.
Campaign revenue attributionBecomes the channel view.
Revenue by channel, campaign and creative on every recorded session, per store view, checked against Magento's orders.
Complete dataThe method, measured
No Magento customer case is published yet, and this page does not pretend otherwise. The reconciliation method above is the one Incapto used on Shopify, where both tools were checked against real orders before anything was compared.
What it does not do
Most of these follow from how Magento confirms an order in the browser. For stores where a webhook confirms purchases server-side, see Sealmetrics for Shopify.
Purchases are sent when the order success page loads. If a payment method never returns the shopper there, that purchase is not recorded.
The default pixel address can appear on blocklists. Setting a custom pixel domain keeps the requests on your own domain.
Order IDs are not stored outside Magento, so you compare totals and channels, never row by row.
Detection relies on Magento layout handles and customer-data events. A heavily customised or headless storefront that bypasses them may need the tracker and events sent directly.
Orders created in the admin, by phone or through marketplaces have no web visit, so they have no channel to attribute.
No multi-touch model and no view-through; a returning visit through another channel takes the credit.
Common Magento questions
Download the Magento module from the Sealmetrics dashboard under Settings → Integrations, copy it into app/code/SealMetrics/Analytics, run bin/magento module:enable SealMetrics_Analytics, setup:upgrade and cache:clean, then enter your Account ID under Stores → Configuration → Sealmetrics → Analytics. It needs Magento 2.4.0+ and PHP 7.4+ or 8.0+.
The module is documented for Magento 2.4+, including Adobe Commerce. It is installed as a standard module in app/code and configured in the Magento admin, so check it through your usual deployment process for your hosting setup.
Yes. The module works with multiple store views, can be configured per store if needed, and respects each store's currency. Compare each store view with its own orders, in the same timezone and currency.
Yes. The options selected on a configurable product, such as size or colour, are captured with add-to-cart and with the items of the purchase, together with product name, SKU, price, category and brand.
Check that the order success page loads after payment, because that is where the purchase is sent, and that the order status is complete. Then check the JavaScript console for errors, confirm the module is enabled with the right Account ID, and clear the frontend cache before testing again.
The tracker is about 1.1 KB on the wire. For the store as a whole, the documentation recommends the usual Magento practices: production mode, deployed static content and full page cache enabled.
It replaces neither by default. Magento's reports stay the source for orders, products and customers, and GA4 can stay as the Google Ads conduit. Sealmetrics becomes the channel and revenue view, measured without consent loss and checked against Magento's order totals.
Not necessarily for the analytics: the module sets no cookie and collects no customer data. Ad pixels, chat tools or A/B testing that do store data still need consent, and whether your store is exempt for analytics depends on its configuration and your national authority's criteria.
Magento walkthrough
Book 30 minutes with the founder. We install the module on your Magento store, test the funnel and a purchase, and set up the comparison with your orders per store view.
