Platform · OpenCart
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 extension for OpenCart 4.x tracks the funnel from product view to purchase, store by store, without setting a cookie or collecting personal data.
OpenCart 4.x · 3.x with modifications · PHP 7.4+ · no cookies · EU-hosted in Dublin
Quick answer
Sealmetrics for OpenCart is an extension, built primarily for OpenCart 4.x and usable on 3.x with modifications, that adds cookieless analytics to a store. It tracks product views, add-to-cart clicks, checkout page views and purchases, each with its own switch in the extension settings, and labels every page with a content group taken from the OpenCart route, without setting a cookie or collecting personal data. On OpenCart 4.x you upload the OCMOD package in the Extension Installer, install Sealmetrics Analytics under Analytics and enter your Account ID. The purchase is sent from the order confirmation page with its revenue, currency, payment method, coupon and items, including the options chosen for each product. In a multi-store installation each store is configured and tracked on its own. Order IDs are not stored outside OpenCart, so reconciliation is on totals and channels, and a purchase whose shopper never reaches the confirmation page is not recorded.
What it captures
Enabled with an Account ID, the extension sends the standard eCommerce funnel and labels every page by its OpenCart route, with each funnel event switchable in the settings.
| Event | When it fires | What it carries | Note |
|---|---|---|---|
| pageview | Every page | The page, its channel and its content group | home, product, catalog, brand, search, cart, checkout, thankyou, account, contact |
| view_item | Product page view | Product ID, name, SKU, price, category, brand | Track Product Views |
| add_to_cart | Add-to-cart button click | The product added | Track Add to Cart; needs the standard OpenCart cart methods |
| begin_checkout | Checkout page view | The checkout step | Track Checkout |
| purchase | Order confirmation page | Revenue, currency, payment method, coupon, items with their options | Track Purchases; the conversion that carries revenue |
| Contact form | Contact form submission | A lead conversion | Optional: Contact Forms as Leads |
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
OpenCart 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 in an OpenCart installation has its own audience and banner behaviour. A consent-gated tag loses a different share in each one, which makes comparing stores on channel performance unreliable.
Install on OpenCart
The steps below are for OpenCart 4.x, the primary target; OpenCart 3.x has its own route, given in the second step. The last step makes the comparison with OpenCart'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 OpenCart extension package, sealmetrics.ocmod.zip. It needs PHP 7.4 or later.
On OpenCart 4.x, go to Extensions → Installer and upload sealmetrics.ocmod.zip. On OpenCart 3.x, upload the contents of the upload folder to your OpenCart root instead, then go to Extensions → Modifications and click Refresh.
Go to Extensions → Extensions → Analytics (Extensions → Analytics on 3.x), install Sealmetrics Analytics and open its settings (Edit, on 4.x). Enter your Account ID, choose which of product views, add to cart, checkout and purchases to track, optionally set a custom pixel domain and contact forms as leads, then enable the extension and save.
Open a product, add it to the cart and go to checkout, and check the events arrive. Place a test order and confirm the purchase appears once the order confirmation page loads. If nothing arrives, check the extension is enabled with the right Account ID and clear the OpenCart cache under System → Maintenance.
Order IDs are not stored outside OpenCart, so compare totals rather than rows: the same period, timezone and currency, for each store separately, since each store is configured and tracked on its own.
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 coupons stay in OpenCart, 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, checked against OpenCart's orders.
Complete dataThe method, measured
No OpenCart 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 OpenCart 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.
OpenCart 3.x is supported with modifications and a different install route. Test the funnel and a purchase on a 3.x store before relying on the numbers.
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 OpenCart, so you compare totals and channels, never row by row. Protection against a reloaded confirmation page counting twice is not documented for OpenCart, so check for it when you compare.
Add-to-cart tracking relies on the standard OpenCart cart methods. A theme or extension that replaces them may not send the event.
No multi-touch model and no view-through; a returning visit through another channel takes the credit.
Common OpenCart questions
Download sealmetrics.ocmod.zip from the Sealmetrics dashboard under Settings → Integrations and upload it in Extensions → Installer. Then go to Extensions → Extensions → Analytics, install Sealmetrics Analytics, click Edit, enter your Account ID, enable the extension and save.
OpenCart 4.x has primary support; OpenCart 3.x is supported with modifications. On 3.x you upload the contents of the upload folder to your OpenCart root, refresh Extensions → Modifications, install Sealmetrics Analytics under Extensions → Analytics, and enter your Account ID. It needs PHP 7.4 or later.
Yes. The settings have separate switches for product views, add to cart, checkout and purchases, plus an option to track contact form submissions as lead conversions. Page views are tracked automatically, each with a content group taken from the OpenCart route.
Yes. In a multi-store installation you configure Sealmetrics separately for each store, with different Account IDs if you need them, and each store is tracked independently.
The order value, currency, payment method and coupon, and for each item the product ID, name, SKU, price, quantity, category and brand, with the product options chosen, such as size or colour, sent as properties.
Check that Track Purchases is enabled, that the order confirmation page loads correctly after payment, because that is where the purchase is sent, and that there are no JavaScript errors in the browser console.
Check that Track Add to Cart is enabled and that your store's cart uses the standard OpenCart methods. A theme or extension that replaces the cart may not trigger the event.
Not necessarily for the analytics: the extension sets no cookie and collects no personal 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.
OpenCart walkthrough
Book 30 minutes: we walk through the extension setup on your OpenCart version, how to test the funnel and a purchase, and how to compare Sealmetrics with your orders store by store.
