Analytics and audit logs
The admin keeps the current carts and wishlists, a short visitor log, daily traffic counts, and an audit log. It keeps this as an operational record, without a charting suite or a multi-year archive.
Carts, wishlists, and visits
Users → Carts and Users → Wishlists display the items people have saved. A wishlist belongs to an account's saved list and stays separate from the visitor event log.
Acquisition → Visitor Sessions is the visit log in chronological order. Open a session to see page navigation and the actions below. Signed-in visitors show an account email. Anonymous traffic is labeled as guests. You can attach a private note to a session.
| What is recorded | Examples |
|---|---|
| Pages and actions | Page views, product views, searches, add to cart, remove from cart, checkout starts, banner clicks, and clicks that leave for an external checkout. |
| Where they came from | Traffic source, referrer, campaign name, and referral code. |
| Environment | Device, region, and browser language. |
UTM
The storefront reads standard campaign parameters from the landing URL and stores them with the visitor session. No third-party analytics script is required.
| Parameter | What it identifies | Examples |
|---|---|---|
utm_source | The traffic source | google, newsletter, instagram |
utm_medium | The channel | cpc, email, social |
utm_campaign | The campaign | spring_sale, black_friday |
The first values seen on that browser are kept on the visitor session for the life of the visitor cookie (365 days) and copied onto the raw events. Acquisition → Visitor Sessions shows them as source, medium, and campaign. Acquisition → Overview groups daily counts by campaign name (utm_campaign). Source and medium stay on the session.
Daily counts
Acquisition → Overview rolls raw events into daily counts: page views, product views, blog views, add to cart, checkout starts, internal searches, and campaigns. The same screen summarizes traffic sources from the visitor sessions in the selected period.
A scheduled job builds yesterday's metrics in the store's timezone. Aggregate today previews the current day and can be run again.
Week, month, and quarter totals add up daily unique visitors. The same person is counted again on each distinct day, so these longer totals are approximations.
Data retention
| Record | Kept for |
|---|---|
| Raw sessions and events | 90 days. This includes page actions and the UTM values. |
| Daily counts | 120 days after each store day. |
| Audit log | 90 days. |
These windows are the kit defaults. Change them in the source when your operations need a different period. For multi-year history, copy the logs into your own data warehouse or BI system.
Audit log
System → Audit Logs records operator and system actions. Operators cannot edit these entries. The log includes:
- Order status changes and payment status updates
- Shipments, fulfillment, and payout decisions
- User role and access changes
- Administrator sign-ins
- System configuration changes
Sensitive values, secret keys, and credentials are redacted before they are stored.
Next step
That covers operations: import, store settings, the catalog, orders, marketing, and this log. Continue to Local sandbox when you want to run the store on your own machine.