Privacy Analytics for E-Commerce Sites

Privacy-first analytics is not usually the first thing that comes to mind for e-commerce. The standard playbook — Facebook Pixel, Google Analytics with Enhanced Ecommerce, revenue attribution, cart abandonment funnels — assumes you want to track individual shoppers across sessions and tie behaviour to revenue.

Antlytics does none of that. It collects no personal data, sets no cookies, and has no concept of individual users.

So does it work for e-commerce at all?

The answer is: yes, for a specific type of e-commerce site. This post explains what you can and cannot track, and when the trade-off makes sense.

What you can track

Traffic and top pages

The same data Antlytics provides for any site applies to a shop: total visitors, pageviews, top pages, referrers, countries, devices, and browsers.

For a small shop, knowing which product pages get the most traffic is genuinely useful. If your /products/blue-widget page gets 400 visits a month and /products/red-widget gets 40, that is a signal — whether it means the blue widget is more interesting, better positioned in navigation, or ranking higher in search.

Path-based conversion goals

Antlytics supports path-based goals: when a visitor reaches a specific URL, that counts as a conversion. For e-commerce, the natural goal is the order confirmation or "thank you" page — /orders/confirmation, /checkout/complete, or whatever URL your platform uses.

Setting up a goal for that page gives you:

Goal completions — how many sessions reached the confirmation page
Goal rate — completions as a percentage of total sessions

This is a session-level metric, not a revenue metric. You see how many orders were completed in a period, not the revenue value. For many small shops, this is exactly enough — it answers "did my marketing drive sales?" without needing per-session tracking.

See conversion goals without cookies for the step-by-step setup.

Referrer and UTM analysis

Where does your shop traffic come from? Antlytics shows referrer data for every session — direct traffic, search, social, and specific referring URLs.

If you run campaigns, UTM parameters pass through the URL and appear in the Sources breakdown. You can compare which channels drive the most traffic and which drive the most goal completions.

This is the same data most shops look at most often: "Did the Instagram post drive traffic? Did the email newsletter drive orders?" You can answer both questions with Antlytics, without cookies.

Product page engagement (approximate)

There is no built-in "add to cart" event tracking in Antlytics. But you can observe product page traffic over time and correlate it with conversion goals. If /products/blue-widget traffic goes up 30% in a week and order confirmation completions go up 25%, that is a reasonable signal.

It is approximate. It is not perfect attribution. But for a small shop where you are making one or two decisions at a time, approximate is often enough.

What you cannot track

Revenue attribution

Antlytics does not have a concept of order value. You cannot track "Session X resulted in a £45 order." There is no revenue dimension, no average order value metric, no revenue per channel.

If you need to know which marketing channel generates the most revenue (not just the most orders), you need a tool that can receive revenue data — typically through an event API or a platform integration. Antlytics does not provide this.

Individual user journeys

You cannot see what path a specific shopper took: which pages they visited, what they added to cart, where they dropped off. Antlytics tracks sessions, not individuals. There is no user-level replay or funnel analysis.

If you are optimising a checkout funnel step by step (reducing drop-off at each screen), you likely need a more granular tool.

Cart abandonment data

Cart abandonment tracking requires knowing that a specific session added an item to cart and did not complete checkout. That requires cross-step session identity, which Antlytics does not support beyond the current tab's sessionStorage.

Ad retargeting integration

The Facebook Pixel, TikTok Pixel, and Google Ads conversion tracking all require setting cookies and collecting personal data. These are incompatible with Antlytics's privacy model.

If your marketing strategy depends on running retargeting ads and optimising them with conversion data from your site, you need a tool that supports these integrations. Antlytics does not, by design.

When privacy analytics is a good fit for e-commerce

Small shops with simple funnels. If your shop has a handful of products and a straightforward checkout, aggregate data is often enough. You want to know if your traffic is growing and if conversions are happening — not a 47-step attribution model.

Privacy-conscious brands. Some shops are built around values that include not tracking their customers. A privacy-first analytics tool is consistent with that positioning. Your customers may notice (and appreciate) the absence of a cookie consent banner.

Sites that already know their traffic sources. If you are a maker who sells via a newsletter and a few social posts, you already know where your traffic comes from. Antlytics confirms the numbers; you do not need a complex attribution model to act on that.

Developers building for clients who want simplicity. A client who just wants to know "how many people visit my shop and do they buy?" is well served by Antlytics. A client who wants to optimise a paid acquisition funnel is not.

When you need something else

If you need any of the following, privacy analytics will not cover you:

Revenue reporting tied to sessions
Individual customer journey analysis
Ad pixel integration for retargeting
Cart abandonment recovery workflows
Deep funnel analytics (step-by-step drop-off)

These are legitimate needs. The honest answer is that they require tools that collect personal data and, typically, cookie consent.

A practical setup for a small shop

If you have decided privacy analytics fits your needs, here is a minimal setup:

Install Antlytics on your shop using the quick start guide. Most e-commerce platforms accept a script tag in the head.
Set a conversion goal for your order confirmation URL. This gives you a session-level conversion rate.
Add UTM parameters to any links you post externally — newsletter, social, campaigns. This segments your traffic sources in the dashboard.
Check weekly — top pages, referrers, and goal completions. That is your signal.

FAQ

Can I track "add to cart" events? Not with Antlytics's current feature set. Path-based goals work for any URL; "add to cart" is typically a JavaScript event, not a page navigation. If your shop uses a dedicated cart page URL, you could set a goal for that URL as a proxy — but it is not equivalent to event-based cart tracking.

Will I see fewer conversions than my platform reports? Possibly, because Antlytics counts sessions reaching the confirmation URL, while your platform counts completed orders. These can differ if a customer visits the confirmation page without completing the order, or if a confirmed order does not trigger a page load. Start by comparing the numbers over a month and see how closely they align.

Does this work with Shopify / WooCommerce / other platforms? Antlytics works with any platform that lets you add a script tag. See the WordPress analytics guide for WordPress/WooCommerce specifics, and check the docs for your platform. The script tag approach works on Shopify, WooCommerce, Squarespace, and most hosted shop builders.

I get heavy traffic from bots. Does Antlytics filter them? Yes — Antlytics filters known bot traffic and headless browser signatures. See bot traffic and referrer spam for details.

Can my accountant or business partner see the analytics without a login? Not currently. All dashboard access requires signing in. Team access features are on the roadmap.