GA4 counts every form view as a lead
- What we'd do
- Event design with form_start and generate_lead carrying form IDs; key events only on submit
- What moves
- Gap between GA4 key events and CRM leads down, form views no longer counted as leads
Map business actions to Google's recommended events, such as generate_lead, begin_checkout and purchase, in a tracking plan. Mark only true business outcomes as key events, and register needed parameters as custom dimensions.

Good GA4 setup services begin with a written tracking plan, so each event maps to something the business cares about instead of whatever a plugin fires by default. This page is for marketing and product teams whose GA4 counts form views as leads, double-counts purchases when a thank-you page reloads, or disagrees with the order system. We audit the current property, write a specification and dataLayer, build it in Google Tag Manager, then validate against real orders or CRM records. We train your team so it survives the next release, and report key event match, unassigned traffic share and parameter completeness. The GA4 setup cost depends on site complexity, the number of platforms and any BigQuery export.
Many GA4 properties in India sit in a freelancer's or former agency's Google account, which means the business cannot add users, change settings or recover history when that person moves on. Part of our GA4 setup services is moving ownership to a Google account your company controls, with administrator access held by at least two named people on your side. Agencies, including us, get the lowest role that lets them do the job.
We also set up simple governance: a naming convention for events and parameters, a change log recording who changed what and why, and a rule that new events go into the tracking spec before they go into Tag Manager. That way the property stays understandable after the next developer, agency or marketing hire.
GA4 is most useful when it talks to the rest of your stack. Linking it to Google Ads lets key events and audiences flow into bidding and remarketing, and lets you compare paid traffic with what happened on the site. Linking Search Console brings organic queries and landing page data alongside behaviour, which helps our Search and Content team see which pages bring visitors who go on to convert.
For lead businesses, the gap between a form fill and a sale lives in the CRM. We pass a lead ID with each lead event so CRM outcomes can be joined back to GA4 data in BigQuery or reporting tools. Your sales pipeline then informs which campaigns and pages actually produce customers, not just enquiries.
If you have an Android or iOS app as well as a website, GA4 can collect both into one property through Firebase, so you see journeys that start on one and finish on the other. The work is in agreeing shared event names and parameters across platforms, so a purchase on the app and a purchase on the site report the same way.
App tracking needs your mobile developers more than web tracking does, because events are coded into each release rather than changed in Tag Manager. We write the event spec for them, test builds with Firebase DebugView before release, and check app store versions after launch, since old app versions keep sending old events until users update.
A clean property is wasted if nobody looks at it. GA4's standard reports suit quick checks, but most teams need a short dashboard built around their own funnel and primary metric. We build these in Looker Studio over GA4 or BigQuery, with a page for leadership showing outcomes and trends, and pages for channel owners showing the detail they act on each week.
Explorations are set up for the questions that recur, such as funnel steps by device or the paths that lead to a purchase, and saved in shared folders. We also define audiences for remarketing and analysis, such as cart abandoners or repeat buyers, so the Performance Marketing team can use them without asking for a new build each time.
The same problems appear again and again. Separate properties for each subdomain split one customer journey into several. Staging and test sites send data into the live property and inflate numbers. Internal staff and call-centre traffic is not filtered. WhatsApp, SMS and email links carry no UTM parameters, so a large share of visits arrives as direct or unassigned.
Other mistakes are in settings rather than tags: wrong time zone or currency, enhanced measurement firing form events that duplicate custom ones, and key events marked on page views rather than real outcomes. Each is quick to fix once found, but left alone they distort every report and every bidding decision that relies on the data.
What happens, how long it takes, what you get and what we need from you.
Configuration, events, data quality
You get: Audit
We need: GA4 and GTM admin access
Spec, dataLayer, GTM, settings; most common failure: custom dimensions registered after launch, so earlier data never appears in reports
You get: Implemented setup
We need: Developer for the dataLayer
QA, reconciliation, training
You get: Sign-off and documentation
We need: Team time for training
Noida coaching marketplace on Next.js, GTM in place, GA4 installed by a freelancer
Every metric has a formula, a target, a source and a reporting rhythm.
| Metric | How it's calculated | Target | Source | Cadence |
|---|---|---|---|---|
| Key event match | GA4 key events ÷ backend outcomes, same timezone and dates | Rule of thumb: within 10% of CRM leads or backend orders; investigate any week outside that | GA4 + CRM or backend | Weekly |
| Unassigned share | Unassigned and (not set) sessions ÷ total sessions | Set from audit; drive it down | GA4 traffic acquisition report | Weekly |
| Parameter completeness | Key events carrying all required parameters ÷ total key events | Complete on every key event | BigQuery export or Explorations | Monthly |
| Data freshness | Hours from event to availability in standard reports | Within GA4's documented processing times | GA4 | Monthly |
The manual work we take out of this service, and the tools we use.
No personally identifiable information in GA4; configure retention and access controls.
Analytics on identifiable users needs notice; minimise what you collect. Main duties apply from 13 May 2027.
We track: Google Analytics Help: What's new, Google Tag Manager release notes.
Review which key events import into Google Ads and as what.
Indian sites with European visitors need v2 consent signals.
Recommended events unlock built-in reports
Mapping to recommended events, documented custom ones
Gateways can break sessions and steal credit
Cross-domain setup, unwanted referral list
Specs survive staff changes
Event table, parameters, triggers, owners
Every engagement is tied to one business metric, tracked before and after over a set period. Named case studies with figures follow as clients approve publication.
All workTracked as patient enquiries, before and after, over a fixed period
Performance Marketing →Tracked as site visits booked, before and after, over a fixed period
Product Engineering →Tracked as hours saved per month, before and after
AI & Automation →Tracked as price premium or repeat rate, before and after
Brand & Positioning →Tracked as organic demo requests, before and after
Search & Content →Tracked as qualified leads in launch month, against plan
Launch & Go-to-Market →Longer answers to the questions buyers research before they hire anyone.
All guidesStraight answers from the practice lead. Highlighted text marks Red Balloon figures we confirm before publishing.
Some shortfall against the backend is normal; a large or sudden gap usually means a bug. Consent refusals, ad blockers, duplicate tags, gateway redirects, time zones and data thresholds all create gaps.
At most 14 months of event-level data for explorations on GA4 standard. Export to BigQuery if you need longer history, raw events or joins with CRM and cost data.
GA4 setup cost depends on the number of sites, subdomains and apps, how many events and funnels need to be tracked, whether developers have to build a dataLayer, the payment and booking flows involved, and whether BigQuery export, CRM joins and dashboards are included. An audit and fix of an existing property is usually lighter than a full rebuild. A Growth Audit or scoping call gives you a fixed quote.
Yes. GA4 setup services in India have to handle a mix of platforms. On Shopify, we work with its customer events and checkout limits. On WordPress and WooCommerce, we replace plugin defaults with a planned dataLayer. On custom builds in frameworks such as Next.js or React, we write the dataLayer spec for your developers, including route changes in single-page apps, which plugins often miss.
A paid two-week Growth Audit covers your funnel, ads, site, tracking and automation gaps, and ends with a 90-day plan you can run with or without us. The fee is credited against your next engagement.
Prefer to talk? Call +91 97114 48083, or email info@redballoon.in.
A person from the team replies to every enquiry.