Conversion tracking setup
Clean source data makes weekly budget decisions sharper and protects spend from platform guesswork. WIF builds the UTM system, the GA4 conversion events, the call and offline conversion feeds, and the reporting view that connects a click to a lead, a qualified lead and revenue.
Short answer
The test is simple. Take one lead in the CRM and say which campaign, ad group and keyword produced it, whether sales called it, and what happened next. Most accounts fail somewhere between the click and the CRM record.
For lead generation that is a confirmed form submission, a completed booking, a tracked call over a minimum duration and a chat that actually starts. Button clicks, scroll depth and page views stay off the conversion list, because once a soft event counts it flows into smart bidding and the platform buys the wrong behaviour.
We watch firing in real time, submit test leads end to end, confirm nothing double-fires on refresh, and compare GA4, ad platform and CRM counts for the same window. Periods when an event was broken get marked, so a bad month is not later read as a real trend.
Inconsistent UTMs are the most common reason attribution collapses. We fix the vocabulary for source and medium, force lower case, build links from a shared template and cover paid, email, WhatsApp, partner and QR traffic. Start from the UTM tracking template for paid ads.
UTM values and the platform click identifier are captured into hidden form fields, stored on the lead record and preserved through routing and stage changes. That is what lets a sales owner see the source before the first call, and what makes cost per qualified lead reportable at all.
In most Indian lead-gen accounts a large share of enquiries arrive by phone. We track click-to-call on mobile, use dynamic number insertion where volume justifies it, set a minimum duration so wrong numbers do not count, and route call records into the CRM with the same source fields as forms.
Where consent rules apply to your audience, the banner has to talk to Consent Mode so tags adjust behaviour instead of firing regardless. That changes what you see rather than breaking it: denied consent produces modelled conversions, and knowing which part of a number is modelled is part of reading the report honestly.
For B2B, high-ticket and showroom businesses a form fill is not the outcome. Using the click identifier captured at submission, qualified-lead and closed-deal statuses are imported back into Google Ads and Meta so bidding optimises toward enquiries that became customers rather than toward easy form fillers.
Qualification status, disqualification reason and stage movement are recorded against the source, then read alongside search terms, audiences and creatives. A campaign with a cheap cost per lead and a poor qualified rate should lose budget even when the platform dashboard looks healthy.
Spend, leads, qualified leads, cost per lead, cost per qualified lead, follow-up speed, stage movement and revenue influenced, each traceable to a campaign.
Tracking workflow
Sequence matters. Fixing dashboards before fixing events only produces a tidier version of the same wrong number, so the data path is repaired from the click end forward.
Attribution review
Click to qualified lead
Related proof
Tracking is only worth building when it changes what happens on Monday morning.
FAQ
Because they count different things over different windows. GA4 counts events on the session they happened in. Ad platforms count conversions back to the click date and include modelled and view-through conversions. The CRM counts records a human created, including calls and walk-ins the website never saw. We pick one source of truth for decisions, usually the CRM, and use the others to explain the gap.
A small set of events that map to real enquiries: a confirmed form submission, a completed booking, a tracked call over a minimum duration, and a chat or WhatsApp conversation that starts. We avoid marking button clicks, scroll depth and page views as conversions, because those inflate the count and then reach smart bidding as if they were leads.
One naming convention, written down, applied to every paid, email, WhatsApp and partner link, with lower-case values and a fixed vocabulary for source and medium. Links are built from a shared template, UTMs are captured into hidden form fields so they reach the CRM with the lead, and stray values are reviewed so a mis-typed name does not split one campaign into two rows.
It is sending qualified-lead and closed-deal outcomes from your CRM back to the ad platform using the click identifier captured at submission. You need it when a form fill is not the real outcome, which covers most B2B, high-ticket and showroom businesses. Without it the platform optimises for whoever fills forms most easily.
If you advertise to visitors in regions with consent requirements, you need a banner wired to Consent Mode so tags adjust their behaviour instead of firing regardless. It does not break tracking, but denied consent produces modelled rather than observed conversions. That is another reason we anchor budget decisions on CRM records.
Spend, leads, qualified leads, cost per lead, cost per qualified lead, follow-up speed, CRM stage movement, revenue influenced, and sales feedback on which sources produced useful conversations. Each row should be traceable to a campaign through its UTM and click identifier, and the report exists to support one weekly decision: where budget moves next.
Free growth audit