---
title: "Ecommerce Revenue Analytics in HitKeep | HitKeep"
description: "Track revenue, orders, products, audience location, network context, and attributable purchase sources in HitKeep with a GA4-inspired ecommerce event model."
canonical: "https://hitkeep.com/guides/analytics/ecommerce/"
---
# Ecommerce Revenue Analytics in HitKeep
HitKeep’s ecommerce analytics page is designed to feel familiar to teams coming from GA4 without importing GA4’s complexity wholesale. You track a small canonical set of ecommerce events, HitKeep stores them in the same tenant-isolated analytics database as the rest of your traffic data, and the dashboard turns them into revenue, order, product, source, city, provider, and ASN reporting.
Revenue KPIs, revenue-over-time, top products, attributed sources, and checkout audience context on the Ecommerce page.
## What HitKeep Ecommerce Tracking Is
HitKeep ecommerce is:
- **GA4-inspired**: the canonical event names are `view_item`, `add_to_cart`, `begin_checkout`, and `purchase`
- **event-based**: no separate orders table or catalog service is required
- **self-hosted**: ecommerce data lives in the same per-team analytics storage as the rest of your site analytics
- **filterable**: the Ecommerce page respects the same date range and audience filters you already use across HitKeep
HitKeep ecommerce is **not**:
- a shopping cart
- an inventory backend
- a payment processor
- full GA4 ecommerce parity
The current ecommerce surface focuses on clean reporting for web revenue events: revenue, orders, average order value, checkout conversion, top products, revenue by source or campaign, and checkout audience aggregates for city, provider, and ASN.
## Canonical Event Model
Use these event names going forward:
- `view_item`
- `add_to_cart`
- `begin_checkout`
- `purchase`
### view_item
Use this when a visitor views a product detail page, pricing modal, or other product-specific surface.
```
window.hk?.event?.('view_item', {
item_id: 'pro-plan',
item_name: 'Pro Plan',
category: 'subscription',
price: 79,
currency: 'USD',
});
```
### add_to_cart
Use this when a visitor explicitly adds an item, plan, or add-on to a cart or draft order.
```
window.hk?.event?.('add_to_cart', {
item_id: 'team-seat-pack',
item_name: 'Team Seat Pack',
category: 'add-on',
quantity: 2,
price: 49,
currency: 'USD',
});
```
### begin_checkout
Use this when the checkout step actually begins, not when a visitor merely lands on a pricing page.
```
window.hk?.event?.('begin_checkout', {
checkout_id: 'chk_01js8c9z4m',
value: 177,
currency: 'USD',
items_count: 3,
coupon: 'SPRING25',
items: [
{ item_id: 'pro-plan', item_name: 'Pro Plan', quantity: 1, price: 79 },
{ item_id: 'team-seat-pack', item_name: 'Team Seat Pack', quantity: 2, price: 49 },
],
});
```
### purchase
This is the event that powers revenue reporting.
Required fields:
| Field | Type | Required | Notes |
| --- | --- | --- | --- |
| transaction_id | string | Yes | Unique order or invoice identifier |
| value | number | Yes | Gross order value in the selected currency |
| currency | string | Yes | ISO currency code such as USD, EUR, GBP |
Recommended fields:
| Field | Type | Why it matters |
| --- | --- | --- |
| items | array | powers top-products reporting |
| items_count | number | improves summary reporting |
| coupon | string | allows coupon analysis later |
| tax | number | helpful for finance sanity checks |
| shipping | number | useful if you sell physical goods |
Example:
```
window.hk?.event?.('purchase', {
transaction_id: 'ord_01js8ca7j4',
value: 177,
currency: 'USD',
items_count: 3,
coupon: 'SPRING25',
tax: 0,
shipping: 0,
items: [
{ item_id: 'pro-plan', item_name: 'Pro Plan', quantity: 1, price: 79 },
{ item_id: 'team-seat-pack', item_name: 'Team Seat Pack', quantity: 2, price: 49 },
],
});
```
## Recommended items Shape
Each entry in `items` should use this shape:
```
{
"item_id": "pro-plan",
"item_name": "Pro Plan",
"quantity": 1,
"price": 79
}
```
Supported optional item fields:
- `item_category`
- `category`
HitKeep uses the `items` array for product aggregation. If `items` is missing, HitKeep falls back to top-level item fields such as `item_id` and `item_name`, but `items` is the format that preserves one or more products per order.
## Migration Compatibility
HitKeep accepts a small compatibility layer during ingestion and reporting so migrations are less brittle.
Accepted event aliases:
- `product_viewed` → `view_item`
- `checkout_started` → `begin_checkout`
- `order_completed` → `purchase`
Accepted property aliases:
- `order_id` → `transaction_id`
- `amount` → `value`
- `product_id` → `item_id`
- `product_name` → `item_name`
These aliases are supported to make migrations easier. The canonical contract remains the four GA4-inspired event names above.
## Browser Tracking Example
```