Setting up GA4 properly: what a small business needs on day one

Fibvo editorial · 6 August 2026 · 5 min read

Most small business websites have GA4 installed. Far fewer have it set up. The tag went in when the site launched, nobody changed the settings, and a year later the reports show your own office as a top location, an enquiry count that does not match the inbox, and explorations that stop two months back. None of this is a fault in GA4. It is what the defaults do when nobody touches them. Here is what we check first.

Get the property basics right

In the property settings, set the reporting time zone to India and the currency to Indian rupees, unless you report in another currency for a clear reason. A wrong time zone shifts late-evening enquiries into the next day, so GA4 and your CRM disagree for no good reason.

Next, confirm the tag loads on every page, including thank-you pages and any landing pages built on a separate tool. Open the Realtime report and visit the site from your phone. If customers leave your site to pay through a payment gateway and then return, add the gateway's domain to the list of unwanted referrals in your web stream's tag settings. Without that, the gateway is recorded as the source of the returning visit and the channel that really brought the customer loses the credit.

Choose key events that reflect real business

GA4 now calls conversions key events. Google Ads still says conversions, which is why the two terms get mixed up. A key event should be an action with commercial value. Take a freight forwarder whose site has a quote form, a click-to-call button and a WhatsApp link. Its key events are short and plainly named.

• quote_request, counted when the thank-you page loads, not when someone presses submit
• phone_click, counted on any link starting with tel:
• whatsapp_click, counted on any link to wa.me or api.whatsapp.com

Leave page views, scrolls and engaged sessions off the list. They help diagnose problems but they are not outcomes, and marking them as key makes every report look healthier than the business is. Do not count enquiries with the form interaction option in enhanced measurement either, as it can record submissions that never reached your inbox.

To build quote_request, go to Events in Admin and create an event whose conditions are event_name equals page_view and page_location contains your thank-you path. Phone and WhatsApp clicks are easier to set up reliably in Google Tag Manager. Once each event has fired at least once, mark it as a key event. Marking is not retroactive, so earlier occurrences will not be counted.

Keep your own team out of the reports

Staff open the website all day, test the forms and look up the ads. Excluding that traffic takes two steps, and the second one is often missed.

• In the web stream's tag settings, define internal traffic by adding the public IP addresses of your office and branches. Matching visits are tagged with a traffic_type value of internal.
• In Admin, open Data filters. The internal traffic filter starts in Testing, which labels the data but keeps it in reports. Confirm it catches a test visit, then switch it to Active.

An active filter removes matching data permanently, so test before you switch. IP filtering will also miss some visits. Many broadband connections change IP address, and staff on mobile data will not match any rule. For people who work on the site daily, installing Google's Analytics opt-out browser add-on in their work browser closes most of the gap.

GA4 records what you told it to record, from the day you told it, and nothing before that.

Extend data retention before you need it

By default, GA4 keeps event-level data for two months. Standard reports use aggregated data and are not affected, but explorations are. Those are the custom tables, funnels and path analyses you build yourself. With two months of history you cannot compare this festive season with the last one, or study how enquiries moved across a financial year.

In Admin, under Data retention, change event data retention to 14 months, the longest option on a standard property. The change applies from that point forward. If you need longer detailed history, link the property to BigQuery, which exports raw events into a Google Cloud project you control. Storage and queries beyond the free allowance are billed.

Link Google Ads and Search Console

Both links live in Admin under Product links. They put ad clicks and search queries next to on-site behaviour.

For Google Ads, you need edit rights on the GA4 property and administrative access to the Ads account. After linking, confirm auto-tagging is on in Google Ads so each click carries its campaign detail into GA4. Then choose one source for each conversion. You can import GA4 key events into Google Ads or use the Google Ads tag directly. If both record the same enquiry, set one as the primary conversion action and the other as secondary, or bidding will optimise towards a doubled count.

For Search Console, you need to be a verified owner of the property. Link it to your web data stream, then open the Library in the Reports section, find the Search Console collection and publish it. Until you do, the reports stay hidden. Once published, you can see which queries and landing pages bring organic visitors alongside what those visitors did next.

When all of this is done, keep a short change log: what was changed, by whom and on what date. Anyone reading the reports later will need to know which figures can be fairly compared.

---

Written by Fibvo — Bengaluru and Erode, India — working with clients in other time zones. Questions, or think we have it wrong? Tell us.