Platform · PrestaShop
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 PrestaShop 1.7+ and 8.x tracks the funnel from product view to purchase, in every store language, without setting a cookie or collecting customer data.
PrestaShop 1.7+ and 8.x · PHP 7.2+ · no cookies · EU-hosted in Dublin
Quick answer
Sealmetrics for PrestaShop is a module for PrestaShop 1.7 and later, including 8.x, that adds cookieless analytics to a store. It tracks product views, add-to-cart, checkout starts and purchases, labels every page with a content group taken from the PrestaShop controller and records the attributes of product combinations, such as size or colour, without setting a cookie or collecting customer data. You download the ZIP from the Sealmetrics dashboard, upload it in the Module Manager and enter your Account ID. The purchase is sent from the order confirmation page with its revenue, currency, payment method, coupon and items, and the module records that it has done so, so refreshing the page does not count the order twice. Order IDs are not stored outside PrestaShop, so reconciliation is on totals and channels. A purchase whose shopper never reaches the confirmation page is not recorded.
What it captures
Configured with nothing more than an Account ID, the module sends the standard eCommerce funnel and labels every page by the PrestaShop controller that rendered it.
| Event | When it fires | What it carries | Note |
|---|---|---|---|
| pageview | Every page | The page, its channel and its content group | home, product, catalog, cart, checkout, thankyou, page, contact, search, brand, account |
| view_item | Product page | Product name, ID, SKU, price, currency, category, brand | Product and category names in the shopper's current language |
| add_to_cart | When PrestaShop updates the cart | Product name, ID, price, quantity, currency | Captured through PrestaShop's native updateCart event |
| begin_checkout | Checkout start | Cart total, currency, item count | The step before payment |
| purchase | Order confirmation page | Revenue, currency, payment method, coupon, items with combination attributes | A conversion, not sent again when the page is refreshed; 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
PrestaShop 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 language version has its own audience and its own banner behaviour. A consent-gated tag loses a different share in each one, which makes comparing markets on channel performance unreliable.
Install on PrestaShop
A standard PrestaShop module upload, no theme edits. The last step makes the comparison with PrestaShop'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 sealmetrics-prestashop.zip. The module needs PrestaShop 1.7.0 or later, or 8.x, and PHP 7.2 or later.
In the PrestaShop admin, go to Modules → Module Manager, click Upload a module and upload the ZIP file. If the module does not appear, clear the PrestaShop cache and check the module folder permissions and your PHP version.
Click Configure on the module and enter your Sealmetrics Account ID. Optionally, set a custom pixel domain in the Pixel URL field so the requests stay on your own domain.
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 order confirmation page loads. If it does not, check that the displayOrderConfirmation hook is registered and test with the default theme.
Order IDs are not stored outside PrestaShop, so compare totals rather than rows: the same period, timezone and currency, leaving out orders with no web visit behind them, such as orders created in the back office.
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.
Stays: the order and catalogue view.
Orders, products, customers and vouchers stay in PrestaShop, 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, checked against PrestaShop's orders.
Complete dataThe method, measured
No PrestaShop 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 PrestaShop 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 confirmation 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 PrestaShop, so you compare totals and channels, never row by row.
Add-to-cart relies on PrestaShop's native updateCart event, and the purchase on the order confirmation hook. A theme or checkout that bypasses them may not send those events, which is why troubleshooting starts with the default theme.
Orders created in the back office, 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 PrestaShop questions
Download sealmetrics-prestashop.zip from the Sealmetrics dashboard under Settings → Integrations. In the PrestaShop admin, go to Modules → Module Manager, click Upload a module, upload the ZIP and click Configure to enter your Account ID.
PrestaShop 1.7.0 and later, and PrestaShop 8.x, with PHP 7.2 or later.
No. The module stores in its configuration that the order has been tracked, so refreshing the order confirmation page does not send the purchase again.
Yes. The attributes of a product combination, such as size, colour or material, are recorded with the items of the purchase, together with product name, ID, SKU, price, category and brand.
Yes. The module works with all PrestaShop languages: product names are sent in the shopper's current language, category names are localised and manufacturer names are included.
Check that the order confirmation page loads after payment, because that is where the purchase is sent, and that the module's order confirmation hook is registered. Then test with the default theme to rule out a theme that bypasses it.
It replaces neither by default. The PrestaShop back office stays 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 PrestaShop'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.
PrestaShop walkthrough
Book 30 minutes: we walk through the module setup on your PrestaShop version, how to test the funnel and a purchase, and how to compare Sealmetrics with your orders.
