Action key
hitsteps.trackAction('signup');
hitsteps.action('signup');
Actions documentation
Track custom Actions with JavaScript
Understand the custom key/value Actions your visitors take, from product interactions to the events your team sends.
- See the volume of custom Actions over complete days.
- Discover which events and values are most common.
- Open the visitors behind a selected Action.
hitsteps.trackAction(
key, value, dimensions);
JavaScript API
Track custom Actions with JavaScript
After your normal Hitsteps tracking code has loaded, send an Action when the interaction happens:
Calling trackAction records one custom Action and does not add a pageview.
Action key + Value
hitsteps.trackAction('cart_category', 'clothes');Custom dimensions
hitsteps.trackAction('checkout_started', 'pro', {
plan: 'pro',
returning_customer: true
});An optional third argument can attach configured Custom Dimensions to the same Action when Custom Dimension collection is enabled.
Use a stable Action key up to 64 UTF-8 bytes. The optional value can be up to 255 UTF-8 bytes.
trackAction returns true when the Action beacon is queued and false when tracking is disabled or the input is invalid.
Use stable, descriptive keys and consistent values so reports and Segments remain useful over time.
What it does
Actions Explorer
Actions record visitor interactions that pageviews cannot describe, such as adding a product to a cart, reaching 50% of a video, or choosing a plan.
Action keys
The key is required and the value is optional.
Action activity over time
Totals include complete account-local days wholly inside your selected and retained range; partial boundary days are excluded.
Top keys and values
Discover which events and values are most common.
Pagination · Previous page · Next pageVisitor drill-down
Open the visitors behind a selected Action.
Segment
A Segment includes visitors who matched its conditions during this report period. Their Actions in the selected period are then counted. Multiple Action key/value conditions remain correlated to the same visitor.
Export visible CSV
Top keys and values · Events · Visitors · Last seen
Value
An exact empty Action value is shown correctly here, but cannot be saved as a Segment because a blank Segment value means “any value.”
Segment and conversion context
Goals and Funnels open their own reports; this page does not infer Action-to-conversion attribution. Explorer history never Segments alerts.
Product proof
Understand your visitors. Take action with confidence.
Use it when you need live visitor context, practical installation routes, and action tools around the traffic you already have.
Maintained for real websites
Hitsteps has kept evolving across website platforms, browser changes, analytics shifts, and store workflows.
Works where your site already lives
WordPress, Shopify, Wix, Google Tag Manager, HTML, CMS, commerce, browser, and desktop setup paths are documented from one hub.
From tracking hit to next action
Live dashboard, visitor profiles, heatmaps, chat, Segments, uptime, reports, and alerts stay connected after tracking is installed.
Practical context
The key is required and the value is optional.
Do not send passwords, payment-card data, authentication secrets, or unnecessary personal data in Action keys, values, or dimensions.
Actions follow the same consent, browser, network, tracker availability, and retention boundaries as other browser analytics.
Workflow
Actions documentation
Tracking Code
After your normal Hitsteps tracking code has loaded, send an Action when the interaction happens:
Action key
Use stable, descriptive keys and consistent values so reports and Segments remain useful over time.
Action activity
New Custom Actions continue to be recorded and are already filterable in Recent Visitors.
Visitor drill-down
Open the visitors behind a selected Action.
See it on your own website
Start free
Track custom Actions with JavaScript
After your normal Hitsteps tracking code has loaded, send an Action when the interaction happens: