Measure What Produced a Project, Not What Produced a Click.
Almost every interior business we audit is optimising toward the wrong number — usually because a button click somewhere is being counted as a conversion, and the reporting has been flattering ever since.
A WhatsApp Click Is Not a Lead. A Lead Is Not a Sale.
The most common tracking fault we find is not missing data. It is a single event — usually a WhatsApp button click — configured as the primary conversion. Google and Meta then dutifully optimise toward producing more of them.
The result is a campaign that reports excellent performance and a business that is not getting more projects. Worse, the algorithm has been actively trained to find people who tap buttons.
These are five genuinely different things and they must never share a conversion name:
Five Events, Five Meanings.
| Event | What it means | What it is worth |
|---|---|---|
whatsapp_click |
Someone tapped a button. They may never have sent the message. | An interest signal. Useful for diagnosis, never a conversion goal. |
lead_submit |
A form was completed and stored server-side. | A real enquiry, of unknown quality. |
qualified_lead |
The enquiry matches service area, project type and budget range. | The number worth optimising campaigns toward. |
consultation_booked |
A design consultation or site visit is in the diary. | A genuine sales opportunity. |
sale |
A project was signed. | The outcome. Available only where CRM data is maintained. |
If your ad account currently has one conversion action covering more than one of these rows, that is almost certainly the highest-value thing to fix.
What We Set Up.
Clean the foundation
One tag management setup, no duplicate pageview tracking, and internal traffic excluded. Duplicated GA4 tags — one direct, one through Tag Manager — are the single most common cause of numbers nobody trusts.
What changes: the baseline data is believable.
Implement the event taxonomy
Each of the five events tracked distinctly, with context attached: which page, which section, which form.
What changes: you can tell a button tap from an enquiry.
Persist the attribution
Campaign parameters captured on arrival and carried through the session, so an enquiry submitted three pages later still knows what brought that visitor in.
What changes: attribution survives a real browsing journey.
Close the loop from the CRM
Qualification and consultation outcomes imported back into Google and Meta against the original click ID, so bidding optimises toward business outcomes rather than form fills.
What changes: the platforms start finding people who become customers.
Handle consent properly
Advertising tags gated behind consent, analytics unaffected, and the gap acknowledged in reporting rather than quietly ignored.
What changes: measurement is compliant and its limits are stated.
Report in business language
A view that answers the questions an owner actually asks, rather than a dashboard of platform metrics.
What changes: the reporting gets read and used.
On the limits of attribution
Perfect attribution does not exist, and any agency presenting it as solved is overstating what the data can support. Consent rejection, iOS restrictions, cross-device journeys and offline conversations all create genuine gaps. A homeowner may see your Instagram ad, search your name a week later, and enquire from a laptop — and no platform will report that honestly.
What good tracking gives you is a directionally reliable picture and the ability to compare like with like. That is enough to make better budget decisions, which is the entire point. We would rather tell you the confidence level than present a number that looks more certain than it is.
What Is and Is Not Included.
Included
- Audit of existing analytics and conversion setup
- Google Tag Manager container build or clean-up
- GA4 configuration with the five-event taxonomy
- Google Ads and Meta conversion configuration
- UTM and click-ID persistence across the session
- Offline conversion import from CRM where feasible
- Consent mode configuration
- Reporting view built around business outcomes
Not included
- Paid analytics platform subscriptions
- Data warehouse or BI tool implementation
- Any claim of complete or perfect attribution
- Retroactive recovery of data that was never collected
What we ask you to prepare
- Admin access to Google Ads, Meta, GA4 and Tag Manager
- CRM access for the offline conversion loop
- An agreed internal definition of what "qualified" means for your business
- Someone who will actually update lead status in the CRM — without that, the loop cannot close
Tracking Questions.
Our agency says conversions are up. Why are projects not?
Usually because the conversion being counted is not an enquiry. Check what the conversion action in the ad account actually fires on — if it is a button click, a page view or a scroll depth, the number can rise indefinitely without a single additional project. This is the most common finding in our audits.
Is GA4 enough on its own?
For understanding website behaviour, largely yes. For knowing which campaign produced a signed project, no — that information lives in your CRM, and the two have to be connected. GA4 can tell you an enquiry happened; only the CRM can tell you it became a consultation.
Will the consent bar hurt our conversion data?
Yes, measurably, for visitors who decline. That is the correct trade-off rather than a problem to engineer around, and the honest response is to report the gap rather than pretend it does not exist. Consent mode preserves modelled data where the platforms support it, which recovers part of it.
How long does this take to set up?
The tag and event work is usually quick. The part that takes longer is agreeing internally what "qualified" means and getting the CRM used consistently enough for the offline loop to be meaningful — and that is a process decision on your side, not a technical one on ours.
What Is Your Ad Account Actually Counting?
The audit checks exactly what each conversion action fires on. It is frequently the most uncomfortable slide.