Specialist service · GA4 setup services

GA4 setup & audit

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.

Performance Marketing practice: abstract red and ink artwork from the Red Balloon reel

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.

Who owns the property, and who can change it

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.

Linking GA4 to Google Ads, Search Console and your CRM

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.

Measuring your website and app in one place

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.

Reports your team will actually open

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.

Common GA4 mistakes we find in audits

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.

Where this works

Real-world situations we're built for

Illustrative · not a client
Edtech (Delhi)

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
Retail ecommerce (Jaipur)

Purchases double-counted when the thank-you page reloads

What we'd do
transaction_id on every purchase, purchase event fired on order confirmation
What moves
Duplicate purchases down, GA4 revenue gap with Shopify down; tracked as GA4-to-Shopify revenue gap before and after, over a fixed period
How a project runs

3 phases, each with a deliverable

What happens, how long it takes, what you get and what we need from you.

Audit

3–5 days

Configuration, events, data quality

You get: Audit

We need: GA4 and GTM admin access

Design and build

1–2 weeks

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

Validate and train

3–5 days

QA, reconciliation, training

You get: Sign-off and documentation

We need: Team time for training

A typical engagement

From first call to result

Illustrative · not a client

Noida coaching marketplace on Next.js, GTM in place, GA4 installed by a freelancer

Week 1AuditData retention checked first: GA4 defaults to 2 months, so set 14; then event inventory, parameters, key events, filters, cross-domainAudit
Weeks 1–2Event designRecommended event names, parameters, custom dimensions, key eventsTracking spec
Weeks 2–3ImplementdataLayer and GTM, consent, internal traffic filter, 14-month retention, BigQuery exportClean GA4 property
Week 4ValidateGA4 DebugView with GTM preview on each key event; then one week of key events compared with CRM leads, same timezoneSign-off
Where it starts60 custom events with inconsistent names, data retention left at 2 months, no BigQuery export
Where it endsThe site has a documented GA4 setup. Weekly it watches key events vs CRM, unassigned traffic share and funnel step rates.
What we measure

The numbers we report on

Every metric has a formula, a target, a source and a reporting rhythm.

MetricHow it's calculatedTargetSourceCadence
Key event matchGA4 key events ÷ backend outcomes, same timezone and datesRule of thumb: within 10% of CRM leads or backend orders; investigate any week outside thatGA4 + CRM or backendWeekly
Unassigned shareUnassigned and (not set) sessions ÷ total sessionsSet from audit; drive it downGA4 traffic acquisition reportWeekly
Parameter completenessKey events carrying all required parameters ÷ total key eventsComplete on every key eventBigQuery export or ExplorationsMonthly
Data freshnessHours from event to availability in standard reportsWithin GA4's documented processing timesGA4Monthly
Automated by default

What runs itself after launch

The manual work we take out of this service, and the tools we use.

When: DailyBigQuery exportGA4 daily or streaming exportRemoves: Keeps raw data beyond the retention setting
When: Each releaseEvent QAPlaywright tests checking dataLayer pushes in CI, plus GTM previewRemoves: Prevents broken events
When: WeeklyReport deliveryLooker Studio scheduled emailsRemoves: Everyone sees the same numbers
Rules we work to

Standards and regulations

GoogleGoogle Analytics terms of service

No personally identifiable information in GA4; configure retention and access controls.

MeitYDPDP Act 2023

Analytics on identifiable users needs notice; minimise what you collect. Main duties apply from 13 May 2027.

What's changing

Platform and policy updates that affect this work

We track: Google Analytics Help: What's new, Google Tag Manager release notes.

Google AnalyticsConversions renamed key events in GA4.

Review which key events import into Google Ads and as what.

GoogleConsent Mode v2 became required for EEA traffic using Google's ad features.

Indian sites with European visitors need v2 consent signals.

Before you hire anyone

Questions to ask any agency, including us

Will you use GA4 recommended events or custom names?

Why ask

Recommended events unlock built-in reports

A good answer

Mapping to recommended events, documented custom ones

How will you handle cross-domain journeys and payment gateway redirects?

Why ask

Gateways can break sessions and steal credit

A good answer

Cross-domain setup, unwanted referral list

Will you deliver a written tracking spec?

Why ask

Specs survive staff changes

A good answer

Event table, parameters, triggers, owners

FAQ

Questions buyers ask us

Straight answers from the practice lead. Highlighted text marks Red Balloon figures we confirm before publishing.

Why don't GA4 numbers match our orders or CRM leads?

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.

  • Razorpay, PayU or Cashfree redirects can appear as referrals and take purchase credit; add them to the unwanted referrals list.
  • Fire purchase once from the order confirmation with a transaction_id, match time zone and INR currency to the store, then compare daily purchases with the order table for a week.
How long does GA4 keep data, and should we export it to BigQuery?

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.

  • Data retention defaults to 2 months; switch it to 14 under Admin > Data collection and modification > Data retention on day one.
  • Standard properties have a daily export limit of 1 million events; streaming export avoids that cap but adds BigQuery cost.
  • In BigQuery, choose an Indian region such as asia-south1 (Mumbai) if policy prefers local storage, and set table expiry and access controls, since raw exports hold personal data.
What does GA4 setup cost depend on?

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.

  • Sites, subdomains and apps
  • Events and funnels
  • Developer work on the dataLayer
  • BigQuery, CRM and dashboards
Do your GA4 setup services in India cover Shopify, WordPress and custom sites?

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.

  • Shopify customer events
  • WordPress and WooCommerce dataLayer
  • Custom and single-page apps
Back to the service

Analytics & attribution →

Start with an audit

Ready for
lift?

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.

What do you need?
Your details are sent over a secure, encrypted connection and only used to reply to you.