GA4 Setup Checklist for Business Websites: 12 Things to Configure Before You Trust the Data
By AdsZeno · Published 2026-07-15 · Updated 2026-07-15
A step-by-step GA4 setup checklist for business websites: property settings, data streams, Google Tag Manager, key events, internal traffic filters, Google Ads linking, consent and the reports that actually matter.
Start with the property, not the tag
Create one GA4 property per business website, set the reporting time zone and currency to match where you operate, and set data retention to 14 months (the maximum for standard properties) so you can compare year on year. Add a single web data stream for your domain and enable enhanced measurement, but review what it turns on — automatic form_submit and file_download events are convenient and are also a common source of noise.
Decide now who owns the property. GA4 access should sit with the business, not an agency or freelancer, with editors added as needed. If an agency created your property under their account, ask for it to be moved or for admin access to be granted to you.
Deploy GA4 through Google Tag Manager
Install GA4 via a Google Tag Manager container rather than hard-coding the gtag snippet. GTM lets you add Google Ads, Meta and other tags later from one place, test every change in Preview mode before publishing, and version your tracking so you can roll back. Use a Google tag (configuration) that fires on all pages with send_page_view enabled — unless you have a single-page app, in which case send page views manually on route changes.
Adopt a naming convention from day one: 'GA4 – Event – generate_lead', 'Trigger – Form Success – Contact'. Six months later, a tidy container is the difference between a ten-minute fix and an afternoon of archaeology.
Define key events (conversions) deliberately
GA4 calls conversions 'key events'. Mark only business outcomes as key events: enquiry form success, phone click, booking completed, purchase. Use Google's recommended event names where they fit — generate_lead, purchase, sign_up — because downstream integrations and reports expect them. Add parameters that make analysis useful later, such as the form name or the service enquired about.
Do not mark automatically collected events like scroll, click or session_start as key events. They inflate conversion counts, pollute Google Ads imports and tell you nothing about revenue.
Filter internal traffic and spam
Define your office and home IP addresses as internal traffic under the data stream's tag settings, then activate the internal traffic filter in Data settings → Data filters (it starts in testing mode). Add an 'unwanted referrals' list for payment gateways and your own domains so sessions are not split or misattributed when users return from a checkout provider.
If you see sudden bursts of traffic from odd locations with 100% engagement or zero engagement, check for referral spam or bot traffic. GA4 excludes known bots automatically, but new ones appear; a hostname check in explorations will often confirm whether hits are even reaching your real domain.
Link Google Ads and Search Console
Link GA4 to Google Ads in Admin → Product links. This lets you import key events as conversion actions, share audiences for remarketing and see Google Ads campaign data inside GA4. Enable Google signals only after reviewing your privacy obligations — it improves cross-device reporting but is a data-sharing decision.
Link Search Console as well: the organic queries and landing pages report shows which searches bring people to each page, which is the foundation for any content or SEO work.
Consent, privacy and data quality
If visitors come from regions with consent requirements, implement consent mode so GA4 tags adjust their behaviour to the user's choice, and make sure your privacy policy describes the analytics you run. Turn on IP anonymisation considerations where relevant (GA4 does not log IP addresses in reports) and avoid sending personal data — names, emails, phone numbers — in event parameters or page URLs.
Check for personally identifiable information leaking through query strings, such as email addresses appended to thank-you URLs by form plugins. If it happens, strip or hash the parameter before it reaches GA4.
The reports that matter for a business website
Most owners need four views: acquisition by channel (where visitors come from), landing pages with key events (which pages generate enquiries), the key events report itself (how many leads, by source and campaign), and a simple funnel exploration from landing to form success. Build these as saved explorations or a Looker Studio dashboard and review them monthly alongside your ad platforms.
Finally, validate before you trust anything: use DebugView while completing the real journeys on your site, confirm each key event fires once with the right parameters, and compare GA4 key events against actual enquiries received for a few weeks. If the numbers disagree, fix tracking first — every decision downstream depends on it.
Related AdsZeno services
- Conversion Tracking
Understand what really works.
- Account Audit
Find the opportunities you're missing.