Short answer: To track qualified leads from Google Ads, capture the click ID (GCLID, GBRAID or WBRAID) and the lead's email and phone with every enquiry, store them on one CRM record, and mark the record "qualified" or "converted" only against agreed criteria. Then import those stages into Google Ads. Google now recommends enhanced conversions for leads, set up through Data Manager, over GCLID-only offline imports. Once the imported "Qualified lead" action has enough data, make it the primary conversion so bidding chases sales-ready leads instead of form fills.
Need this done for you? GrowthSparx offers a fixed-scope lead tracking and attribution setup: GA4, Google Ads, Meta, WhatsApp, calls and CRM wired into one dashboard, usually live in 2–3 weeks.
Benchmark reference: the public 2025–2026 numbers behind this guide (Meta and Google CPC/CPM in India, CPL ranges by industry, landing-page conversion, real estate funnel rates, WhatsApp API pricing) are collected and graded in our India lead generation benchmarks 2026 report.
Why aren't form submissions enough?
A form submission proves someone typed into a form. It does not prove they can buy. In Indian lead generation the gap is wide: wrong numbers, job seekers, students filling every education form they see, competitors, and duplicate enquiries from the same person across devices. If "Submit lead form" is the primary conversion, Smart Bidding treats a junk lead and a ₹50-lakh flat buyer as identical and learns to find more of whichever is cheaper.
Google's own goal setup reflects this. It replaced the old "imported leads" category with two goal types, Qualified lead and Converted lead: a qualified lead is a Google-generated lead "further qualified offline", and a converted lead is one that has "completed a chosen step", such as a sale. Google says choosing the right goal lets automated systems "optimize for specific, high-value business outcomes rather than just maximizing lead volume."
Keep form submissions as a secondary, diagnostic conversion. Bid on what sales accepts.
How do you define a qualified lead?
Write the definition with the sales head, in observable terms, before touching any tag. A good definition is something a telecaller can tick in 30 seconds. Examples by vertical:
| Vertical | Qualified lead (example criteria) | Converted lead |
|---|---|---|
| Real estate | Reachable, budget within project range, buying within 6 months, agrees to a site visit | Site visit done, or booking amount paid |
| Education / admissions | Reachable, eligible for the course, intake year matches, parent or student confirms interest | Application fee paid or seat confirmed |
| Healthcare | Reachable, condition matches a treatment offered, shares reports or books a consult | Consultation attended or treatment started |
| B2B services | Company fits ICP, decision-maker or influencer, problem and timeline confirmed, meeting booked | Proposal accepted or PO received |
Two rules we hold to. First, separate "unknown" from "no": an unreachable lead is not a rejected lead, and mixing them hides contact-rate problems. Second, record a rejection reason from a fixed list (wrong number, no budget, outside location, job seeker, duplicate, competitor). Those reasons become negative keywords, placement exclusions and form changes.
Step 1: How do you capture GCLID, GBRAID and WBRAID?
With auto-tagging on, Google Ads appends a click identifier to the landing-page URL. Most clicks carry gclid. For some iOS traffic Google sends different parameters: Google's iOS measurement page says gbraid "is added to landing page URLs when auto-tagging is enabled for all iOS14.5+ clicks", and wbraid was introduced for attributing web conversions on iOS. Capture all three.
- Confirm auto-tagging is on in account settings, and check that redirects or your CMS do not strip query parameters. Click a live ad (or use ad preview) and look for
gclid=in the final URL. - Persist the ID on landing. A small script reads
gclid,gbraid,wbraidand UTMs from the URL and saves them in a first-party cookie or localStorage for 90 days, so the ID survives if the visitor browses three pages before enquiring. - Write them into hidden form fields named exactly
gclid,gbraid,wbraid,utm_source,utm_campaign,landing_page. Our GTM form-tracking guide shows the trigger setup. - Map those fields in the CRM integration (HubSpot, Zoho, LeadSquared, Salesforce or a webhook). The commonest failure we see is a hidden field that fills correctly on the website and is silently dropped because nobody mapped it in the CRM.
- Collect email and phone in a clean format. Enhanced conversions for leads matches on hashed user-provided data. Store Indian mobiles in E.164 format (
+919876543210), lower-case emails, and trim spaces. - Handle the non-form paths. Calls from ads need call tracking, and click-to-WhatsApp chats need a source capture step. See call tracking for Indian businesses and WhatsApp lead tracking.
Test with a real ad click on Android Chrome, iPhone Safari and desktop. Submit a test lead from each, then open the CRM record and confirm the ID is there.
What CRM fields do you need? A sample schema
| Field | Type / format | Set by | Purpose |
|---|---|---|---|
| lead_id | Unique text | CRM on create | One stable key across web, CRM and uploads |
| created_at | Datetime with offset, e.g. 2026-10-09 14:32:00+05:30 | CRM | Lead time; must be after click time |
| gclid / gbraid / wbraid | Text, stored exactly as received | Hidden form field | Click match key |
| email, phone | Lower-case email; E.164 phone | Form | Match keys for enhanced conversions for leads |
| utm_source, utm_medium, utm_campaign, landing_page | Text | Hidden form field | Reporting; campaign-level quality analysis |
| consent_ad_user_data, consent_ad_personalization | GRANTED / DENIED | Consent banner or form | Sent with uploads where required |
| lead_status | Picklist: New, Contacted, Unreachable, Qualified, Rejected, Converted, Lost | Sales | Drives which conversions are uploaded |
| qualified_at, converted_at | Datetime with offset | Workflow on status change | Conversion time in the upload |
| rejection_reason | Picklist | Sales | Feeds negatives and form fixes |
| deal_value | Number (INR) | Sales / finance | Converted-lead value |
| uploaded_qualified, uploaded_converted | Boolean + timestamp | Upload job | Prevents repeat uploads |
Set qualified_at by workflow when the status first changes, and never let it be edited afterwards. If a salesperson toggles a lead back and forth, the timestamp stays put and you avoid a second conversion.
Step 2: Offline conversion import or enhanced conversions for leads?
As checked in October 2026, Google's position is clear. Its offline conversion imports page says advertisers who haven't adopted offline import should start "with enhanced conversions for leads instead", and calls Data Manager "the fastest and easiest way to set up or upgrade". The file-based GCLID import article is now labelled "legacy". Google also states that from 15 June 2026, offline conversion and enhanced conversions for leads uploads "will be migrated to the Data Manager API and blocked in the Google Ads API". Any custom script still calling the old Google Ads API upload method needs rebuilding.
| Offline conversion import (GCLID) | Enhanced conversions for leads | |
|---|---|---|
| Match key | GCLID (GBRAID in limited cases) | Hashed email/phone captured by the Google tag, plus GCLID where available |
| Website requirement | Store GCLID in a hidden field | Google tag or GTM collects user-provided data on the form; keep storing GCLID too |
| Coverage | Lost when the ID is stripped or missing | Can match when no click ID survives; Google cites more accurate reporting and engaged-view and cross-device conversions |
| Status | Legacy; still works through Data Manager | Google's recommended path |
| Upload window | GCLIDs retained for 90 days | Data with personal information uploaded within 63 days of the event |
The windows above come from Google's offline conversion imports FAQ. Setup paths for enhanced conversions for leads, per the Google Ads Help overview, are the Google tag, Google Tag Manager, Data Manager and the Google Ads API. Upgrade options listed in Google's upgrade guide cover Data Manager, the Google Ads API and third-party tools such as Zapier and HubSpot, and Google calls choosing "Qualified lead" or "Converted lead" as the goal a best practice. Since April 2026, enhanced conversions for web and for leads share one on/off setting.
If you already run GCLID imports, the same guide says to keep sending GCLIDs, "import all events whether they contain a GCLID, user-provided data field, or both", and wait "1-2 conversion cycles or 4 weeks" before making the new action primary and the old one secondary. Our step-by-step tag setup is in Google Ads enhanced conversions for leads, and the classic GCLID flow is in offline conversion tracking for Google Ads.
Step 3: What does the upload file look like, and how often should you upload?
For a Google Sheet or file connection, one row is one conversion event. A sample header for a GCLID-based sheet, using the column names in Google's legacy file template plus the consent columns it documents:
Parameters:TimeZone=Asia/Kolkata
Google Click ID,Conversion Name,Conversion Time,Conversion Value,Conversion Currency,Ad User Data,Ad Personalization
Cj0KCQjw...,Qualified lead,2026-10-09 16:05:00,9000,INR,GRANTED,GRANTED
For enhanced conversions for leads, add your email and phone columns and map them in Data Manager; the column names are yours, the mapping tells Google what they contain. Use a time-zone ID such as Asia/Kolkata; Google's template article recommends IDs over raw offsets and lists missing time-zone data as a common error.
Cadence and timing rules from Google's import FAQ:
- Upload at least daily. If that is impossible, use a fixed schedule such as every two days or weekly. Irregular uploads make Smart Bidding see sudden spikes.
- Wait about 6 hours after the click before a scheduled upload, so Google has processed the click.
- Conversion time must be after the click. A "conversion precedes click" error usually means a time-zone mismatch.
- Duplicates: a row with the same GCLID, conversion name and conversion time is de-duplicated. To record a qualified and a converted event for one lead, use two conversion names, not two rows of the same name.
Our standard flow: a CRM workflow writes a row to the sheet when lead_status becomes Qualified and sets uploaded_qualified; Data Manager reads the sheet on its schedule; a weekly review checks the diagnostics tab for rejected rows.
How should you assign values? Conversion value rules
A qualified lead needs a value if you want to bid with Target ROAS or Maximise conversion value. Work it out from your own funnel.
Worked example (assumptions stated): 1 in 4 qualified leads closes, the average deal is ₹1,20,000 and gross margin is 30%. Value per qualified lead = 0.25 × ₹1,20,000 × 0.30 = ₹9,000. Upload Converted lead events with the actual deal value from the CRM.
Conversion value rules then let you adjust values by audience, geographic location or device, and Smart Bidding uses them in real time for Target ROAS and Maximise conversion value. Google lists Search, Shopping, Display and Performance Max as supported. Useful case: if leads from Tier-1 cities close at twice the rate of the rest, multiply their value instead of building separate campaigns. Note Google's caveat that some conditions may be unavailable for housing, employment or credit ads, which affects real-estate and loan advertisers in India.
How do you measure lead quality?
Track a short set of ratios by campaign, keyword theme and landing page, on lead cohorts (leads created in the same week), not calendar totals.
| Metric | Formula | What a drop usually means |
|---|---|---|
| Valid-contact rate | Reachable leads ÷ all leads | Fake numbers, bots, or slow first call |
| Qualified rate | Qualified ÷ valid contacts | Broad keywords, mismatched ad promise |
| Cost per qualified lead | Spend ÷ qualified leads | The number to optimise, not CPL |
| Speed to first contact | Median minutes from created_at to first call | Sales capacity, not marketing |
| Lead-to-deal rate | Converted ÷ all leads | Pricing, offer or follow-up issues |
Our published results are framed this way: a 30% lead-to-deal conversion for ILeadGuru's real-estate buyer leads (our founder's in-house role) and an 8% conversion at ₹50 average CPL for Career Clinic. The CPL alone would not tell you whether either account was healthy.
QA checklist before bidding on imported leads
| Check | Pass threshold |
|---|---|
| Test clicks on Android, iPhone and desktop land with a click ID in the CRM | 3 of 3 |
| Share of Google Ads leads in the CRM with GCLID, GBRAID or WBRAID | Track weekly; investigate any sudden fall |
| Email or phone present and correctly formatted | Every form lead |
| Conversion time includes time zone and is after the click | Zero "precedes click" errors |
| One CRM stage maps to one conversion action | No action fed by two stages |
| Upload flags prevent re-sending | No duplicate rows in a week's file |
| Data Manager / offline diagnostics reviewed | Weekly |
| Imported qualified leads reconciled with CRM qualified count for the same cohort | Monthly; explain the gap, don't force a match |
| Qualified-lead action ran as secondary before becoming primary | 1–2 conversion cycles or 4 weeks, per Google |
For a broader audit covering GA4, Meta and the CRM together, use our lead tracking audit checklist.
Sources
- Google Ads Help: About offline conversion imports: enhanced conversions for leads recommended; Data Manager preferred; 15 June 2026 Data Manager API migration.
- Google Ads Help: About enhanced conversions for leads: how matching works; setup paths; combined setting from April 2026.
- Google Ads Help: Upgrade offline conversion import to enhanced conversions for leads: keep GCLIDs, import all events, 1–2 cycles or 4 weeks before switching primary.
- Google Ads Help: Offline conversion imports FAQs: 90-day GCLID retention, 63-day limit, daily uploads, 6-hour wait, de-duplication.
- Google Ads Help: Import conversions using files (legacy): template columns, consent columns, time-zone parameter.
- Google Ads Help: Updates to iOS 14 campaign measurement: GBRAID and WBRAID parameters.
- Google Ads Help: About qualified leads and converted leads: goal definitions.
- Google Ads Help: About conversion value rules: conditions, supported campaigns, housing/credit limitation.