Tracking enquiry events without collecting private messages
Enquiry analytics should describe the stage of the interaction using a small approved event vocabulary.
AI-assisted practical guide · Editorial approach
The useful starting point
Enquiry analytics should describe the stage of the interaction using a small approved event vocabulary. Keep names, email addresses, phone numbers and free-text messages out of general event properties. The receiving system and analytics serve different purposes and need different information.
Understand the decision
Inventory existing tracking calls and third-party scripts. Inspect whether URLs or labels can expose form details. Use controlled event names for start, attempt and accepted receipt. Apply the site's consent rules consistently. Validate the payload in a test environment and check failures and retries, not only the successful route.
A practical approach
Define each event and business state before implementing tracking. Distinguish page visits, contact clicks, form attempts, accepted enquiries and qualified opportunities. Match reports to these definitions. Test whether an interruption or retry creates duplicate events. Collect only the information needed for the agreed measurement purpose; contact details and free-text enquiry content should not be copied into general analytics events.
- Use an allowlist of event names and fields.
- Exclude contact and free-text values.
- Review URLs and third-party collection.
- Test consent, failures and retries.
Illustrative example
A contact form could emit enquiry_accepted after a matching durable receipt without attaching the person's email or message. The receiving record would retain the information needed for follow-up in its approved system. General traffic reporting would only describe the interaction stage.
A mistake to avoid
Do not put submission references into broad analytics merely because they look anonymous. Review whether they can be linked back to a private record and whether they are needed.
What to review
Audit emitted payloads and event timing, and confirm that private form content cannot enter analytics through arbitrary property values.
Turn the guide into a working brief
Write a measurement dictionary containing event names, trigger conditions, exclusions, owners and known gaps. Compare the analytics report with the receiving system for the same period and document differences rather than forcing the numbers to match. Use small experiments with a written hypothesis and one primary decision. Report uncertainty, missing consent and unavailable data plainly so the team does not mistake a partial view for complete attribution.
Common questions
What should I prepare before asking for help?
Start with this checklist: Use an allowlist of event names and fields. Exclude contact and free-text values. Review URLs and third-party collection. Test consent, failures and retries. Add your business context, existing materials and the decision you need to make. A useful initial brief can include uncertainty; you do not need to invent answers before discussing scope.
How should I judge whether the work helped?
Audit emitted payloads and event timing, and confirm that private form content cannot enter analytics through arbitrary property values. Keep the observation period and definitions visible. Use the responsible team's evidence alongside the website journey; do not attribute every change in results to one asset or article.
Sources & scope
AI-assisted practical guide. Examples are illustrative; business-specific facts and sector claims need the responsible owner’s approval.
- W3C WAI: Forms Tutorial
Reference for accessible labels, instructions and feedback. Original business examples are illustrative, not research findings or verified client results.
Use this guide to start your brief.
Share your business context, existing materials and what is still unclear. The guide title will be included so the conversation starts with the right problem.
Prefer email? Send a brief with this guide’s context.Related guides
Clicks, enquiries and qualified opportunities are different metrics
A click shows an interaction, an accepted enquiry shows confirmed receipt and a qualified opportunity shows assessed commercial fit.
Read the guide →A measurement plan before redesigning a website
A measurement plan defines the problem, intended improvement, observable events and commercial review before a redesign begins.
Read the guide →Campaign attribution when the data is incomplete
Attribution estimates which touchpoints are associated with outcomes under a particular model and available data.
Read the guide →