Service — Analytics & tracking

Numbers your decisions can stand on.

GA4, Tag Manager, server-side signals and WhatsApp-era conversion tracking implemented, verified and documented — because every marketing decision downstream is only as good as the measurement underneath it.

Who this is for

Businesses making real budget decisions on numbers they quietly distrust — duplicate conversions, mystery traffic, platforms that each claim the same sale.

  • GA4 was 'migrated' in 2023 and nobody has trusted it since
  • Meta, Google and your CRM report three different realities
  • Most of your leads arrive by WhatsApp or phone — and your analytics can't see them
  • You're about to scale ad spend and need the instruments calibrated first
  • An agency reports conversions your bank account cannot corroborate

The problems it solves

What this fixes.

Conversions that lieDuplicate events, test submissions counted, button clicks dressed as leads. Platforms optimise toward whatever you count — counting wrong trains them wrong.
The WhatsApp blind spotIn Malaysia, the highest-intent action on most sites is a WhatsApp tap — and default setups don't see it. We track message starts, calls and form fills as first-class conversions.
Attribution civil warEvery platform claims the sale. Without one source of truth and honest UTM discipline, budget meetings become theology debates.
Consent-era signal lossBrowser privacy and ad-blockers eat client-side pixels. Server-side events and Conversions API recover the signal — implemented properly, not bolted on.

Scope

What's included.

IncludedTracking auditEvery tag, trigger and event tested against reality: what fires, what duplicates, what's missing, what's fiction.
IncludedGA4 implementationProperty configured around your business events — enquiries, calls, WhatsApp, purchases — not the default noise.
IncludedTag Manager architectureA documented GTM container humans can maintain: naming conventions, folders, versioning, no tag spaghetti.
IncludedServer-side & Conversions APIMeta CAPI and server-side tagging where spend justifies it — cleaner signal to the platforms doing your bidding.
IncludedCall & WhatsApp trackingClicks, message starts and where feasible call outcomes wired into the same measurement spine.
IncludedDashboards & documentationA Looker Studio view answering your actual questions, plus a measurement plan document your next hire can operate.

Measurement is the foundation everything rents

There is a moment in every audit when the room goes quiet: the tracked conversions and the actual enquiries in the inbox refuse to match. Sometimes double; sometimes half. Every budget decision made on those numbers — every “winning” campaign scaled, every “failing” channel cut — inherited that error silently.

That’s why we treat analytics as infrastructure, not reporting decoration. The measurement plan comes before the tools: what, precisely, is worth counting for this business? A verified enquiry. A connected call. A WhatsApp conversation that starts. A purchase net of refunds. Then GA4, Tag Manager and the platform APIs get built to that plan — and then comes the step that separates setups that work from setups that exist: verification. Real form fills, real taps, real transactions, traced end-to-end until the numbers agree with reality.

Built for the market you actually sell in

Default analytics assumes customers convert in tidy browser forms. Malaysian customers tap WhatsApp. High-ticket buyers call. B2B deals close in CRMs weeks later. Our implementations treat those paths as first-class citizens — which regularly rewrites the story of which marketing was working all along. Attribution stops being a black hole labelled “direct,” and the platforms doing your bidding (Google, Meta) finally learn from signals that mean money.

Everything ships documented, in your accounts, verifiable by anyone — the same transparency spine as our shared SEO rank tracking. Instruments you can trust, then decisions worth making: optimisation that isn’t astrology, scaling that isn’t gambling.

The engagement

How the work runs.

01Audit & measurement planCurrent state tested; the events that matter to the business written down first.
02ImplementGA4, GTM, pixels and server-side wiring built to the plan.
03Verify end-to-endReal submissions, real taps, real purchases traced through every system.
04Document & handoverThe setup explained in writing — owned by you, operable without us.
05MonitorTracking decays as sites change; optional monitoring catches breakage before bad data breeds bad decisions.
Week 1Audit and measurement plan agreed.
Weeks 2–3Implementation and end-to-end verification.
Optional ongoingMonitoring retainer; tracking reviewed as the site and stack evolve.

Measurement

The numbers we watch.

Event accuracyTracked conversions reconciled against inbox/CRM reality — the definition of the whole job. We aim for boringly close.
Attribution coverageShare of conversions with known source — UTM discipline and server-side signal shrink the 'direct/unknown' black hole.
Signal match qualityCAPI event-match quality and dedup rates decide how well platforms learn from your data.
Data freshness & breakageTracking rots quietly when sites change. Monitored setups fail loudly instead — the good kind of failure.

Watch-outs

Mistakes we see often.

Optimising before measuringRunning CRO or scaling ads on broken data optimises noise. Instruments first, then decisions — it's cheaper in every timeline.
Counting button clicks as leadsA click on 'Submit' is not a submission; a form fired twice is not two customers. Verification against reality is the step most setups skip.
GTM as a junk drawerYears of vendor snippets, duplicate pixels and orphan triggers slow the site and corrupt the data. Containers deserve architecture, not accumulation.
Ignoring consent designPDPA and GDPR-era tracking needs consent handling that's honest without nuking your data quality. It's a design problem — we design it.

Know the difference

Implementation is not campaign management.

This service builds and verifies the measurement layer — the instruments. Campaign management (our performance marketing, Google Ads and Meta services) flies the plane using those instruments. Agencies that do both without separating them end up grading their own homework on data they configured. We keep the disciplines distinct precisely so the numbers stay trustworthy — and everything is implemented in YOUR accounts, auditable by anyone you hire after us.

Questions

Asked before you ask.

Our GA4 shows different numbers from Google Ads and Meta. Which is right?

Possibly all of them, by their own rules — different attribution models, windows and counting methods measuring different things. The fix isn't picking a favourite; it's a measurement plan that defines one source of truth per question, plus reconciliation so you know WHY numbers differ. Once that's in place, the platform reports become useful instruments instead of competing propaganda.

What does a proper tracking setup include?

A written measurement plan (events that matter, named and defined), GA4 configured to it, a clean documented GTM container, ad-platform pixels with server-side reinforcement where spend justifies it, call/WhatsApp conversion wiring, and — the step everyone skips — end-to-end verification with real actions traced through every system. Plus documentation, because a setup only you understand is a liability.

Do we really need server-side tracking / Conversions API?

It scales with your spend. Under modest budgets, well-implemented client-side tracking usually suffices. Once media spend is significant, recovered signal from CAPI and server-side tagging measurably improves platform optimisation and reporting — the maths starts paying for the plumbing. The audit gives you the threshold reasoning for your case rather than a blanket upsell.

Can you track WhatsApp leads properly?

Yes — click-to-chat taps as conversion events with full source attribution, distinguished by page and placement, flowing into GA4 and back to ad platforms. Where the WhatsApp Business API is in play, conversation starts become trackable outcomes too. For Malaysian businesses this single fix often reveals that 'mystery' campaigns were quietly your best performers.

Will consent banners and PDPA ruin our data?

They change it; ruin is optional. Honest consent design, first-party data discipline and appropriately configured modelling keep decision-quality data flowing while respecting the law. What actually ruins data is pretending 2019 still exists — we build for the privacy era you're operating in.

Is this a one-time project or ongoing?

The build is a project with a defined end: implemented, verified, documented, handed over. Decay is the ongoing risk — site edits break triggers, platforms deprecate APIs, new tools arrive untagged. Optional monitoring catches that early; some clients bundle it into a wider retainer, others self-maintain with our documentation. Both are legitimate.

Next step

Ready when you are.

Tell us what you're building and where you want it to grow. We reply within one business day with an honest read — no sales sequence.