Understand what shoppers do from product view through checkout, then reconcile that journey with authenticated orders, payments, and refunds.
Ecommerce Analytics appears as Commerce in your website dashboard.
Browser Commerce events explain shopping behavior. A verified store provider supplies orders and revenue.
Yes—the Hitsteps browser tracker carries browser Commerce events after your storefront integration sends them. Ordinary pageviews alone do not reveal products, carts, checkout steps, or orders.
Product and list views, cart changes, checkout steps, item context, and a provisional purchase signal.
This source receives authenticated order facts from Shopify, WooCommerce, your own store server, or another verified billing system. Ordinary pageviews never create verified orders or revenue.
Orders, status changes, items, discounts, tax, shipping, payments, and refunds when the connected source supplies and verifies them.
Open Commerce from your website dashboard to review Overview, Orders, Products, Cart & Checkout, Acquisition, Customers, and Data Quality & Setup.
Orders, products, journeys, acquisition, and customers use one audited Commerce truth layer.
Orders, status changes, items, discounts, tax, shipping, payments, and refunds when the connected source supplies and verifies them.
Product reports include provider lines and active audited item corrections. They pause when any matching order has incomplete item coverage.
Cart and checkout funnels, product journey context, visitor timelines, and Commerce Segments. Detected cart abandonment can also become a durable system Action.
Immutable order-time attribution, order-time Custom Dimensions, and exact saved Segment membership use the selected report period.
Anonymous orders stay separate. Hitsteps never invents one customer per unlinked order. First-time versus repeat uses the earliest retained verified order.
Data Quality & Setup is a retained site-wide health view. Report dates, currency, and Segments do not change these diagnostics.
Control Commerce retention, reporting defaults, privacy behavior, and verified collection for this website.
Provider facts stay immutable. Every customer correction is a separately provenanced, reversible audit entry. Reports, exports, Segments, and visitor cards use the same effective-value layer.
Choose your store platform
Install the normal Hitsteps tracking code on the storefront.
Connect the browser Commerce events for your platform:
Connect Shopify, WooCommerce, or your custom store. Collection begins only after the provider is verified and enabled.
After setup is ready, enable the data collection switch and save these settings.
Hitsteps enrolls the installed app’s storefront Commerce event bridge for this website.
Hitsteps-assisted setup checks permission to read current orders, verifies the required webhooks, and compares one specific test order between your store and Hitsteps.
Hitsteps confirms that your official plugin includes Commerce support and connects it to this website.
Use the Commerce-capable official Hitsteps plugin with credentials provisioned for this website. Hitsteps then checks that one new test order and its refund arrive correctly.
Call the tracker Commerce methods when each shopper interaction happens.
Your developer sends signed server events that can be retried safely, using credentials provisioned for this website.
On a custom storefront, call the Commerce methods after the normal Hitsteps tracker has loaded.
var items = [{
product_id: 'product-42',
variant_id: 'blue-medium',
sku: 'TSHIRT-BLUE-M',
name: 'Classic T-shirt',
category: 'Clothing',
quantity: '1',
currency: 'EUR',
unit_amount: '29.900000'
}];
hitsteps.trackProductView(items[0]);
hitsteps.trackItemListView(
{ reference: 'summer-collection', name: 'Summer collection' },
items
);
hitsteps.trackCartChange(
'add',
{ reference: 'cart-8f3a' },
items
);
hitsteps.trackCheckoutStep(
'start',
{ reference: 'checkout-8f3a' },
items
);
hitsteps.trackPurchaseSignal('order-1042', 'journey-checkout-8f3a');Ask Hitsteps to provision site-scoped credentials before your server sends signed Commerce events.
Your developer sends signed server events that can be retried safely, using credentials provisioned for this website.
Verified server collection for custom stores
HTTPS POST · JSON · HMAC-SHA256
Hitsteps Commerce
After activation, place a new test order and issue a refund. Confirm the order, items, payment state, refund, currency, visitor linkage, and coverage status.
Collection starts only after you enable the source and save. Disabling it creates a visible data gap; re-enabling never fills missed activity.
Use it when you need live visitor context, practical installation routes, and action tools around the traffic you already have.
Hitsteps has kept evolving across website platforms, browser changes, analytics shifts, and store workflows.
WordPress, Shopify, Wix, Google Tag Manager, HTML, CMS, commerce, browser, and desktop setup paths are documented from one hub.
Live dashboard, visitor profiles, heatmaps, chat, Segments, uptime, reports, and alerts stay connected after tracking is installed.
Browser Commerce events exclude customer email, phone, address, card details, and checkout secrets. Hitsteps privacy and opt-out controls still apply. Changing this policy requires your current password and affects future erasure requests.
Each lane starts forward-only from its verified coverage date. Enabling collection never imports older orders.
Browser data describes behavior, not financial proof. It never creates verified orders, revenue, payments, or refunds.
Provider orders still count when no browser journey can be linked; they appear as unlinked instead of being discarded.
Provider facts stay immutable. Every customer correction is a separately provenanced, reversible audit entry.
Tell support which website and store platform you use. Never include payment credentials, provider secrets, or customer data in a support message.