Worked example

A clicked button is not a confirmed enquiry

Illustrative scenario and demonstration data. Not Broad Promo client results or a performance promise.

Contact clicks
140
Validated submissions
56
Confirmed records
52
Illustrative example data
EventIllustrative countMeaning
Contact button clicks140Intent to open or start contact
Validated form submissions56Submission passes the form checks
Confirmed enquiry records52Destination system records an enquiry

These events are constructed and use different definitions. The four-submission gap calls for reconciliation; it does not by itself prove lost leads. Deduplication, rejected records and delayed delivery should be investigated.

What matters for web traffic analysis

Website analytics helps explain how people arrive, what they encounter, and whether they complete useful actions. Reliable analysis starts with event definitions and implementation checks. Page views alone do not reveal buying intent, and browser or consent restrictions can leave gaps. Combine traffic data with form delivery, CRM outcomes, and practical usability review. Treat correlations as clues to investigate rather than automatic proof of causation.

Find the cause before choosing the fix

Find out when the problem began and what changed around that time. Check website updates, targeting, offers, spending, and how enquiries are handled. Test the basics first: a broken form can look like a campaign problem. Compare similar periods and groups of visitors instead of relying on one headline number.

Choose the most likely explanation and decide how to test it. Make one controlled change where possible, record it, and gather enough data to assess the result. If several things have to change at once, be clear that you may not know which one made the difference. Focus on what helps customers and the business, not simply on improving a dashboard figure.

A practical checklist

  1. Define the important journeys and completed actions on the website.
  2. Verify event collection, campaign tagging, and duplicate handling.
  3. Compare traffic sources, landing pages, and devices using consistent periods.
  4. Check form delivery and lead quality against customer records.
  5. Investigate changes alongside releases, campaigns, and seasonal demand.
  6. Prioritize improvements and measure their effect after implementation.

Use this checklist to see what is working and what needs attention. Start with the most important change before taking on more work. Record what you change so you can understand the results later.

How to assess the results

Review relevant sessions, completed forms or bookings, qualified enquiries, and customer outcomes. Segment carefully when sample sizes are small. Bot traffic, internal visits, missing consent, and implementation changes can distort trends, so document the collection method before interpreting a rise or fall.

What to include in your brief

Share access to analytics, what your events measure, recent website changes, campaign tags, and verified enquiry records. Explain which part of the visitor experience is affected and when the problem began. Agree how consent choices will be tested, what data may be missing, and whether the project includes making and checking the fixes.

Ask for a proposal explaining what is included, what your team needs to provide, who owns the work, and what it costs. Agree when you will review progress. Broad Promo can help you plan the services you need and explain how they fit together, with the details confirmed before work begins.

Further reading

Google Analytics: understanding events