Define the business outcome first
Before adding tags, we agree on what counts as a lead. A phone-link click, a chat conversation and an accepted form request represent different actions. A qualified opportunity requires further information from your team. A measurement plan should make those stages understandable so a report does not turn every interaction into a sale.
We also identify the dimensions that will help decisions, such as the requested service, selected market and landing page. These should be meaningful categories. Contact details and private enquiry text belong in the lead system, not in analytics event labels or page addresses.
Connect the right properties and events
The setup review checks the actual domain, property and web stream rather than relying on a familiar account name. We consider Search Console ownership, sitemap submission, GA4 configuration and the behaviour of important events. Existing tags need to be reviewed so the same action is not accidentally collected through several implementations.
For a Flor enquiry flow, the form can wait for a confirmed receipt before sending the lead event. Form attempts, chat activity and contact clicks remain separate signals. That distinction makes it easier to investigate a problem such as many attempted submissions with few accepted requests.
Keep attribution useful and proportionate
Landing-page and campaign context can help the team understand how an enquiry began. We can retain approved campaign labels and the referring website origin without copying a visitor’s entire referring URL or private search text. The plan should explain what is collected, where it is stored and which choice controls optional analytics.
Consent, browser restrictions and the difference between an event and a business record mean the systems may not match perfectly. We review those limitations with the report rather than treating every discrepancy as missing revenue. The lead system remains the place to confirm that a particular enquiry was received.
Use the report to make the next decision
A useful review combines Search Console queries and pages, consented website activity, confirmed enquiries and follow-up feedback. We ask whether the traffic fits the business, whether visitors can find the next step and whether the resulting conversations match the intended service area and scope.
The outcome should be a short set of actions with a reason for each. That might mean clarifying a service page, improving a mobile form or narrowing a location description. We preserve a record of meaningful site changes so future reviews can compare outcomes with the work actually completed.
Sources & further reading
Reviewed 2026-11-05. Guidance is adapted to your business and current platform requirements.