Web & Commerce

Analytics & Tracking Setup: If Measurement Is Wrong, Everything Downstream Is Wrong

Every optimisation decision, every budget reallocation and every performance argument rests on the measurement layer. When it is wrong — and in most accounts we audit, it is wrong in at least one material way — the whole structure above it is guesswork with decimal places.

Senior specialist, not a junior You own every account 3-month minimum, then rolling
~30%Typical conversion under-reporting browser-onlyvaries by audience and device
3Material tracking errors in the median auditusually including duplicate conversions
9.2/10Achievable event match qualityafter CAPI enrichment
1Source of truthnot one per platform
What is server-side tracking and why does it matter?

Server-side tracking sends conversion and analytics events from your own server to advertising and analytics platforms, rather than relying solely on JavaScript running in the visitor's browser. It matters because browser tracking is increasingly blocked by ad blockers, privacy features and cookie restrictions, causing significant under-reporting. Server-side implementation restores a meaningful share of lost data, which improves both reporting accuracy and the quality of automated bidding.

Analytics & Tracking Setup: why it matters right now

The most expensive marketing errors we see are not bad campaigns; they are good decisions made on bad data. Duplicated conversion actions inflate performance and cause budget to flow to the wrong channel. A missing event means the algorithm optimises toward the wrong outcome. A misconfigured attribution setting makes a working channel look broken.

The technical landscape has also shifted decisively. Browser-based tracking loses a substantial share of events to tracking prevention, ad blockers and cookie lifetime limits. Server-side tagging and platform conversion APIs restore much of that signal — and because bidding algorithms optimise on the data they receive, better data directly lowers acquisition cost.

Consent adds a further layer. Consent mode, regional privacy requirements and modelled conversions all change what your reports mean. Implementing them correctly is a compliance requirement; understanding what they do to your numbers is a measurement requirement.

Key takeaways

  • Analytics & Tracking Setup is measured on platform vs backend revenue variance — not on activity.
  • The first thing we fix is audit.
  • The most common mistake we correct: multiple overlapping conversion actions.

What is included in our Analytics & Tracking Setup

Every engagement is scoped to your situation, but these are the workstreams that make up a full Analytics & Tracking Setup programme at Credex Media.

Measurement plan

A documented map of business questions to events, parameters and reports — written before any tag is deployed.

GA4 & GTM implementation

Clean property configuration, event and parameter naming conventions, enhanced ecommerce, cross-domain setup and internal traffic filtering.

Server-side tagging

Server container deployment, event forwarding to Google, Meta, LinkedIn and other destinations, with deduplication against browser events.

Conversions API & offline imports

Meta CAPI, Google offline conversion imports and CRM stage syncing so platforms optimise on qualified outcomes rather than raw form fills.

Consent mode & privacy compliance

Consent management platform integration, consent mode configuration and documentation of what is collected and why.

Attribution modelling

Model selection, lookback windows matched to your sales cycle, and blended reporting that reconciles platform claims against actual revenue.

Dashboards & reporting

Looker Studio dashboards built around decisions rather than every available metric, with data freshness and definitions documented.

Data QA & monitoring

Automated checks and alerting so a broken tag is caught in days rather than discovered next quarter.

How we deliver it

A five-stage sequence. You will know at every point what is happening this week and which number it is meant to move.

01

Audit

Every tag, event, conversion action and data source inventoried, with discrepancies between platforms quantified.

Week 1–2
02

Measurement plan

Business questions mapped to events and reports, naming conventions agreed, ownership defined.

Week 2
03

Implementation

GA4, GTM, server container, CAPI and consent mode deployed and validated against real transactions.

Week 2–5
04

Reconciliation

Platform-reported numbers reconciled against backend revenue, with the remaining gap explained rather than ignored.

Week 5–6
05

Dashboards & monitoring

Decision-oriented dashboards built, automated data quality alerts configured, documentation handed over.

Week 6–8

Analytics & Tracking Setup pricing

Published, in rupees and dollars, because "contact us for pricing" wastes everyone's afternoon. These are real starting points — the scoping call adjusts them to your situation, up or down.

One-off project

GA4 Rebuild

₹75,000

$925 one-off

One-off. Clean GA4 and GTM with a measurement plan.

  • Full tracking audit with discrepancies quantified
  • Measurement plan mapping questions to events
  • GA4 property and GTM container rebuild
  • Enhanced ecommerce and event naming conventions
  • Internal traffic filtering and cross-domain setup
  • Documentation handed over

Best for: Anyone whose platform numbers do not match their revenue.

Most popular

Server-Side

₹1,40,000

$1,725 one-off

One-off. Server container, CAPI and consent mode.

  • Everything in GA4 Rebuild
  • Server-side GTM container deployed
  • Meta Conversions API with deduplication
  • Google offline conversion imports from CRM
  • Consent mode and CMP integration
  • Reconciliation against backend revenue

Best for: Businesses spending meaningfully on paid media with browser-only tracking.

Monthly retainer

Managed

₹45,000

$550 / month

Ongoing monitoring, dashboards and data QA.

  • Automated data quality alerting
  • Looker Studio dashboards maintained
  • Monthly reconciliation to backend revenue
  • New event implementation as you ship features
  • Attribution model review
  • Quarterly measurement health report

Best for: Teams that want tracking to stay correct rather than silently break.

What is not included

Media spend (paid directly by you to Google, Meta, Amazon or whichever platform), third-party software licences, and creator or influencer fees. We never resell media or take a margin on it. Everything else needed to deliver the scope above is in the retainer.

How we measure success

These are the metrics we report on. Notice what is absent: impressions, likes, and any number that cannot be connected to revenue.

CheckAcceptance standard
Platform vs backend revenue varianceWithin 5%, and the gap explained
Duplicate conversion actionsZero
Event match quality (Meta)8.0+ out of 10
Server-side event coverageAll primary conversions
Consent mode configurationValidated in both consent states
Dashboard definition documentationEvery metric defined in writing

Is this right for your business?

We would rather tell you no on the first call than take a retainer we do not believe will work. Here is our honest read on fit.

A good fit if…
  • Your platform numbers do not match your revenue
  • You have never implemented server-side tracking
  • You are about to invest heavily in paid media
  • Nobody can say authoritatively what a conversion means
Probably not yet if…
  • You do not want to know the real numbers
  • You have no website conversions to measure
  • You need it done without any developer involvement at all

The mistakes we see most often

These are drawn from real audits. If two or more describe your account, there is meaningful upside available before anyone spends another rupee or dollar.

1. Multiple overlapping conversion actions

Counting a purchase as three conversions makes everything look profitable and misallocates budget.

2. Browser-only tracking in 2026

You are optimising bidding algorithms on roughly two-thirds of the truth, and paying for the gap.

3. Never reconciling to backend revenue

If nobody has compared GA4 to the accounting system, nobody knows whether any report is right.

4. Building dashboards with every available metric

A dashboard nobody reads is worse than no dashboard, because it creates the appearance of measurement.

5. No monitoring after implementation

Tags break on every site release. Without alerting you find out a quarter later.

Tools and platforms we work in

We work inside your accounts wherever possible, so your data and history stay yours.

Google Analytics 4Google Tag Manager (web & server)Meta Conversions APIBigQueryLooker StudioConsent management platformsSegment-class CDPsCRM integrations

Analytics & Tracking Setup — frequently asked questions

Why do Google Ads, Meta and GA4 all report different numbers?

Because they use different attribution models, different lookback windows and different definitions of a conversion. Meta credits view-through conversions Google does not count; GA4 uses its own model; each platform sees only its own touchpoints. Some divergence is expected and correct. Divergence beyond roughly 15 to 20 percent, or numbers that do not reconcile to your actual revenue, indicates an implementation problem.

Do we need server-side tracking?

If you spend meaningfully on paid media, yes. Browser-based tracking loses a substantial share of conversions to privacy features and ad blockers, and that loss degrades both your reporting and the quality of automated bidding. Server-side tagging typically recovers a large share of the gap and often pays for itself through improved bidding performance alone.

How long does a GA4 and GTM implementation take?

A standard implementation with server-side tagging and Conversions API takes six to eight weeks including audit, planning, build, validation and dashboards. A basic GA4 rebuild without server-side components can be done in two to three weeks. The variable is usually how much developer access and cooperation is available.

Is GA4 enough or do we need a warehouse?

GA4 is sufficient for most businesses under significant scale. A warehouse — typically BigQuery — becomes worthwhile when you need to join marketing data with CRM, subscription or profitability data, when GA4's sampling and cardinality limits start to bite, or when you need retention beyond GA4's default windows. We will tell you honestly which side of that line you are on.

How do you handle consent and privacy regulations?

By implementing a consent management platform integrated with consent mode, so tags fire according to the user's actual choices, and by documenting what is collected, why and for how long. We also explain what consent mode does to your reported numbers, because modelled conversions behave differently from observed ones and misreading them causes real budget mistakes.

Want an honest read on your Analytics & Tracking Setup?

Send us access and we will come back with a written audit — the real problems, ranked, with what we would do first. Yours to keep whether or not you hire us.