Short answer: To reduce fake and duplicate real estate leads, verify phone numbers at capture (Meta Higher-intent forms with SMS verification, Google lead form OTP, WhatsApp or SMS OTP on your website), normalise every number to +91 format, and let the CRM merge repeat enquiries into one contact with a dated activity log instead of creating new leads. Then send "junk" and "qualified" outcomes back to Meta and Google so their bidding stops chasing bad leads.
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.
What counts as a fake or duplicate real estate lead?
"Fake lead" is used for at least six different problems, and each one has a different fix. Before you change any form, make the sales team use these disposition codes for two weeks:
| Code | Definition | Typical cause | Primary fix |
|---|---|---|---|
| INVALID | Number not in service, wrong digits, or obviously junk (9999999999) | Typos, bots, made-up entries | Validation and OTP at capture |
| DID_NOT_ENQUIRE | Real person who says they never filled a form | Autofilled instant forms, accidental taps, organic form shares | Higher-intent forms, review screen, SMS verification |
| DUPLICATE | Same person already in CRM for the same project | Several ads, portals and retargeting reaching one buyer | CRM matching and merge rules |
| UNREACHABLE | Valid number, no answer after 3 attempts on 2 days | Slow first call, wrong time of day | Response time and WhatsApp-first contact |
| NOT_A_BUYER | Broker, job seeker, vendor, competitor | Broad keywords and targeting | Negative keywords, qualifying question |
| OUT_OF_FIT | Real buyer, wrong budget or location | No price in the ad; loose radius | Price in creative; budget question |
Once you have the split, you can see the problem clearly. If DID_NOT_ENQUIRE is the biggest bucket, the form type is wrong. If UNREACHABLE is biggest, the problem is speed, not the leads. As a working rule, we act on any single code that exceeds 10–15% of a source's leads in a week. Treat that as a starting threshold, not an industry benchmark.
Where do fake real estate leads come from?
| Source | Main junk pattern | First control to add |
|---|---|---|
| Meta instant forms | Autofill submits name and number in two taps; organic shares of the form | Higher-intent form, SMS verification, block organic leads |
| Google lead form assets | Quick submissions from broad searches | OTP verification; required qualifying question |
| Website forms | Bots, competitors, test entries, made-up numbers | Server-side validation, bot check, OTP |
| Portals | Same buyer enquires on 10 listings; brokers posing as buyers | Dedupe across sources; one qualifying call script |
| Vendors and affiliates | Recycled databases, the same lead sold to several developers | Contract terms, consent proof, replacement rules |
How do you set up Meta instant forms to cut fake leads?
- Form type: Higher intent. It adds a review step before submission. In Meta's leadgen form API this is the
is_optimized_for_qualityflag. - SMS phone verification on. The same API documents
is_phone_sms_verify_enabled, "whether the form requires phone sms verification when user submits". Where Ads Manager offers it on your account, turn it on for every real estate form. - A required multiple-choice question with an honest exit option, for example "When do you plan to buy? 0–3 months / 3–6 months / 6–12 months / Just exploring". People who tap through without reading pick randomly, and you can see it in the data.
- Price on the context card. "3 BHK from ₹1.4 crore" filters out budget mismatches before they become leads.
- Block organic leads with
block_display_for_non_targeted_viewer(Meta's lead ads guide), so form shares outside your targeting do not pollute the CRM.
Expect CPL to rise when you do this. Judge the change on cost per contacted, qualified lead, not CPL. More Meta-specific setup is in our Meta ads for real estate guide.
How do you set up Google lead forms to cut fake leads?
Google's lead form assets run on Search and Performance Max campaigns and list OTP verification as a quality feature. Two more settings matter:
- Qualifying responses (Search campaigns only): a required multiple-choice question where you mark which answers count as qualified. Those submissions are tagged as qualified leads and fed into a "Qualified lead" conversion goal, which bidding can use.
- Get leads out quickly: Google stores leads for only 60 days. Use the webhook or a CRM integration, not a monthly CSV download, or you will lose leads and call them too late.
Website forms behind Google Search ads need the controls in the next section. Our Google Ads for real estate guide covers negative keywords that keep job seekers and renters out.
Should you add OTP to real estate website forms?
Yes for high-abuse sources, with one design choice that protects conversion: save the lead first, verify second. If OTP is a gate before submission, people with network delays drop off and you never see them. If you save the lead and then ask for the OTP, verified leads go to the top of the call queue and unverified ones still get a call later.
| OTP channel | Cost basis (October 2026) | Setup requirement | Notes |
|---|---|---|---|
| WhatsApp authentication template | ₹0.115 per delivered message plus GST (Free Press Journal) | WhatsApp Business API account and an approved authentication template | Also opens a WhatsApp thread you can use for the brochure |
| SMS OTP | Set by your SMS provider | DLT registration of entity, sender header and content template (TRAI DLT framework) | Works for buyers without WhatsApp |
Worked example: 1,000 website leads a month, with about 1.3 OTP sends per lead to allow for resends, is 1,300 WhatsApp authentication messages, roughly ₹150 plus GST at the October 2026 rate. The cost is negligible. The real cost is any drop in form completion, which is why "save first, verify second" matters. Full rate details are in our WhatsApp Business API cost guide.
Bot and spam controls that do not need OTP:
- A hidden honeypot field. Reject any submission that fills it.
- A time check. Reject forms submitted within 2–3 seconds of page load.
- A bot check such as Cloudflare Turnstile or Google reCAPTCHA, which usually runs without showing a puzzle. Always validate the token on your server, not just in the browser.
- Rate limits: no more than 3 submissions per phone number or IP address per hour.
What phone validation rules should every real estate form use?
Normalise before you validate or dedupe. Google's open-source libphonenumber parses, formats to E.164 and checks number type (mobile or fixed line) for any country, with ports in most languages. Apply these rules:
- Strip spaces, dashes, brackets and leading 0, 91 or +91, then store as
+91XXXXXXXXXX. - Accept Indian numbers only if libphonenumber returns a valid mobile number for region IN. Allow other country codes for NRI forms.
- Reject repeated digits (9999999999), simple sequences (9876543210, 1234567890) and your own office numbers.
- Run the same normalisation on every source (Meta, Google, portals, website and imports) before records reach the CRM. Most "duplicates" that slip through differ only by +91 or a space.
What CRM dedupe rules work for real estate?
The goal is one contact per person, with every enquiry recorded as activity, so sales sees "third enquiry in 40 days, from Google and 99acres" rather than three cold leads given to three people.
| Scenario | Match key | Action |
|---|---|---|
| Same phone, same project, within 90 days | Normalised phone + project | Merge into the existing lead; log the new source as a touch; keep the original owner; alert them ("re-enquired via Meta") |
| Same phone, same project, after 90 days with lead closed as lost | Phone + project + status | Reopen the same lead with a "re-engaged" tag; keep the full history |
| Same phone, different project | Phone | Same contact, new opportunity for the second project; notify both project owners |
| Same email, different phone | Lower-cased email | Flag for manual review; never auto-merge on email alone |
| Channel partner registers a buyer already in the CRM | Phone + project + registration timestamp | The first valid registration within your partner policy's validity window wins; reject later claims with the timestamp shown |
| Household or office number used by two buyers | Phone + different names | Manual review; allow two contacts with a shared-number tag |
Store two source fields: original source (never overwritten) and latest source. Without them, retargeting and portals take credit for buyers that search ads found first. Our real estate CRM guide has the full stage model.
How do you make Meta and Google stop sending junk?
Filters remove junk after it arrives. Feedback changes what the platforms look for. Send CRM outcomes back:
- Meta: the Conversions API for CRM lets Meta optimise for leads that reach a stage you choose. Meta asks for at least 200 leads a month and daily uploads, with the stage reached within 28 days. Also upload junk leads as a custom audience to exclude.
- Google: import "qualified" and "site visit" stages as offline conversions. Since 15 June 2026, Google routes these uploads through Data Manager rather than the Google Ads API. Our offline conversion tracking guide has the setup.
How do you control fake leads from vendors and channel partners?
Bought or vendor-supplied leads are where duplicates and fakes multiply, because the same record can be sold to several developers. Put these terms in writing:
- Exclusivity: the lead is not sold to anyone else for a defined period
- Consent proof: timestamp, source URL or ad ID and the consent text shown to the buyer
- Replacement: invalid, duplicate and DID_NOT_ENQUIRE leads replaced if reported within 72 hours
- Dedupe against your CRM before billing, using the normalised phone
Read our real estate leads database guide before you buy any list.
What should a weekly lead-quality scorecard show?
| Metric | Formula | By |
|---|---|---|
| Valid rate | (Leads − INVALID − DID_NOT_ENQUIRE) ÷ leads | Source, campaign, form |
| Duplicate rate | DUPLICATE merges ÷ raw leads | Source |
| Contact rate | Leads reached ÷ valid leads | Owner, hour received |
| Median first response | Time from lead to first call or WhatsApp | Owner |
| Qualified rate | Qualified ÷ contacted | Campaign, creative |
| Cost per qualified lead | Spend ÷ qualified leads | Campaign |
Quality work pays off further down the funnel. Founder Rinku Singh's in-house ILeadGuru programme (before GrowthSparx) captured budget and location before leads reached brokers and optimised on lead progression, reaching a 30% lead-to-deal rate. For what happens after the lead is clean, see real estate lead qualification to site visit.
Sources
- Meta Graph API: leadgen_forms:
is_optimized_for_qualityandis_phone_sms_verify_enabled - Meta Marketing API: Create lead ads: organic lead blocking, custom questions
- Google Ads: About lead form assets: OTP verification, 60-day lead storage, webhook delivery
- Google Ads: Qualifying responses in lead forms: Search-only qualified lead tagging
- Free Press Journal: WhatsApp rates from 1 October 2026: ₹0.115 authentication message rate
- Mobile Seva: SMS DLT registration: entity, header and template registration under TRAI's DLT system
- Google libphonenumber: parsing, E.164 formatting and mobile number validation
- Meta: Conversion leads integration: CRM feedback requirements