Supported plugin workflows
Use the Hitsteps field in Contact Form 7, Gravity Forms, or Ninja Forms to add context to supported notifications. WooCommerce also has a supported order-email integration; each workflow needs its own setup and test.
Bring the available referral source, landing page, and recent page history into the form notification your team already reads. Hitsteps connects supported Contact Form 7, Gravity Forms, Ninja Forms, and WooCommerce email workflows with a matched visitor journey, subject to your tracking and privacy settings.
A form email says what the person submitted. When the integration can make a permitted match, analytics context can also show how that visit reached the site and which tracked pages preceded the action.
Use the Hitsteps field in Contact Form 7, Gravity Forms, or Ninja Forms to add context to supported notifications. WooCommerce also has a supported order-email integration; each workflow needs its own setup and test.
Add permitted referrer, landing-page, device, approximate location, first-visit, or recent-page signals when a valid match exists.
Associate form or order identity only when the site configuration, visitor choice, and applicable policy allow that processing.
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.
Add only the visitor information needed for the receiving team to handle the inquiry or order. A convenient email is not a reason to collect or distribute unnecessary personal data.
Install and activate Hitsteps Web Analytics from Plugins > Add New. Open Settings > Hitsteps, enter the API key for this website, and verify a visit from a separate browser. If administrator tracking is excluded, use a logged-out test visit.
Edit the Contact Form 7 form and use its Hitsteps Analytics tag generator to insert the hidden analytics field. Choose which visitor details to include: the field offers separate controls for visitor details, viewed pages, visit history, and the more-information link.
Open the form's Mail tab and add [hitsteps_analytics] to the Message body where the visitor context should appear, then save. Use the staff notification sent to authorized recipients; keep extra visitor context out of customer autoresponders unless it is appropriate for that recipient.
In a separate browser, follow your normal consent flow, open a landing page and two relevant pages, then submit a test inquiry. Check that the received email contains the expected available history. If context is missing, verify the API key, inserted form field, mail tag, tracking match, and cache before relying on it.
This is an illustrative journey, not a real customer record. The available fields depend on the tracked visit and the context options you enabled.
The visitor follows a link from partner.example to your services page. If the browser supplies the referral and tracking runs, that source can provide context for the inquiry.
The visitor reads /services/, then /pricing/, then /contact/. Recent-page context can bring that sequence into the notification beside the submitted message.
Your team can review the pricing page before responding and ask a relevant follow-up question. The page path shows what was viewed; it does not prove the visitor's budget, intent, or reason for contacting you.
A one-minute recording from a disposable test store. A synthetic shopper follows a partner link, reads a guide and buys through the classic WooCommerce checkout. The shop's New Order email then arrives with the visitor details the released Hitsteps plugin adds.
Give an authorized sales recipient available source and page context alongside a prospect submission.
Review permitted landing-page and journey signals near an order email when the integration can associate them.
Use recent-page context to understand a submitted question, while restricting personal data to staff who need it.
Clear answers about what this feature reports, how to use it, and where its limits are.
Hitsteps has supported Contact Form 7, Ninja Forms, Gravity Forms, and WooCommerce order email workflows. Confirm current plugin compatibility and versions before relying on a production integration.
No. Available fields depend on the submission, tracking match, configuration, consent, and applicable policy. Configure only the data your organization is permitted and needs to process.
Consent choices, blockers, a different browser or device, missing tracking, caching, plugin incompatibility, or an unmatched session can prevent context from being associated.
Connect this report with the surrounding visitor, acquisition, and workflow context.
Create a free account, install the Hitsteps tracking code, and confirm your first visit before choosing the plan that fits your traffic and reporting needs.