Information checked: 21 July 2026.
Google Analytics 4 can show event-based website activity, but a small business should configure only what it can understand, test and use. The implementation must also fit the website’s UK privacy and cookie approach.
In brief: Implement a small, tested set of events tied to real business actions.
Minimum useful setup
- A business-owned Analytics account and property.
- One documented web data stream.
- A clear event naming plan.
- Important actions marked as key events where appropriate.
- Internal and test traffic handling.
- Consent behaviour matching the site’s privacy implementation.
- Links to Search Console or advertising accounts only when justified.
Events to prioritise
Practical events
- Lead form
- Event approach: Server-confirmed generate_lead or documented custom event; Verification: Match with received record
- Booking
- Event approach: Confirmed booking event; Verification: Match with booking platform
- Purchase
- Event approach: Purchase event with transaction identifier; Verification: Reconcile with orders and payments
- Phone or email click
- Event approach: Interaction event; Verification: Do not treat every click as a completed enquiry
- Download
- Event approach: File event with non-personal metadata; Verification: Confirm file is real and available
Privacy and consent
Depending on the technology and purpose, storage or access on a user device may require consent under PECR, alongside UK GDPR considerations. Configure the banner and tags from a documented assessment rather than assuming that all analytics is automatically essential.
Quality assurance
- Test in debug and real browsing contexts.
- Check duplicate tags and duplicate events.
- Verify cross-domain journeys where bookings or payments leave the site.
- Compare analytics with source systems.
- Document known missing data caused by consent or blockers.
- Retest after website releases.
Before you publish
Analytics is ready when key actions are reproducible, counts can be reconciled and the privacy implementation matches the documented purpose.
A common way this goes wrong
Multiple plugins or tag containers can send the same event twice. Another common issue is changing consent configuration without retesting measurement. Inspect the live requests, not only dashboard settings.
Implementation records
- Property and stream identifiers.
- Tag and event specification.
- Consent states and expected behaviour.
- Reconciliation and release-test results.
Your next action
Implement only the events required for the first release, then inspect live requests and reconcile them with source systems. Add further tracking only when a real decision requires it.
Sources and date checked
Search, product and regulatory information was checked against the following primary sources. Interfaces and policies can change, so recheck operational details before acting. Date checked: 21 July 2026.
Keep the decision under your control
Retain the relevant accounts, source material, supplier terms and recovery information. Recheck changing prices, interfaces and rules before acting.