How to set up GA4 so the numbers mean something
Configure a GA4 property with named key events clean referrals and the right retention settings so your reports answer questions about your business.
Installed is not the same as set up
The tag is live. Reports are filling with users sessions engagement rate and average engagement time. None of it answers whether last month's enquiries came from search or from the Instagram campaign. The property is collecting data correctly and measuring nothing you decided to measure.
A GA4 property out of the box records page views and a handful of automatic events. Everything connecting those events to your business is configuration you have to supply. That gap is perhaps a day of deliberate work.
What it costs and what sits outside the setup
GA4 excludes several things people assume it covers. It is not a CRM and it will not tell you which enquiry became a customer unless you feed that back yourself. It is not a consent solution. It does not fix a website with no measurable actions on it. It also does not backfill. Data missing because the property was misconfigured in March is gone and no later change recovers it.
The platform is free at the volumes an Indian small or medium business generates. Costs appear only if you export to BigQuery where Google charges for storage and queries. The spend is effort. Expect a few hours for a brochure site and a longer exercise for a commerce site with a payment gateway. Vibence publishes a fixed scope and rate for analytics and measurement setup if you would rather not hold the configuration work internally.
Who should invest in this and who should not
Do not do this work if your website has no actions worth counting. A five page brochure site receiving a few dozen visits a month with a phone number as its only call to action gains nothing from event design. Install the basic tag and spend the attention on the phone instead.
Also wait if you are replatforming within the next couple of months. Events built on a site about to be replaced have to be rebuilt and the history will not carry across cleanly. Configure the property once on the new site rather than twice.
The work pays for itself when you spend money on more than one channel or when your website is the main route to an enquiry or an order. It is close to mandatory for ecommerce because a commerce property without proper item and purchase events cannot report what sold.
The configuration that actually matters
Start with the property settings because several of them cannot be fixed retroactively. Set the time zone to Indian Standard Time and the currency to Indian rupees before any data arrives. Raise data retention from the shorter default to the longer option available to you so year on year comparison is possible later. Switch on bot filtering and add your office addresses and your agency's as internal traffic to be excluded.
Then deal with referrals. This is the step most Indian setups miss. When a customer is sent to Razorpay or PayU or a bank page and returns to your thank you page the gateway appears as the referring source and the real campaign loses the sale. Add every payment gateway domain to the unwanted referrals list. Do the same for any separate booking or support subdomain and configure cross domain measurement where your journey spans two domains.
Now design the events. Name a small set of key events matching the definitions your team already uses. Enquiry submitted. Call button tapped. Purchase completed. Use a fixed naming convention in lower case with underscores and record it in a document. Attach only parameters you will read such as form name or plan selected. Test each event in the debug view before trusting it. Finally link Search Console so acquisition reports show more than a column of direct traffic.
How to tell the property is trustworthy
The test is reconciliation against systems that hold money. Count key events for a week and compare them against enquiries in your CRM and orders in your commerce platform. A stable and explainable gap means the property is reliable. A gap changing shape every week means a tag is firing twice or not at all.
Engagement rate and average engagement time are the flattering metrics. They move with content length and page speed and say nothing about revenue. Judge the property by whether its key event counts hold their relationship with your records.
The common mistake
The expensive mistake is leaving payment gateways and internal traffic uncorrected. Both quietly reassign credit. Gateway referrals steal conversions from the campaigns that earned them and office traffic inflates sessions on the pages your own team visits most. Decisions then get made on a map of your staff's browsing habits.
The second mistake is never defining key events at all. A property recording only automatic events will still produce full reports and that is what makes it dangerous. The numbers look complete. Six months later a budget review has no conversion data to examine and nothing can be reconstructed because GA4 does not backfill.
Write the configuration down
Keep a one page record of your event names parameters excluded referrals and retention settings. An undocumented tag container becomes unmaintainable the moment its author leaves.
Review that record once a quarter against the live property. Tags accumulate quietly and a property clean in April is rarely clean in October.
This guide explains how something works. It is not legal, tax or financial advice, and rules change. Confirm anything regulatory with a qualified professional before you act on it.