---
title: "Customer analytics"
description: "What your store counts about its visitors and customers on every channel, without cookies, how visitors are told apart, what is estimated and how long it is kept."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.sherpo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Customer analytics

Your store counts what its visitors and customers do, on every channel: your storefront, your own front end through the customer API, your customers' AI assistants through the customer MCP server, and feeds. It is built in and always on. It is first-party audience measurement for aggregate statistics only: it sets no cookie, stores nothing on a visitor's device, keeps no address and no lasting id for a visitor who isn't signed in, never tracks visitors across sites, and keeps no record or total for more than 13 months, so your store shows no cookie banner for it. Integrations you turn on, such as Google Analytics, are separate: one that sets cookies still waits for a visitor's consent (see [Integrations](/merchant-app/settings#integrations)).

## What is counted

- **Views**: your home page, a page, a product and a lesson or article, each time one is shown.
- **Buying**: a checkout started (for the product of its cart's first line) and a purchase completed.
- **Accounts**: sign-ins and sign-ups.
- **Files**: downloads, streams and previews of the files a customer opens through a product, and a podcast episode played from a feed. Public files, and free media anyone may play, are not counted.
- **Progress**: a lesson completed, counted once per customer.
- **Feeds**: each read of a public or a private feed.
- **Apps**: each successful call an app makes over the customer API or the customer MCP server, with the app that made it.

Each count keeps its day, its channel, the product or page it concerns and the visitor's country, as their network places them; a purchase also keeps its amount and currency. A visit's first page also keeps where the visitor came from: the referring site's host (never the full address), the `utm_source`, `utm_medium`, `utm_campaign` and `ref` tags of the link they followed, and whether they were on a phone or on a computer or tablet (unknown when the caller isn't a browser), as the user agent and mobile hint their browser sends with every request tell it.

Left out: you and your staff while your browser holds the merchant app's pass to your store (admin mode on or off), previews, and crawlers, uptime checks and other automated traffic.

The storefront counts its pages on its own. A front end of your own tells the store which pages it showed, as [Visits](/customer-api/storefront#visits) in the customer API describes.

## Visitors

A visitor is told apart only within one day: each count carries a code worked out from the visitor's network address, their browser, your store and the day, with a random key that is deleted about 26 hours after it is made (backups keep it for up to 30 days). The address and the browser are never kept, the code changes every day, and it never matches one from another store. So one person who comes back on three days counts as three visitors, and a week's visitors are each of its days' visitors added up.

A signed-in customer's counts also carry a random key linked to their account, never their name or email address, so their counts stay linked from one day to the next until the customer is deleted, which deletes the key. These figures never show what a single customer did: every one is a total.

## Estimates and exact figures

On a very busy store, the counts are sampled: views and the other counts are scaled back up, and visitors are told apart within the sample, so they may read low. A figure counted from sampled data says it is an estimate (`estimated: true`). The store's orders and a product's orders never are: they are counted from your orders themselves. A channel's orders come from the counts, as orders record no channel, so they may be estimated.

## How long it is kept

The counts are added up into daily totals once each of your store's days ends, so today shows nothing yet. Daily totals are kept for 13 months, then deleted; they relate to no visitor or customer. The individual counts behind them are kept for up to 3 months.

## Reading the figures

Open **Analytics** in the merchant app, as [Analytics](/merchant-app/analytics) describes, ask an AI assistant connected through the merchant MCP server, as in [How a launch did](/merchant-mcp/examples#how-a-launch-did), or read them over the merchant API, as [Read your traffic](/merchant-api/guides/read-traffic) describes: views and visitors by kind of page, channel, country and product, sign-ins and sign-ups, conversion from product views to checkouts started to orders, and the calls your customers' apps made.

## Telling your customers

Your storefront's privacy policy, in its **Legal** menu, already describes this analytics: what is recorded, that it uses no cookie and how long it is kept. A front end of your own counts through the same store, so say the same in its own privacy policy.

Source: https://docs.sherpo.io/overview/analytics/index.mdx
