How to Spot Fake Leads in a BTL Activation Report

Why lead fabrication happens, structurally

A fabricated lead is almost never the result of a promoter deciding to invent data for no reason. It is nearly always downstream of how the work is paid for. Where a contract pays per raw lead captured, with no quality gate before payment, the incentive is to produce the largest possible count, and the easiest way to do that under time pressure is to pad a genuine list with entries that were never actually collected. This is not a claim about any specific agency or promoter — it is a predictable response to a specific payment structure, and the fix is equally structural: pay against verified, qualified leads, or build verification into the contract as a non-optional step rather than an occasional audit.

Framed this way, spotting fake leads is less about suspicion and more about having a checking method that works regardless of whether any individual batch happens to be genuine. Two kinds of checks matter: whether the count is arithmetically plausible given how many people were actually engaged that day, and whether the list itself shows the structural signs of having been assembled rather than captured.

This matters more in some categories than others. In high-value categories — BFSI, real estate, telecom and edtech are the common ones for on-ground lead generation — a single qualified lead can be worth far more than the product itself in a sampling activation, which raises the stakes on verification considerably. A fabricated lead in a sampling campaign wastes a promoter's time and a small day-rate; a fabricated lead sold into a real-estate or BFSI pipeline wastes a sales team's time chasing a contact that was never real in the first place, which is a materially more expensive mistake.

Why the payment model changes the arithmetic, not just the incentive

The incentive argument is easiest to see in actual rupees. Lead-generation activity in this industry is typically priced somewhere in an indicative ₹60–₹400 range per verified lead, depending on the category and the qualification bar. The table below applies the low end of that range to the same corporate-park day used earlier — 450 contacts engaged, with a realistic 39 qualified leads at the mid-point of the quality-rate band — under two different payment structures.

What a fabricated lead list looks like

A genuinely captured lead list has the texture of real, slightly messy human data. A fabricated one tends to be too clean in specific, checkable ways.

• Phone numbers that are sequential or near-sequential across many entries — a sign of numbers generated rather than collected
• Duplicate numbers appearing across different venues or different days, attributed to different promoters
• No consent timestamp, or a consent timestamp identical across a batch of entries that should have been collected minutes apart
• Entries clustered at the exact same minute, inconsistent with one promoter capturing contacts one conversation at a time
• Numbers that are unreachable, disconnected, or belong to someone who has no memory of the interaction when called back
• A lead count that doesn't move when the reported contacts-engaged number for the same day is unusually low
• Names and other optional fields filled in with the same generic value across many entries, where a genuine conversation would have produced some variation

What a realistic capture rate actually looks like

Before checking a lead list for structural red flags, it is worth checking the headline count against the funnel arithmetic for how many people were engaged that day. The planning ranges below cascade from contacts through to an eventual sale, and a reported lead count that sits outside the lead-rate band is worth questioning before any deeper audit.

A reported count that cannot be real

The table above gives the ceiling, not just the mid-point, for how many leads one day of engagement can plausibly produce. Here is what happens when a reported number is checked against that ceiling.

How to verify a lead batch before paying for it

The arithmetic check above is a first pass, not a final answer — a batch can sit inside the realistic band and still contain fabricated entries, just fewer of them. The steps below are what actually confirms a batch is genuine.

1. 1

   Run the funnel check first

   Compare the reported lead count against the contacts-engaged figure for the same day. A rate outside the usual 8–22% band is worth a closer look before anything else.

2. 2

   Deduplicate against the full campaign list

   Check for repeated numbers across venues, days and promoters — a genuine lead should appear once, from one promoter, on one day.

3. 3

   Sample and call back

   Call a random sample of the batch, not a convenient one, and confirm the person remembers the interaction, the venue and roughly when it happened.

4. 4

   Check for a consent record on every entry

   A lead with no record of consent to be contacted is not just a verification gap — in most categories it is also a data-handling liability.

5. 5

   Hold payment on a quality gate, not the raw count

   Structure payment against leads that pass verification, not against the number submitted, so the incentive to pad the list disappears at the source.

What a qualified lead should actually cost

Once a batch is verified down to its genuinely qualified leads, the useful budgeting question changes from 'how many leads did we get' to 'what did each checkable lead cost.' Applying the mid-point of the indicative ₹60–₹400 per-verified-lead range to the 39 qualified leads expected from the corporate-park day used throughout this guide gives a concrete number to hold a vendor to.

Why the payment structure is the real lever

Checking individual batches catches individual problems. The more durable fix is upstream of any single check: how the work is paid for in the first place. A verification process bolted onto a per-raw-lead contract is fighting the contract's own incentive every single batch; a verification process built into a per-qualified-lead contract is simply confirming what the payment terms already require before money changes hands.

Paying per raw lead creates an incentive to manufacture them, which is why verification is contractual rather than optional.

Consent and data handling

Beyond fraud detection, there is a second, separate reason a consent record matters for every lead: the person's contact details are personal data, collected on the brand's behalf, and most categories carry some expectation that the person agreed to be contacted before that data is used again. A lead with no consent timestamp is a verification gap and a data-handling gap at the same time, and both should be closed by the same field in the capture form.

• Record the time and method of consent alongside every contact detail captured, not as a separate, optional step
• Store consent records with the lead, not in a separate system that can drift out of sync
• Make the capture tool itself refuse to save an entry with no consent flag set

What to ask a vendor before the campaign, not after

The cleanest way to avoid a fake-leads problem is to settle these questions in the contract before day one, rather than auditing a suspicious batch after the fact.

• How is the team paid — per raw lead, or against a verified and qualified count?
• What proportion of each batch is independently called back, and by whom?
• Is a consent record mandatory on every captured entry, with the tool enforcing it?
• How quickly are duplicates across venues and days checked, and against what master list?
• Who owns the cost of a batch that fails verification — is it rebilled, replaced, or simply absorbed?

What verification actually costs, compared to what it prevents

Calling back a random sample of a batch, checking for duplicates against a master list, and requiring a consent timestamp on every entry are all steps that take a supervisor minutes per batch, not hours — they are not the expensive part of running a lead-generation activation. The expensive part is downstream: a sales or telecalling team spending real hours working through a list that turns out to be substantially unreachable, after the activation has already ended and the on-ground team has moved to the next city. Verification is cheap and happens while the problem is still fixable; discovering the same problem downstream is expensive and happens after it no longer is.