Guide5 min read

Why a CRM consent timestamp may not answer a buyer’s questions

Your CRM records when consent was logged. But when a buyer questions a lead, they may need more than a timestamp.

What wording did the consumer see? What action did they take? And can someone outside your systems examine the evidence?

This guide explains what a consent timestamp can tell you, what it may leave unanswered and how additional evidence can help.

For
Lead sellers and marketplaces that keep consent logs, and the buyer teams that receive them
Updated

In brief

  1. A timestamp shows that your system marked consent at a given moment. It rarely shows what the consumer saw, what they did, or who or what filled in the form.
  2. It is your own account, kept in your own systems, so whoever receives it has to take your word for it.
  3. Keep your logs. Add evidence the next business can examine for itself, and keep integrity, documentation and legal validity apart.

What a CRM timestamp usually records

A typical consent entry ties a lead to a flag and a time. It is built for running the business: suppression lists, call scheduling, opt-outs. It does that well.

The time may even be when your system received the lead, rather than the moment of the click.

CRM entry

Lead ID
L-20418
Source
compare.example
Consent
yes
Recorded
2026-10-28 09:41:07 UTC

What it doesn’t hold: the wording, the order of events, and who or what filled in the form.

IllustrativeA typical consent entry, simplified.

Five questions a buyer asks, and what each answer needs

When a lead is questioned, these are the questions that come back. A timestamp answers part of the second.

  1. What wording did the consumer see?

    A CRM timestamp alone

    Not recorded, or only a label such as “marketing consent”.

    A detailed consent evidence record

    The exact wording in view, with a reference to its version.

  2. What did they do, and when?

    A CRM timestamp alone

    That a flag was set, and when your system recorded it.

    A detailed consent evidence record

    The box before and after, and when the form was sent.

  3. Who or what filled in the form?

    A CRM timestamp alone

    Not recorded.

    A detailed consent evidence record

    An assessment: person, AI agent, bot or uncertain. Probabilistic, never an identity.

  4. Has anything changed since?

    A CRM timestamp alone

    A database row can be edited, and showing that it wasn’t is hard.

    A detailed consent evidence record

    Cryptographically sealed, so changes made after signing can be detected.

  5. Who can check it?

    A CRM timestamp alone

    Only someone with access to your systems, taking your word for it.

    A detailed consent evidence record

    The business that receives the lead, through an identifier that travels with it.

“A detailed consent evidence record” here means any record built this way, whoever provides it.

Why independent verification matters

Your CRM and consent platform remain important sources of information. But when evidence stays inside the seller’s systems, a buyer may need to request screenshots, exports or access to investigate a disputed lead.

Evidence linked to the lead gives the receiving business a way to examine the associated record without depending entirely on the seller’s account.

Keep your logs, and add what they don’t hold

Your CRM is where your teams work, and where consent meets opt-outs and call history. Before your next buyer asks, check that you can also:

  • keep a copy of every consent wording you have used, with the dates each one was live;
  • record what happened on the form, in order, not only the final flag;
  • note the site and page each lead came from, including publishers’ sites;
  • show that a record hasn’t changed since it was made;
  • pass something the buyer can examine with each lead, rather than only on request, and store its identifier next to the lead in your CRM.

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 complements your existing CRM and consent platform by connecting the consent interaction, traffic assessment and cryptographic integrity under one Evidence ID.

The goal is to make the evidence available to the businesses receiving the lead, without requiring access to the seller’s internal systems.

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

All guides →

Bring evidence into your lead flow.

Tell us how you collect consent, generate leads and deliver them to buyers. We’ll explore how AdPriva could fit your existing workflow.

Explore a pilot
Who it’s for
  • Publishers, affiliates, comparison sites and lead marketplaces generating or selling consumer leads.
What you get
  • Free access during the agreed pilot, integration guidance and direct collaboration with our team.
What happens next
  • We’ll review your existing workflow and identify a suitable pilot together.