GA4 setup checklist: from property settings to clean data
This GA4 setup checklist covers what a Google Analytics 4 property needs before you can trust its numbers: a tracking plan, correct property settings, well-designed events, consent handling, platform links and a validation routine. Installing the tag takes minutes. Getting data that matches your orders and CRM leads takes deliberate set-up.
Work through the sections in order. Each one lists the settings to check and the mistakes we see most often, such as form views counted as leads, purchases double-counted on page reloads and payment gateways taking credit for sales.
Google changes GA4 limits and features from time to time, so we note where each fact comes from and when we checked it.
1. Write a tracking plan before touching GA4
A tracking plan is a simple table that maps business actions to GA4 events. It stops the property filling up with whatever a plugin fires by default, and it survives staff changes. Agree it with marketing, sales and the developer who will implement it, then treat it as the specification.
| Business action | GA4 event | Key parameters | Key event? |
|---|---|---|---|
| Lead form submitted | generate_lead | form_id, lead_type, value | Yes |
| Form started | form_start (or custom) | form_id | No |
| WhatsApp or call click | Custom, e.g. contact_click | method, page_type | Depends on lead quality |
| Product viewed | view_item | items array, currency, value | No |
| Checkout started | begin_checkout | items, value, coupon | No |
| Order placed | purchase | transaction_id, value, currency, items | Yes |
| Account created | sign_up | method | Depends on model |
Use Google's recommended event names wherever one fits, because recommended events feed GA4's built-in reports. Keep custom names short, lowercase and consistent. If you want a second pair of eyes on the plan, our GA4 setup services start with exactly this document.
2. Account and property settings
- Create the account under a company-owned Google account, and give agencies their own user access rather than shared logins.
- Set the reporting time zone and currency (INR for most Indian businesses) to match your store or CRM, so daily totals reconcile.
- Check data retention. Google's help centre lists 2 or 14 months for standard properties; choose 14 unless you have a reason not to.
- Define internal traffic by IP and activate the filter once you have tested it, so staff visits stop inflating numbers.
- Add payment gateways such as Razorpay, PayU or Cashfree to the unwanted referrals list, so returning shoppers are not credited to the gateway.
- Configure cross-domain measurement if journeys span several of your domains, such as a site and a separate booking engine.
- Decide on Google signals and reporting identity deliberately, and record why.
- Review user access every quarter and remove people who have left.
Retention deserves a note. Google's help centre says the retention setting only affects explorations and funnel reports, not standard aggregated reports. If you need long-run, event-level history, plan a BigQuery export, covered in section 7. Changing retention later applies to data you still hold, but it cannot bring back explorations data that has already expired, so set it on day one.
4. Events, parameters and key events
Design events within GA4's limits from the start. As of November 2026, Google's help centre lists these limits for standard properties: event names up to 40 characters, up to 25 parameters per event, parameter values up to 100 characters for most parameters, and 25 user properties. Configuration limits allow 50 event-scoped and 25 user-scoped custom dimensions, and 50 custom metrics. The configuration limits page lists 30 key events per property.
Register every parameter you will report on as a custom dimension before launch. Data collected before a dimension is registered does not appear against it in standard reports, which is one of the most common and least reversible set-up mistakes. Avoid registering high-cardinality values such as user IDs or order IDs as dimensions.
Mark only true business outcomes as key events. Google renamed GA4 conversions to key events; a conversion now means a key event that you use to measure and bid in Google Ads. Counting page views or form starts as key events makes reports look healthy while telling bidding algorithms to chase the wrong action.
5. E-commerce and lead tracking details
For stores, implement the e-commerce event sequence with a consistent items array: view_item_list, view_item, add_to_cart, begin_checkout, add_payment_info and purchase. Send currency and value on every monetary event. Fire purchase once, from the order confirmation, with a transaction_id; GA4 uses it to drop duplicates when a thank-you page reloads.
For lead generation, fire generate_lead only after a successful submission, not on button click, and include a form identifier. Store GA4's client ID, UTM values and click IDs with each lead in your CRM so you can later match leads to revenue. When phone and WhatsApp matter, track clicks in GA4 but judge them against call logs or CRM records, because a click is not a conversation. Our conversion rate optimisation work depends on this data being right.
6. Consent and privacy
Google's policies prohibit sending personally identifiable information, such as email addresses or phone numbers, to Google Analytics. Check URLs, page titles and event parameters for names, emails and phone numbers, which often leak through form redirects and search parameters. Switch forms that use GET to POST, strip personal data from site search terms, and use an internal ID rather than an email address if you send a user ID.
Set up consent mode if you use a consent banner. Google updated consent mode in late 2023 with two parameters, ad_user_data and ad_personalization, and requires consent signals for users in the European Economic Area to use measurement and personalisation features. For Indian traffic, India's DPDP Act requires notice and consent for processing personal data, with the main duties under the 2025 Rules applying from May 2027, so it is sensible to build consent handling now.
7. Integrations: Google Ads, Search Console and BigQuery
- Link Google Ads and import only the key events you want to bid on, as conversions, with the right primary or secondary setting.
- Link Search Console so organic query and landing page data sit beside GA4 behaviour data.
- Link Merchant Center if you run Shopping or Performance Max campaigns.
- Turn on the BigQuery export for raw, unsampled event data you control.
- Connect your reporting tool, such as Looker Studio, and agree one shared dashboard for marketing and sales.
Know the BigQuery limits before you rely on them. Google's help centre lists a daily export limit of 1 million events for standard properties; the streaming export has no volume limit but is best-effort and adds BigQuery cost. For campaign bidding, consider adding server-side events alongside GA4; our server-side tracking explainer covers when that is worth it.
8. Validate, reconcile and maintain
- Walk every key journey with GTM preview and GA4 DebugView open, confirming each event fires once with the right parameters.
- Submit test leads and test orders and trace them through to the CRM or order system.
- Compare a week of GA4 purchases or leads with your backend, in the same time zone; investigate large or sudden gaps.
- Watch the share of Unassigned and (not set) traffic, and fix the UTM or tagging gaps behind it.
- Add tracking checks to your release process, so a site update cannot silently break events.
- Document the setup and keep the tracking plan current.
Some gap between GA4 and your backend is normal, because of consent choices, ad blockers and browser limits. A large or sudden gap usually means a bug. If you would rather have this checklist run against your property, our GA4 setup and audit service starts with a tracking audit, and the Growth Audit, a two-week paid diagnostic whose fee is credited to the next engagement, covers tracking alongside your funnel, ads and automation.