To set up GA4 for lead generation and eCommerce, create one property and web data stream, raise data retention to 14 months, filter internal traffic, configure cross-domain measurement, send a short named event plan such as generate_lead or purchase, mark the events that matter as key events, link Google Ads and Search Console, then validate in DebugView.
Most GA4 problems come from a rushed install: default settings left alone, every click marked as a key event and forms that fire twice. This guide covers a clean setup, an event plan for lead-gen sites and stores, a validation checklist, common mistakes and a 30-day plan.
Key takeaways
- Change data retention to 14 months on day one; it cannot be applied backwards.
- Write an event plan before tagging: a few lead events for lead-gen sites, the view_item to purchase sequence for stores.
- Mark only real business outcomes as key events. Standard properties allow 30, and a cluttered list weakens bidding and reporting.
- Filters, cross-domain settings and consent mode decide data quality. Set them before launch.
- Validate in DebugView and reconcile with CRM or store orders weekly.
What does recent Google documentation say about GA4 setup?
The most reliable recent evidence is Google’s own documentation. First, terminology. Google’s Analytics Help page on conversions vs key events explains that events measuring important business actions “are now called key events”, while a conversion now means an action used to measure ad campaigns. The GA4 Data API changelog dates the API side of the rename to 6 May 2024, when the conversions metric was mapped to keyEvents.
Second, consent. Google’s consent mode overview (updated 30 July 2026) lists four consent types: ad_storage, analytics_storage, ad_user_data and ad_personalization. The last two are what people call consent mode v2; Google’s Google Ads EEA consent page says advertisers must collect and pass consent signals for European Economic Area users.
Third, attribution and filtering. The What’s new in Google Analytics page records that from 16 January 2026 (beta) conversion attribution settings can be adjusted per conversion, and that on 21 September 2026 Google added hostname Include filters. The chart shows standard-property limits from Google’s configuration limits page and event collection limits page, both checked in November 2026.
Selected GA4 standard-property limits (Google Analytics Help, checked November 2026)
There is room for a sensible setup, but not for registering every parameter or marking every click as a key event. Event and parameter names are limited to 40 characters.
How do you set up the GA4 property and data stream?
Create one GA4 property per business or brand, not per page or campaign. Set the reporting time zone and currency correctly at the start, because both affect daily totals and revenue. For a single website, create one web data stream.
Install the Google tag through Google Tag Manager rather than hard-coding it in the theme. GTM keeps events and consent logic in one place; our Google Tag Manager guide covers containers, triggers and versioning. Never run a plugin tag and a GTM tag together.
Give at least two people Administrator access using company accounts, not a freelancer’s personal Gmail.
Which admin settings should you change on day one?
Google’s data retention page says standard properties can keep user-level and other event data for 2 or 14 months, while 360 properties get extra options of 26, 38 and 50 months for event data. The same page states that “the data retention setting only affects explorations and funnel reports”; standard aggregated reports are not affected. Choose 14 months; the change is not retroactive.
Next, filters. Google’s data filters page lists developer traffic, internal traffic and web hostname filters, and warns that “once you apply a data filter, the effect on the data is permanent” while historical data is untouched. Define your office and agency IP ranges under internal traffic rules, start the filter in Testing state, check that the test dimension behaves as expected, then activate it. With remote teams, IP filters miss a lot, so also exclude debug traffic.
Finally, list unwanted referrals. Payment gateways (Razorpay, PayU, Stripe), booking tools and your own subdomains appear as referrals and steal credit from the real source. Google’s cross-domain measurement page warns that self-referrals “may mean that traffic to your site is being attributed incorrectly”.
What do enhanced measurement and cross-domain settings do?
Enhanced measurement collects common interactions without extra code. According to Google’s enhanced measurement events page it covers page_view, scroll (fired when 90% of the page depth is visible), outbound click, view_search_results, YouTube video_start, video_progress and video_complete, file_download, and form_start and form_submit. Treat the automatic form events as signals, not lead counts: they can fire on search boxes and failed submissions. Build your lead event on the confirmed success state; our form optimisation guide explains why thank-you states matter.
Cross-domain measurement matters when a journey crosses domains, such as a site and a separate booking or checkout domain. In Admin, open the web data stream, choose Configure tag settings, then Configure your domains and add each domain. Every domain must use the same tag ID. Google says Analytics passes user IDs in a _gl URL parameter, so check that redirects do not strip it.
Which events should lead-gen sites and online stores track?
Start from Google’s recommended events list, which includes lead-generation events (generate_lead, qualify_lead, working_lead, close_convert_lead and their negative versions) and the online sales sequence from view_item_list to purchase and refund. For stores, follow the GA4 ecommerce developer guide for the items array and required parameters.
| Business type | Event | Fires when | Key event? | Useful parameters |
|---|---|---|---|---|
| Lead gen | generate_lead | Form submission is confirmed (thank-you state or success callback) | Yes | form_name, lead_type, value, currency |
| Lead gen | phone_click (custom) | Click on a tel: link | Usually yes | link_location, page_type |
| Lead gen | whatsapp_click (custom) | Click on a wa.me or WhatsApp chat link | Usually yes | link_location, page_type |
| Lead gen | qualify_lead / close_convert_lead | CRM stage changes (imported or server-side) | Optional | lead_source, value |
| eCommerce | view_item | Product page viewed | No | items, value, currency |
| eCommerce | add_to_cart / view_cart | Item added / cart viewed | No | items, value, currency |
| eCommerce | begin_checkout / add_shipping_info / add_payment_info | Checkout steps completed | No | items, shipping_tier, payment_type, coupon |
| eCommerce | purchase | Order confirmed (once per transaction) | Yes | transaction_id, value, tax, shipping, currency, items |
Name custom events in lower case with underscores, and send one event with a parameter rather than many near-duplicates (one whatsapp_click with link_location, not whatsapp_header and whatsapp_footer). For stores in India, decide how cash-on-delivery orders are treated: fire purchase at order confirmation, then reconcile cancellations and returns, as our eCommerce KPIs guide recommends.
How do key events, custom dimensions and Google Ads conversions fit together?
A key event is any event you mark as important in Admin (see Google’s About key events page). Standard properties allow 30 key events, so mark only outcomes: leads, booked calls, purchases, perhaps sign-ups.
A conversion, in current Google terminology, is a key event you also use in Google Ads. Per Google’s conversions vs key events page, you need a linked Google Ads account to create one, and Ads conversions created from Analytics appear in the Advertising section rather than standard reports. For lead-gen bidding, import only the primary lead event as a primary conversion; our Google Ads lead generation guide explains why secondary actions should not drive bids.
Custom dimensions make your parameters visible in reports. Register only those you will use, such as form_name, lead_type or page_type. They are not retroactive, so register on day one. Never send email addresses or phone numbers as parameters.
What do you need to know about consent mode v2?
Consent mode lets Google tags adjust behaviour to the visitor’s choice. Google’s consent mode overview describes two implementations. In basic mode, tags wait for the banner choice and send nothing if the visitor declines. In advanced mode, tags load with denied defaults and send cookieless pings that Google uses for modelling.
For Indian businesses, the DPDP framework published by MeitY is being phased in; take legal advice on consent wording and record-keeping rather than copying another site’s banner. Set consent defaults in GTM before any tag fires and test each state in Tag Assistant.
Which integrations should you connect?
1. Google Ads
What: Link the Ads account in Admin under Product links and enable auto-tagging. Why: It brings cost and campaign data into GA4, allows audience sharing and lets you create Ads conversions from key events. How: Follow Google’s guide to creating Google Ads conversions from key events, and avoid counting one lead twice as primary.
2. Search Console
What: Link the verified Search Console property to the web stream. Why: You get organic queries and landing pages next to engagement and key events. How: Google’s Search Console linking page says a web data stream can link to only one Search Console property, and you need Editor rights in GA4 plus verified ownership in Search Console. Then publish the Search Console collection from the Library.
3. BigQuery
What: Export raw event data to BigQuery. Why: Raw data avoids interface sampling and can be joined with CRM or order data. How: Google’s BigQuery Export page says standard properties have a daily export limit of 1 million events, streaming export has no volume limit but costs extra, and you can export to the free BigQuery sandbox where sandbox limits apply. Turn it on early; history is not backfilled.
4. CRM and offline data
What: Bring lead quality and sales outcomes back into measurement. Why: GA4 counts form fills; the CRM knows which became revenue. How: Store the GA4 client ID and UTM values in hidden form fields so each CRM record can be matched later. Google’s offline event import page allows CSV uploads of events with a client_id, but timestamps must fall within the previous two calendar days plus today. For later sales outcomes, Google Ads offline conversion imports are usually the better route.
How should you report on GA4 data?
Use standard reports for routine checks and Explorations for questions. A funnel exploration from landing page to form view to generate_lead, or from view_item to purchase, shows where people drop out. Consistent UTM tracking is what makes the channel reports trustworthy.
For management reporting, pull GA4 into a Looker Studio dashboard alongside CRM and ad data, and choose a few metrics from our marketing KPIs guide. For attribution questions beyond last click, see the marketing analytics and attribution guide.
Two caveats confuse new users. Thresholds: Google’s data thresholds page says data may be withheld from reports that include demographics or search queries, or when user counts are low, and that thresholds “are system defined. You can’t adjust them.” Sampling: Google’s data sampling page gives a quota of 10 million events per query for standard properties, flagged by the data quality icon.
Is your GA4 setup ready to guide budget decisions?
One property, one tag, correct time zone, currency and 14-month retention.
Internal, developer and hostname filters active; unwanted referrals listed; cross-domain set.
Written event plan; 3 to 6 key events; custom dimensions registered for parameters you use.
Google Ads, Search Console and BigQuery linked; consent mode tested in each state.
Weekly match of GA4 leads or orders against CRM or store data within an agreed tolerance.
Only now use GA4 channel and campaign data to move budget.
How do you validate a GA4 setup?
Use GTM Preview, Tag Assistant and GA4’s DebugView together. Preview shows what fired; DebugView shows what GA4 received.
| Check | How to test | Pass condition |
|---|---|---|
| Single tag | Tag Assistant on key templates | One Google tag, one page_view per page load |
| Internal traffic | Visit from office IP, view test dimension | Traffic tagged as internal before the filter is activated |
| Cross-domain | Click from site A to site B | _gl parameter present; no self-referral session |
| Lead event | Submit a real test form, and a failed one | generate_lead fires once on success only |
| Calls and WhatsApp | Click tel: and wa.me links on mobile | One event each with link_location |
| Purchase | Place a test order, refresh the thank-you page | One purchase with correct transaction_id, value, currency and items |
| Consent | Accept, reject and ignore the banner | Consent states update as expected in Tag Assistant |
| Reconciliation | Compare 7 days of GA4 vs CRM or store | Differences understood and documented |
What does a worked example look like?
Consider a hypothetical B2B software firm in Pune with a WordPress site, a separate booking tool on its own domain and leads in a CRM. GA4 counts form_submit as a key event, shows the booking tool as a referrer and reports far more leads than the CRM. The fix: add the booking domain to cross-domain settings, list it as an unwanted referral, replace form_submit with generate_lead on the confirmed thank-you state, add phone_click and whatsapp_click, store the client ID in a hidden field and keep three key events. Weekly reconciliation then shows whether counts are close enough for budget decisions. This is an illustration, not a client result.
What are the most common GA4 setup mistakes?
- Leaving data retention at 2 months and discovering it when a year-on-year exploration is empty.
- Marking automatic form_submit, scroll or page_view events as key events.
- Firing purchase on every thank-you page reload, without a stable transaction_id.
- Forgetting payment gateways in unwanted referrals.
- Registering custom dimensions months after launch and expecting historical data.
- Treating GA4 lead counts as sales truth instead of reconciling with the CRM.
What is a practical 30-day GA4 setup plan?
- Days 1 to 5: audit access, tags and settings; set retention, time zone and currency; write the event plan and naming rules; agree key events with sales or finance.
- Days 6 to 12: implement events and consent mode in GTM; set internal and developer filters in Testing; add cross-domain domains and unwanted referrals; register custom dimensions.
- Days 13 to 18: validate with the checklist; activate filters; link Google Ads, Search Console and BigQuery; set up hidden fields for client ID and UTMs.
- Days 19 to 30: build funnel explorations and a Looker Studio report; reconcile weekly with CRM or store data; document the setup so the next person can maintain it.
If you want help turning clean measurement into pipeline, Bargaon’s demand generation service uses this kind of setup as the base for channel planning and reporting.
Which related guides should you read next?
- Google Tag Manager guide for containers, triggers, consent and event tags.
- UTM tracking guide for naming rules that keep GA4 channel reports clean.
- Looker Studio dashboards guide for turning GA4 data into management reports.
- Marketing analytics and attribution guide for choosing attribution models and reading them sensibly.
- eCommerce KPIs guide for the store metrics your GA4 events should feed.
Frequently asked questions
Is GA4 free for small businesses?
Yes, the standard version of Google Analytics is free. Analytics 360 is the paid enterprise version with higher limits; most SMBs never need it.
Should data retention be set to 14 months?
For standard properties, yes in most cases. The setting only affects explorations and funnel reports, but you need 14 months for year-on-year explorations.
What is the difference between a key event and a conversion?
A key event is an important action marked in GA4. A conversion is a key event that you also use to measure ad campaign performance in Google Ads. Google renamed GA4 conversions to key events in 2024.
How many key events should a lead-generation site have?
Usually three to six, such as a confirmed form lead, phone and WhatsApp clicks and booked meetings. Standard properties allow 30, but a short list keeps bidding focused.
Do I need BigQuery export?
Not on day one, but it is worth enabling early because the export does not backfill history. Watch the 1 million events per day daily-export limit for standard properties.
Why do GA4 numbers not match my CRM or store?
Consent choices, ad blockers, duplicate events, cross-domain issues and cancelled orders all create gaps. Agree a tolerance and reconcile weekly.
Sources and further reading
- Google Analytics Help: Data retention
- Google Analytics Help: Conversions vs key events
- Google for Developers: GA4 Data API changelog (6 May 2024 key events entry)
- Google Analytics Help: Configuration limits
- Google Analytics Help: Event collection limits
- Google Analytics Help: What’s new in Google Analytics (2026 entries)
- Google for Developers: Consent mode overview
- Google Analytics Help: Data filters
- Google Analytics Help: Enhanced measurement events
- Google Analytics Help: Set up cross-domain measurement
- Google Analytics Help: Recommended events
- Google for Developers: Measure ecommerce in GA4
- Google Analytics Help: BigQuery Export
- MeitY: Data protection framework
- Editorial note: the event plan, validation checklist, GA4 Readiness Ladder, worked example and 30-day plan are Bargaon editorial models, not research data or client results.
Need GA4 measurement that sales and finance trust? Bargaon’s demand generation service can plan your event model, validate tracking and connect it to channel strategy and reporting.