Measurement you can actually make decisions on
Analytics setup configures the measurement your decisions depend on: which events count as conversions, how they are tracked, how consent is handled, and whether the numbers reaching your reports are trustworthy. Most accounts are installed rather than configured, which is not the same thing.
Almost every business has analytics. Far fewer have analytics they trust, and fewer still have checked. The default installation records pageviews and little else, so the reports describe traffic rather than outcomes, and every decision made from them is a decision about the wrong thing.
The faults are consistent and invisible without inspection. Conversions were never defined, so the reports show sessions and bounce rate and nothing about enquiries. Tags fire twice, inflating everything. Internal traffic is not excluded, so your own team's visits are in the numbers. Cross-domain tracking is broken, so a visitor moving to a booking subdomain becomes two people. Consent is either absent, which is a compliance problem, or so blunt that it discards most of the data.
When this work makes sense
Questions worth asking any supplier
Are conversions defined, or only pageviews recorded?
Has anyone tested that the tracking fires correctly, once, for a real submission?
Is internal traffic excluded? Your own team can be a visible share of small-site numbers.
Does tracking respect consent where you operate? In the UK and EU this is enforced, not advisory.
Do phone and offline conversions appear anywhere? For many businesses they are most of the result.
Deliverables
GA4 configured with conversions defined against your actual business outcomes
Tag management implemented cleanly, with duplicate and misfiring tags removed
End-to-end verification, a real submission traced through to the report
Consent mode configured so tracking respects permission where required
Server-side tracking where browser restrictions materially affect data quality
Cross-domain tracking where visitors move between your properties
Call tracking integrated so phone enquiries appear alongside form submissions
Reporting built around the decisions you make, not the metrics that come default
Built with
Process
Every configuration is verified by submitting a real enquiry and following it through to the report. It sounds obvious and it is the step almost universally skipped. Tags are installed, the tool shows data arriving, and everyone assumes the data is correct. Tracking that fires twice or attributes to the wrong source still shows data arriving, which is why installation and verification are different jobs.
The standard nine stages, discovery, strategy, UX/UI, development, content and SEO, testing, launch, measurement and continuous improvement, apply to every project. The paragraph above is what differs for this one.
What moves the number
Pricing depends on scope, functionality, integrations and content requirements. These are the factors that change it most:
Default install, proper configuration, or server-side
Default installation
Fits: Knowing roughly how much traffic you get
Limits: No outcome measurement; unusable for deciding where to spend
Configured with conversion tracking
Fits: Most businesses, measurement tied to actual outcomes
Limits: Still subject to browser tracking restrictions and consent losses
Server-side tagging
Fits: Businesses where data loss materially affects decisions or ad optimisation
Limits: More infrastructure to run and maintain; additional hosting cost
Case studies
No published analytics case study. The output of this work is trustworthy numbers, which is difficult to demonstrate to someone outside the business.
MBGDesk operates from 4 offices in India, United States, United Kingdom, United Arab Emirates. We hold no industry certifications and do not imply otherwise.
Frequently asked questions
Why do our ad platform numbers not match analytics?
They never will exactly. Platforms count conversions in their own attribution window including view-through; analytics applies a different model and loses what browsers block. Expect platforms to sum to more than your real total, and judge spend against outcomes you can verify in your own systems.
Is GA4 enough?
For most businesses, once properly configured. The complaints about GA4 are usually complaints about a default installation that measures nothing useful. Configuration is the difference, not the tool.
Do we need server-side tracking?
If browser restrictions are materially degrading your data or your ad platforms are optimising on incomplete signals, it helps. It is more infrastructure to run, so it should follow a specific problem rather than being adopted because it sounds more robust.
How does consent affect our data?
Where consent is required and properly implemented, you lose data from people who decline. Consent mode allows modelling to partially compensate. In the UK and EU this is not optional, and analytics collected without consent is a compliance problem regardless of how useful the data is.
Can we track phone calls?
Yes, through call tracking numbers that attribute a call to its source. For many service businesses phone enquiries are the majority, and without this the reporting describes a minority of results while appearing complete.
Our numbers suddenly changed. What happened?
Common causes are a tag deployment, a consent banner change, a site migration, or a platform update to how something is counted. Annotated changes in the analytics property make this diagnosable; without annotations it becomes archaeology.
What should we actually be looking at?
The smallest set of numbers that changes a decision. Most dashboards report everything measurable, which buries the few metrics anyone acts on. We build reporting around the decisions you make rather than around what the tool offers by default.
How long should we keep our data?
Longer than the default, which is shorter than most people expect and cannot be applied retroactively. GA4's event data retention has a maximum that is well below what year-on-year comparison needs, so if you want to compare this quarter against the same quarter last year, the setting has to be raised before that data expires. It is a two-minute change that is impossible to fix later, and it is the most common regret in analytics configuration.
Services that connect to this
Talk to us about this
Tell us what you are trying to build and we will come back with scope, approach and an estimate.