WordPress inquiry and order context

See where WordPress leads came from inside form emails

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.

  • Connect supported form and WooCommerce email workflows
  • Include available source, landing page, device, or recent journey context
  • Keep identity association and personal data subject to consent and policy
What it does

Understand the journey behind a submitted form or order

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.

WordPress email integration associates an eligible form submission or order email with permitted Hitsteps journey data from the same visitor context. It does not identify unrelated anonymous visits or guarantee that every submission can be matched.

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.

Available journey context

Add permitted referrer, landing-page, device, approximate location, first-visit, or recent-page signals when a valid match exists.

Consent-aware association

Associate form or order identity only when the site configuration, visitor choice, and applicable policy allow that processing.

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.

Since 2013

Maintained for real websites

Hitsteps has kept evolving across website platforms, browser changes, analytics shifts, and store workflows.

15+ install paths

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.

One workspace

From tracking hit to next action

Live dashboard, visitor profiles, heatmaps, chat, Segments, uptime, reports, and alerts stay connected after tracking is installed.

Hitsteps live dashboard with visitor activity and charts
Live dashboard
Hitsteps heatmap and page-analysis report
Heatmap context
Hitsteps live chat interface connected to visitor context
Chat workflow
Practical context

Useful context still needs a lawful boundary

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.

Supported plugins and fields can change. Test after WordPress, WooCommerce, form-plugin, theme, consent-tool, or Hitsteps plugin updates.
Workflow

How to add visitor tracking to Contact Form 7 emails

Connect the Hitsteps WordPress plugin

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.

Insert the Hitsteps Analytics form field

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.

Add the mail tag to the notification

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.

Test the journey and received email

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.

Example: a lead who read your pricing before getting in touch

This is an illustrative journey, not a real customer record. The available fields depend on the tracked visit and the context options you enabled.

An available referral source

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 pages before the inquiry

The visitor reads /services/, then /pricing/, then /contact/. Recent-page context can bring that sequence into the notification beside the submitted message.

A more useful first reply

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.

WooCommerce demo

Watch a WooCommerce order email with visitor context

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.

Recorded on 10 October 2026 with Hitsteps WordPress plugin 5.98, WooCommerce 11.2.1 and WordPress 7.1 on a local test store. The store, shopper, visitor details and email are synthetic; no real customer data was used.

What happens in the recording

  1. A shopper clicks a link in a partner's article and lands on the store's brewing guide.
  2. They open a product, add it to the cart and pay cash on delivery in the classic WooCommerce checkout.
  3. WooCommerce sends its usual New Order email to the shop's staff address.
  4. Below the order, the email shows the visitor's approximate location, network and device, the first visit's referrer and landing page, recent pages with their referrers, and a link to the visitor in Hitsteps.

Check these before you rely on it

  • In Settings > Hitsteps, keep "WooCommerce revenue and visitor context" turned on.
  • Use Hitsteps plugin 5.99 or later. It adds visitor context for both the classic checkout (the [woocommerce_checkout] shortcode) and the WooCommerce Checkout block on WooCommerce 8.2 or later. Version 5.98 and earlier add it only for the classic checkout.
  • The context is also added when the New Order email is sent later, for example after an off-site payment or when you resend it from the order screen, because Hitsteps saves the visitor with the order. Orders placed with express payment buttons on the cart or product page can arrive without it.
  • Only the staff New Order email gets this block, never customer emails. It includes the visitor's IP address and approximate location, so send it only to staff who need it.
  • Place a test order from a separate browser and check the received email.
Use cases

WordPress workflows that benefit from journey context

Lead forms

Give an authorized sales recipient available source and page context alongside a prospect submission.

WooCommerce orders

Review permitted landing-page and journey signals near an order email when the integration can associate them.

Support and contact forms

Use recent-page context to understand a submitted question, while restricting personal data to staff who need it.

Questions and answers

WordPress Email Integration FAQ

Clear answers about what this feature reports, how to use it, and where its limits are.

Which WordPress workflows can integrate with Hitsteps emails?

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.

Does the integration add personal data to every email?

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.

Why might visitor journey context be missing?

Consent choices, blockers, a different browser or device, missing tracking, caching, plugin incompatibility, or an unmatched session can prevent context from being associated.

Keep exploring

Related Hitsteps features

Connect this report with the surrounding visitor, acquisition, and workflow context.

See it on your own website

Turn wordpress email integration into a working analytics workflow

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.

Start free