GA4 Analytics

GA4 Setup Checklist for Small Business Websites

5 min read. Practical guidance from the Hope Digitals team.

Practical and specificNo hype or guarantees
GA4 Analytics5 min read

Most GA4 problems we see in audits were created on day one. A property gets created in a hurry, a tag gets pasted into the site, and nobody revisits the settings. Months later the reports include the owner's own visits, the data window is shorter than anyone expected, and checkout traffic from a second domain shows up as a brand new session.

This checklist walks through the setup in the order we would do it on a new small business website. Each step takes a few minutes, and together they give you a property you can trust before you start making decisions from the numbers.

Start with the property and the right account structure

Create the Google Analytics account under a Google login that the business owns, not a freelancer's personal email. If an agency or developer sets things up, add them as a user instead of making them the owner. Losing access to your own analytics history because a contractor moved on is one of the most common and most avoidable problems.

Inside the account, create one GA4 property per business or brand. Set the reporting time zone and currency correctly during creation, because the currency affects revenue reporting and the time zone affects how days are split. Choose the industry category and business size honestly, since these feed some benchmarking and default settings.

  • Use a business-owned Google account as the primary owner
  • Add agencies and staff with the lowest role they need
  • Set time zone and currency before collecting data
  • Name the property clearly, such as "Company Name Website"

Create the web data stream and confirm enhanced measurement

A data stream is the pipe that carries data from your site into the property. For a website, create a web stream using the exact primary domain. GA4 gives you a Measurement ID that starts with G-. You can place it with the Google tag directly, or deploy it through Google Tag Manager, which is our preference because it keeps every tag in one place.

Once the stream exists, open the enhanced measurement settings. These automatically record page views, scrolls, outbound clicks, site search, file downloads and some video engagement without extra code. Review each toggle. A brochure site may want downloads and outbound clicks, while a site with no search box can leave site search off.

After publishing the tag, check the Realtime report while you browse your own site in another tab. If your visit appears, the tag is firing. If you use a platform such as WordPress or Shopify, confirm the tag is not being added twice by both a plugin and a theme setting, which inflates page views.

Set data retention to the longest option

In Admin, under Data collection and modification, open Data retention. For standard properties GA4 offers 2 months or 14 months for event data. The default is 2 months, and it only affects Explorations and some user-level data, not the standard aggregated reports. Even so, a 2 month window means you cannot build a year over year exploration or look back at how a funnel behaved last season.

Change event data retention to 14 months and leave the option to reset on new activity enabled. It costs nothing and cannot be applied backwards, so do it the day the property is created.

Filter out internal traffic and known noise

Your team visits the site constantly: checking edits, testing forms, placing test orders. Those visits look exactly like customers unless you tell GA4 otherwise. The process has two parts.

  1. In the web data stream, open Configure tag settings, then Show all, then Define internal traffic, and add the public IP address or range for each office.
  2. In Admin, open Data filters, find the Internal Traffic filter, and set it to Testing first so you can verify it in DebugView or Explorations.
  3. Once you are sure it behaves, change the filter state to Active. Active filters permanently exclude matching data, so do not skip the testing step.

Remote staff on changing home IP addresses are harder to cover. For them, consider a test mode habit: use GA4 DebugView, or install the Tag Assistant companion, so test visits are visible and separable. Also open the list of unwanted referrals in the same tag settings area and add payment processors or booking tools that send customers back to your site, otherwise they can appear as a referral source and break attribution.

Handle cross-domain journeys before they bite

Many small businesses send visitors to a second domain for part of the journey: a hosted booking system, a donation form, or a separate checkout. If both domains are not configured together, GA4 treats the handoff as a new session starting from a referral, and the original source such as Google Ads or organic search is lost.

In the data stream's tag settings, open Configure your domains and list every domain involved. Then test by clicking through from the main site to the second domain and checking that the URL picks up a linker parameter beginning with _gl. This matters for business websites with outside booking tools and for organizations using external giving platforms, which we often see on church websites.

If you have visitors from the European Economic Area, the UK, or other regions with consent rules, your tags may need to respect a consent banner. Google's Consent Mode lets tags adjust their behavior based on whether a visitor accepted analytics or advertising storage. GA4 can then use modeling to fill some gaps, although modeling has eligibility requirements and is not a full substitute for consented data.

Even for a US-only business, check state privacy requirements and your own privacy policy. Disable data collection features you do not need, such as Google signals if you have no use for it, and never send personal information like email addresses or names into GA4 through page URLs or event parameters. Google's terms prohibit it.

Finally, link the property to your advertising account and to Search Console while you are in Admin. A GA4 setup and reporting engagement usually covers all of these steps in one pass, but the checklist above is simple enough to work through on your own.

Key takeaways

  • Own your property with a business Google account and add others as users.
  • Switch event data retention to 14 months on day one, because it cannot be applied backwards.
  • Test the internal traffic filter before making it active.
  • List every domain in the cross-domain settings if any step of the journey happens elsewhere.
  • Decide how consent will be handled before launch, not after an audit.
FAQs

Questions We Hear Often

Standard aggregated reports are not limited by the retention setting. Event data used in Explorations is kept for either 2 months or 14 months on standard properties, and the default is 2 months, so most owners should change it to 14.

No. You can add the Google tag directly. Tag Manager is helpful once you want to track forms, calls and buttons, because you can add and edit those tags without changing site code each time.

No. GA4 only records from the moment the tag starts working. Older Universal Analytics data is no longer processed, so the earlier you set up the property correctly, the sooner you build a usable history.

Want Help Putting This Into Practice?

Get a free audit and we will show you the quickest wins for your campaigns, tracking or website.

EmailFree Audit