Last updated:
TL;DR
Originally published: 15 June 2022. Reviewed: 15 October 2026.
A service business usually needs to know which pages bring suitable enquiries, where visitors get stuck and whether enquiries become worthwhile customers. Collecting more personal information does not automatically answer those questions. Start with the decision, then identify the least information needed to support it.
First-party data is information collected through your own relationship with a visitor or customer, such as an enquiry, purchase or survey response. That label does not establish permission for every use. Browser behaviour, settings and tool purposes vary, so a single prediction about the end of third-party cookies is a poor basis for a measurement plan.
Start with three decisions
- Which service needs attention? Review relevant landing-page search data and the questions customers ask. Many impressions may indicate demand, unsuitable searches or a page that needs a clearer offer. 2. Does the enquiry route work? Check the form, confirmation and inbox delivery. A button click is not proof that a message arrived. 3. Are the enquiries suitable? Ask the person handling them to record outcomes such as suitable, outside coverage, unrelated or duplicate. A submitted form is not a sale.
If a repair page attracts enquiries outside the service area, clearer coverage information may help more than another tracking tool. If messages never reach the inbox, fix delivery before interpreting low enquiry counts as a content problem.
Inventory what is actually collected
List forms, analytics, advertising tags, embedded videos, booking tools, CRM connections and server logs. Inspect the fields, identifiers, recipients and settings in use. Check whether URLs or event parameters accidentally contain names, email addresses or message text. A vendor’s default configuration is not an inventory of your site.
Keep enquiry content in the system used to respond to customers. A reporting event can often use a page category and an action name instead of copying the message into analytics. Separate a request for a reply from a request to receive marketing; explain each purpose clearly.
Check permissions against the purpose
The ICO storage and access guidance was finalised on 29 April 2026 after changes under the Data (Use and Access) Act. Its exceptions guidance allows narrowly defined statistical use to improve a service, subject to conditions including clear information and a simple, free objection route. It does not exempt advertising, profiling or individual tracking. If an exception does not fit, obtain consent before the relevant storage or access. When personal data is involved, assess the separate UK GDPR requirements.
Review the actual tool configuration and provider use before selecting a consent or exception route. Calling a tool first-party, cookieless or server-side does not by itself settle that assessment. A privacy or legal specialist can help resolve uncertain cases; this measurement plan does not certify compliance.
Keep a small measurement record
This is a hypothetical planning example, not this website’s configuration or a recommended retention period. Complete the permission and retention decisions before enabling collection.
| Field | Example record to complete |
|---|---|
| Event | Repair enquiry confirmation |
| Purpose | Check whether the repair page’s enquiry route is used |
| Information collected | Page category and event name; exclude email, phone and message text from the analytics event |
| Permission or exception basis checked | Record reviewer, date, configured purpose and whether consent or a specific exception applies; do not assume eligibility |
| Retention and access | Name the roles needing access, set a justified retention period and record how deletion is checked |
| Validation | Test that the event fires only at the intended step and respects the visitor’s choice |
Store customer records needed to answer enquiries separately from aggregate content reporting. Document whether data is shared with a provider, what that provider may do with it and who can change the configuration.
Test the choices as well as the numbers
Check the page before a choice, after acceptance, after rejection or objection and after a later preference change, as applicable. Inspect the requests and storage that actually occur. Confirm that a form or purchase records the intended action once and does not leak its contents into unrelated tools. Repeat relevant checks when adding a plugin, embed or advertising integration.
Compare reports with the records the business uses to handle enquiries. Note missing permissions, blocked requests, duplicate events and attribution gaps. Do not fill those gaps by claiming every customer came from the last page or channel recorded.
Turn the review into a content decision
Choose one page and one question: does the page explain coverage, help customers choose a service or make the enquiry step clear? Record what changed, when and the outcome you can observe. Search data, aggregate behaviour and customer feedback can inform that decision without building a profile of every visitor.
Useful next reads are the local SEO reporting guide and the SEO resource hub. For help checking measurement alongside website improvements, describe the site and the decision you need to make.
