Measurement guide 02
Make sure your business owns the Google Analytics 4 (GA4) property, the tag is installed once, and each important action is counted once. At setup, check data retention, consent settings, and links to Search Console and Google Ads. Keep a short log of changes so a tracking fault is not mistaken for a change in customer demand.
← All measurement and analytics guidanceConfirm access
Check settings
Install once
Test collection
Keep a change log
Why this matters
An analytics report can look precise while tracking the wrong site, counting actions twice, or missing the pages where customers contact you. Small businesses feel these errors more: a few staff tests can look like a busy day, and a broken contact-page tag can hide real inquiries. Before comparing marketing channels, confirm what is being collected and who can fix it.
Hypothetical example: page views jump from 400 to 800 after a site update, but the inquiry inbox stays flat. A test visit shows two page_view events per page. Removing the duplicate trigger fixes it, and the owner notes the affected dates instead of claiming doubled demand. A short change log makes this kind of fault easy to spot.
Responsible practices
A named person at your business should hold administrator access through an account the business controls. Give agencies and freelancers their own logins instead of sharing a password. Before creating a new property, check whether one already exists. A second property splits your history without fixing the original problem.
Confirm the property's time zone, currency, website address, and measurement ID, and write them down. Then open Admin, Data retention. Standard properties can keep user-level and event-level data for 2 months or 14 months. This affects Explorations and funnel reports, not standard reports. Check which is selected at setup; 14 months allows year-over-year exploration.
List every place a tag could live: the website builder's analytics field, plugins, code snippets, and Google Tag Manager. Choose one. Then use Tag Assistant and GA4 DebugView to walk through home page, service page, contact page, and one labeled test inquiry. Each page and action should appear once. Repeat on a phone.
Google's EU user consent policy requires consent from visitors in the European Economic Area (EEA), the UK, and Switzerland before Google measurement and ad features use their data. Consent mode (version 2) passes your cookie banner's answers to Google tags. In basic mode, tags wait for consent. In advanced mode, tags load first and send cookieless signals when consent is declined, so GA4 can estimate the gap.
Define internal traffic, then leave the filter in Testing until you confirm it only matches staff. An active filter permanently removes matching data. Separately, check page addresses, titles, and event details for names, emails, or phone numbers. Google prohibits sending personally identifiable information to Analytics. Use fixed labels such as contact_form instead.
In GA4 Admin, link your Search Console property so search queries sit beside site behavior. You need Editor access in GA4 and verified-owner status in Search Console; a web stream links to one Search Console property. If you advertise, link Google Ads too. That lets key events be used as Ads conversions and shares ad click details with GA4.
GA4 setup
Record the owner, backup contact, property ID, measurement ID, website domains, and where the tag is installed.
List existing tags and plugins with whoever maintains the site, and choose one installation path.
Confirm time zone and currency, review enhanced-measurement options, and check the data-retention setting.
Decide whether you need consent mode, and see the privacy and cookie consent guide for your banner and policy.
Run the same home-to-contact test on a computer and a phone, and confirm each event appears once.
Test the internal-traffic filter before activating it, and check URLs and event details for personal data.
Link Search Console and Google Ads, then note the date in a change log you review after every site update.
Avoid these failures
Collection, attribution, qualification, bookings, costs, and revenue depend on technical, customer, operational, and platform factors outside any provider's control. Results are not guaranteed.
Questions business owners ask
Usually not. Get business access to the existing property and keep using it if it still fits. If you do start over, note the date of the break and keep access to the old data.
Google's EU user consent policy applies to visitors in the EEA, the UK, and Switzerland. If you have few or none, it may not apply, but US state privacy laws can still affect your cookie banner. Check the privacy and cookie consent guide and confirm with a qualified attorney for your situation.
DebugView shows events right away; standard reports take longer to process. Confirm the property, date range, and filters, then check the report again a day or two later instead of sending more tests.
No. People call without visiting the site, decline cookies, switch devices, or book offline. Aim for consistent, understandable numbers. Keep analytics totals separate from your phone and form records, and investigate large gaps.
Primary guidance
Make the numbers trustworthy