Guide7 min read

What consent evidence should come with a purchased lead?

A lead file may say “consent: yes”. But what evidence sits behind that claim?

This guide explains eight elements worth checking when purchasing leads, why each matters and what to ask your suppliers.

For
Brokers, insurers and marketplaces that buy leads, and the sellers who supply them
Updated

In brief

  1. “Consent: yes” is a conclusion. Evidence is what lets someone else check it: the wording shown, the choice made, where and when, and who or what made it.
  2. Ask for evidence that travels with each lead, through an identifier in the lead file, rather than evidence that stays with the seller until someone asks for it.
  3. Keep three questions apart: whether the record is intact, what it documents, and whether the consent was legally valid. A record can help with the first two; the third is for you and your counsel.

Start from the question you may have to answer

Picture a common chain. A consumer asks a comparison site for a home insurance quote and ticks a box agreeing to be called. The lead is sold to a marketplace, then to a broker, then to an insurer. Weeks later, the consumer says they never agreed to a call.

The business that made the call may now need to show what happened on a form it never saw, held by a company several steps upstream. The lead file it received rarely helps: it names the person, the product and a consent flag.

So the useful question for a buyer isn’t “does the seller say there was consent?” but “what could we show, and how quickly, if someone asked?”

  1. Comparison site
  2. Marketplace
  3. Broker
  4. Insurer
IllustrativeEach step is a separate company.

The elements to ask for, one by one

Eight elements, in the order a buyer tends to need them. None is specific to one provider: ask for them whatever tools your sellers use.

  1. 1. The exact wording shown

    Why it matters
    The words set the scope: who may call, and about what. A label such as “marketing consent” loses that.
    Ask for
    The full text in view when the box was ticked, not a summary.
  2. 2. Which version of the wording

    Why it matters
    Forms change. You need the wording in force when this lead was collected, not the one on the form today.
    Ask for
    A version reference or fingerprint for the text, and the dates each version was live.
  3. 3. Who is named, and for what purpose

    Why it matters
    So you can see whether the business that will call is the one the request named, for the purpose it named.
    Ask for
    The businesses and purposes as the consumer saw them.
  4. 4. What the consumer did, in order

    Why it matters
    A box ticked by the visitor and a box that was already ticked are different facts. So are a click and a flag set later by a system.
    Ask for
    The state of the box when the form appeared, the change, and when the form was sent.
  5. 5. Where and when it happened

    Why it matters
    A lead can pass through publishers’ sites before it reaches a seller. The page and the time tie the record to one event.
    Ask for
    The site and page, and a timestamp with its time zone.
  6. 6. Who or what submitted the form

    Why it matters
    People aren’t the only ones filling in forms: AI agents and bots do too. Whether a person made the choice is part of the context.
    Ask for
    An assessment of person, AI agent, bot or uncertain, and what it rests on. It is probabilistic, never an identity.
  7. 7. Whether the record has changed

    Why it matters
    A file exported on request shows what a system holds today. A sealed record shows whether anything has changed since.
    Ask for
    A seal or signature you can check, and what it covers.
  8. 8. An identifier that travels with the lead

    Why it matters
    Evidence you can reach from the lead file doesn’t depend on asking the seller for screenshots weeks later.
    Ask for
    An evidence identifier, as one more field in the lead file or API payload.

What the eight elements look like in one record

The same elements in an example Evidence Object. The values are made up for this guide; the structure is the point.

Evidence Object8. Evidence IDEV-91C2-7F4A

Recorded interaction

1. Wording shown
“I agree to be called by Example Insurance about my home insurance quote.”
2. Wording fingerprint (SHA-256)
01b71a85975b…22ddaf
3. Named business
Example InsurancePurpose: Phone call about a home insurance quote
4. Box
Unticked when the form appeared→ consent box ticked by the visitor, then form sent
5. Site and page
compare.example/home-insurance/quoteForm sent: 28 Oct 2026, 09:41:05 UTC

Traffic assessment

6. Assessment
Human · R-101technical assessment, not a legal finding

Integrity

7. Signature
ECDSA P-256 with SHA-256Signature value not shown in this example
Example recordRun the demonstration check →

Ask for evidence that travels with the lead

Evidence that stays with the seller until a dispute tends to arrive late, as screenshots or exports, or not at all, especially once a lead has changed hands twice.

The simplest arrangement is one more field in the lead file: an identifier through which the receiving business can examine the evidence for that lead. Store it with the lead in your own systems, next to the call history.

LeadProductPhoneEvidence ID
L-20418Home insurance•• •• •• •• 42EV-91C2-7F4A
IllustrativeThe identifier, as one more column in the lead file.

Eight questions to put to a lead seller

Useful in a supplier review or before a new contract. Ask for the answers in writing, with an example record.

  1. What exact wording did the consumer see, and can you show the version in force on the day this lead was collected?
  2. Which businesses and purposes did the request name?
  3. How do you record the state of the box before the visitor acted, and the time the form was sent?
  4. On which site and page was each lead collected, and was it your site or a publisher’s?
  5. How do you tell whether a person, an AI agent or a bot submitted the form?
  6. How would we see that a record had been changed after it was made?
  7. How does the evidence reach us: with each lead, or on request? How long does a request take?
  8. What do you hold for leads collected before your current tools were in place?

Three questions to keep apart

Conversations about evidence go wrong when these are treated as one. A record can help with the first two. The third is a legal judgement.

  1. Evidence integrity

    Has this record changed since it was made?

    Answered by
    A check of its seal or signature.
    Leaves open
    Whether what was recorded was true or complete.
  2. Consent documentation

    What does the record say happened?

    Answered by
    The record itself: the wording, the choice, where and when, and the traffic assessment.
    Leaves open
    Who the person was, and whether they read or understood the wording.
  3. Legal validity

    Did that consent meet the legal requirements for this use?

    Answered by
    You and your counsel and, in a dispute, the authorities or the courts.
    Leaves open
    No record or check answers it on its own.

Where AdPriva fits

AdPriva is building independent, verifiable consent evidence for lead generation.

Its evidence infrastructure brings together the recorded consent interaction, traffic assessment and cryptographic integrity under one Evidence ID.

Evidence sealing and signing are available. Consent capture, traffic assessment and Evidence ID lookup are in preview, while end-to-end evidence handoff is being developed with design partners.

All guides →

Examine the evidence behind your leads.

Tell us how you buy leads, what consent evidence you receive today and what your team needs to verify. We’ll explore how AdPriva could fit your existing workflow.

Explore a pilot