Analytics you can trust when you make the call.
We set up GA4, Tag Manager, and campaign tracking to ensure each enquiry, sale, and call is counted once, clearly labeled, and attributed to the correct channel. Our Lahore team builds, tests, and documents the measurement layer, so you can easily understand each metric and its limitations.
Why do analytics, ad platforms and my CRM all show different numbers?
Each tool tracks its own metrics. Ad platforms count conversions based on their clicks within a set time frame. Analytics includes only visitors who allow tracking and whose browsers do not block it. The CRM logs contacts who reached a person. These numbers will not match exactly, so aligning them is not an effective use of time. Instead, define key events, record them consistently across all systems, and regularly compare totals to actual revenue.
Google documents these gaps itself in its GA4 attribution help pages, including why modelled and observed data differ.
What gets tracked, and why it earns a place on the list.
Most accounts hold hundreds of events nobody uses. We start from the decisions you need to make, then work backwards to the few events that inform them.
What goes into the plan
- Business questions first. Which pages bring enquiries, which ads bring buyers, which forms get abandoned. Each question gets one named event, and anything that answers no question is left out.
- A naming scheme. Event and parameter names follow one pattern, so a report built next year still makes sense to a new colleague.
- Conversion definitions. A lead, a qualified lead and a sale are written down separately, because ad platforms optimise for whatever you tell them to count.
- Ownership. Each event has an owner who knows why it exists, and a note on what should happen if its numbers change suddenly.
Measurement shapes search work too. Our technical SEO service uses the same data to find pages worth fixing.
The tracking pieces we put in place.
Every site needs a different mix. These are the parts we configure most often, each one tested before it goes live.
GA4 property setup
Data streams, internal traffic filters, retention, cross-domain rules and key events configured so the base data is clean before reports are built.
Google Tag Manager
A tidy container with naming rules, version notes and triggers limited to the pages that need them, so tags do not slow every visit.
Form and call tracking
Contact forms, click-to-call, WhatsApp buttons and booking widgets recorded as separate events, including forms that load inside a pop-up.
Campaign tagging
UTM rules for ads, email, social and partner links, with a shared sheet so spelling differences do not split one campaign into five rows.
Ecommerce events
Product views, add to cart, checkout steps and purchases passed with item data, for WooCommerce, Shopify and custom stores.
Dashboards
A Looker Studio view for owners and one for the marketing team, each limited to the numbers that person acts on every week.
Search Console link
Search queries and landing pages joined to on-site behaviour, so organic work can be judged by enquiries and not by traffic alone.
Alerts and checks
Simple alerts for a sudden drop in leads or purchases, so a broken form is noticed within a day and not at month end.
Reports that show what the money bought.
Campaign analytics is where tracking meets budget. We connect ad platforms, analytics and your records so spend can be compared with outcomes.
How campaign data is joined
- Click identifiers kept. Google and Meta click IDs are stored with the lead, so a sale weeks later can still be linked to its first touch.
- Offline results returned. Qualified leads and closed deals are sent back to the ad platform, so bidding learns from real value instead of form fills.
- One reporting view. A Looker Studio report combines spend, sessions, leads and revenue, with notes explaining which numbers are modelled.
- Honest attribution. We show several models side by side and explain their gaps instead of presenting one view as the truth.
If paid campaigns are on your list, see our PPC management and conversion campaigns pages.
Browser tags, server-side tags, or both?
Server-side tracking helps in some cases and is wasted effort in others. We decide with you, using the points below.
When server-side tagging is worth it
- High ad spend. When budgets are large, recovering even a small share of lost conversions can pay for the extra server.
- Strict data rules. A server container lets you remove fields before data leaves your domain, which suits regulated sectors.
- Heavy pages. Moving vendor scripts off the browser reduces what phones must download and run.
- Small simple sites. A brochure site with one form rarely needs it. A clean browser setup is cheaper and easier to maintain.
Server-side tagging changes how data is collected. It does not remove the need for consent and a clear privacy notice.
What each source counts, and what it cannot see.
Before anyone argues about a dashboard, it helps to know why the sources differ. This table is part of every hand-over document.
| Criteria | What it counts | What it misses |
|---|---|---|
| GA4 | Consented sessions and events | Declined consent, blockers, offline sales |
| Ad platforms | Conversions tied to their own clicks | Other channels that helped the sale |
| Search Console | Search impressions and clicks | What visitors did after they landed |
| CRM | Records a person actually handled | Visitors who never left details |
| Accounting | Money received | Which channel earned it |
Respecting choices without losing the picture.
Visitors who decline tracking are not measured. That is normal, and the setup must be honest about it.
What we configure
- Consent banner wiring. Tags wait for the visitor's choice, and Google consent mode is set so modelled data fills only the allowed gaps.
- Cleaner form data. Names, emails and phone numbers are kept out of analytics unless a lawful reason exists and a hashed method is used.
- Cookie records. You receive a list of every cookie and tag in use, with its purpose, so your privacy policy matches reality.
- Blocked-script awareness. Reports note that ad blockers and privacy browsers hide some visits, so no one reads totals as complete counts.
This is technical guidance, not legal advice. Your lawyer should approve the final wording of any notice.
From audit to a dashboard people actually open.
The path is short and checked at each stage, so broken tags are found before reports are built on top of them.
- 01
Audit
We open your current property, container and ad accounts, and list what fires, what is missing and what is counted twice.
- 02
Plan
You approve a one-page measurement plan with events, parameters and owners.
- 03
Build
Tags, triggers and data layer code are made in a workspace and kept separate from the live container.
- 04
Test
Each event is fired on real devices and checked in debug view, the network tab and the report itself.
- 05
Publish
Changes go live with a version note and a rollback ready, ideally outside your busiest trading hours.
- 06
Hand over
Dashboards, a tracking document and a short training call leave your team able to read the data without us.
Tracking questions, plainly answered.
Straight answers to what clients ask before they start.
How long does a tracking setup take?
A single site with forms and a few ad accounts often takes one to two weeks. Online stores, several domains or old messy containers take longer, mostly because of testing and clean-up rather than building.
Do you replace our existing GA4 property?
Usually no. We audit what exists, fix what is wrong and keep the history. A fresh property is suggested only when the old one is too damaged to repair, and we explain why before touching anything.
What affects the price?
The number of sites and domains, how many ad platforms feed in, store complexity, whether server-side tagging is needed and how much old clean-up exists. We quote after the audit, in writing.
Will tracking slow my website?
It should not. We load only what each page needs, delay non-critical tags and remove duplicates. A messy container often makes a site slower, so cleaning it can help speed.
Why do my numbers change after the setup?
Because the old numbers were probably counting twice or missing events. The first weeks may look different. We record the change in a note so reports before and after are read with the right context.
Do you check that tracking keeps working?
Yes, if you ask. Tracking often breaks silently after a theme update or a new plugin, so we offer a monthly check of the key events alongside website maintenance.
Can you fix tracking on a site built by someone else?
Yes. Most of our tracking work starts on an existing site. We read the theme, plugins and container, document what we find, and make changes in a workspace so nothing live is edited blindly.
What do I receive at the end?
A tracking document listing every event and tag, access to the container and dashboards, a short recorded walkthrough and a checklist for testing tracking after future site updates. You own all of it.
Know which half of your marketing works.
Send us your website address and the ad accounts you use. We will review what is firing today and tell you, in writing, what to fix first.