Strategy

Proof of Consent for Leads: What to Verify Before You Contact Anyone

By Phil | SoloAdsGuide.comNovember 14, 202614 min read
Solo ads strategy illustration for Proof of Consent for Leads: What to Verify Before You Contact Anyone

Full disclosure: Philip Coble, the owner of SoloAdsGuide.com, owns PulseTraffic, PhilSoloAds and PulseTrack. That is exactly why this guide teaches you to verify claims instead of trusting them. Hold my services to the same standard as any other provider.

Proof of consent for a lead is a record that shows when the person agreed, the exact words they agreed to, the page where they did it, and that your business was covered by that agreement. A name, a phone number, a timestamp and a seller's promise of compliance are not proof. If you buy leads, or buy solo ad traffic that turns into leads, you need to check the record yourself before you email, call or text anyone. That is the same buyer-first habit we teach for traffic: verify first, spend second.

TL;DR

  • A consent record needs the timestamp, the disclosure text, the form URL, the IP address, the user-agent string and the specific action the person took.
  • A seller saying "we're compliant" does not move the legal risk off you. Buyers are expected to check the record on their own.
  • A third-party certificate ID only points to evidence. It helps only if the session behind it can still be played back and matches the lead.
  • Aged or resold leads need extra checks, because consent does not travel with a phone number.
  • Consent shows you may contact someone. It says nothing about whether the lead is any good, so you still need click tracking and traffic verification.

Table of Contents

Why buyers, not sellers, carry the burden

Many beginners assume the lead seller is responsible for compliance. The law does not work that way. Under the Telephone Consumer Protection Act (TCPA), the federal law that governs autodialed and prerecorded calls and texts, the caller has to prove consent. In Van Patten v. Vertical Fitness Group, the Ninth Circuit treated express consent as an affirmative defense, which means the defendant carries the burden of proving it.

That puts you, the buyer, in the hot seat. Lead buyers inherit the legal risk of non-compliant outreach and cannot rely only on a seller's assurances. One compliance firm put it bluntly in March 2026: the law does not care whether the vendor promised compliance, it cares whether the buyer can prove it.

This matters for solo ad buyers in particular. A solo ad is a single email sent by a vendor to their list with one call to action, usually pointing to your squeeze page. The person who opts in on your page gave you consent on your page, and you hold that record. But when a vendor hands you a spreadsheet of "leads", or a lead who came through another form, the record sits with someone else. Your job is to get it, read it and test it.

What the law asks for right now

Rules around lead consent have moved a lot in two years. Here is the picture as of late 2026, from the sources we checked. Confirm anything you rely on with a lawyer, because this is general education and not legal advice.

  • Prior express written consent is still required for autodialed or prerecorded marketing calls and texts.
  • The one-to-one consent rule adopted by the FCC in December 2023 was vacated by the Eleventh Circuit on January 24, 2025, and the FCC formally reinstated the earlier consent standard in August 2025.
  • Revocation: since April 11, 2025, consumers can revoke consent by any reasonable method, and callers must honor it within 10 business days. A separate revoke-all provision was delayed until January 31, 2027, per the same source.
  • AI voices: in February 2024 the FCC ruled that AI-generated voices count as artificial or prerecorded voices. A marketing call using one to a mobile number requires prior express written consent.
  • Seller-specific consent still shows up elsewhere. Even with the FCC rule vacated, the FTC's Telemarketing Sales Rule requires consent to name the specific seller for covered telemarketing calls.

The practical takeaway: even where a rule is gone, a record that names your business specifically is still the strongest thing you can hold. Build to the stricter standard and you do not have to re-tool every time a court rules.

A useful test: could someone who was never in the room replay what happened? A consent trail built to that standard includes:

  1. A timestamp of the consent event, ideally in ISO-8601 format with timezone, such as 2026-11-12T14:03:22-05:00.
  2. The IP address of the device.
  3. The exact page URL where the form lived.
  4. The consent language shown, word for word as the person saw it.
  5. The named sellers covered, so you can see your business was included.
  6. The user-agent string, which identifies the browser and device.
  7. Session data showing which fields were filled in and in what order.
  8. Any opt-out record, with its timestamp and the method used.

That list follows a 2026 lead buyer documentation checklist. Another source adds location data and the specific consent action taken, such as a checked box or a button press, and notes that these artifacts should stay linked to the delivery, order and invoice so you can produce proof without searching across systems.

There is also a useful benchmark from the FTC side. Where the Telemarketing Sales Rule requires consent, 16 C.F.R. § 310.5(a)(8) says a complete record includes the date and a copy of the request for consent in the same manner and format it was shown. It is a different rule under a different statute, but it is a sensible bar for every lead record you keep.

Worked example: a record that passes and one that does not

Imagine you buy 500 leads from a vendor for a business opportunity offer.

Record A arrives as a spreadsheet: name, email, phone, a date, and a note saying "opt-in verified." There is no form URL, no wording, no IP address, no list of sellers covered.

Record B arrives with the same columns plus the form URL, the IP address, the user-agent string, the exact disclosure text, and a list of named sellers that includes your company. It also has a session replay or archived page capture of the form as it looked that day.

Record A is a claim. Record B is evidence. A lead that comes with only a name, a number, a timestamp and a vendor's promise is not a consent record. If you only get Record A, do not call or text those people.

Comparison of incomplete and verifiable consent records

Having the fields is step one. Step two is reading them like a skeptic. Here is a routine you can run on a sample before you act on the whole batch.

  1. Read the disclosure text. Does it clearly say the person agrees to marketing calls or texts, and does it name a seller or a clear set of sellers? Language that buries the permission in a long privacy policy is a bad sign.
  2. Look for your business by name. If the form covers "partners" without a list, you cannot show that your company was included. For shared leads, ask for the full seller list and the exact consent text.
  3. Check that the action was affirmative. A pre-checked box or an opt-in that happens just by landing on a page is weaker than a person typing their number and ticking an unchecked box.
  4. Match the purpose. If the form promised a free guide and your outreach is a phone pitch for a paid program, ask whether the person could reasonably expect that.
  5. Match the contact type. Consent for email is not consent for autodialed texts or calls. The record should cover the channel you plan to use.
  6. Compare the record to the lead. Does the phone number in the record match the number on your list, and does the form URL actually exist and show that disclosure?

The same page-capture habit protects you here. A common documentation failure is being unable to authenticate the rendered disclosure shown at opt-in. If you cannot show what the person saw, the text in your database is just text.

Certificates and third-party reports are pointers, not proof

Many lead sellers attach a certificate ID from a third-party verification service. That is better than nothing, but do not treat it as the end of the check. A certificate ID is a pointer to evidence, not the evidence itself, and helps only if the session it points to can still be played back and matches the consumer and the form.

Courts have noticed. In a 2026 case covered by the National Law Review, a company lost its summary judgment bid because the court treated the certificate and a related report as hearsay: statements made out of court by third parties, with no witness who could authenticate them. The court noted they might be admissible under a business-records exception, but the defendant offered no declaration from someone with the knowledge to support it.

What that means for you: ask who can testify to how the record was created, and keep the underlying session data, not just the report. If a vendor cannot or will not produce the underlying capture, treat that as a red flag, the same way you would treat a traffic vendor who cannot show click logs. Our guide on how proof of clicks works uses the same logic: matching IDs and logs beats trusting a summary.

Certificates and third-party reports are pointers, not proof

Aged, resold and shared leads need extra checks

The riskiest lead is an old one. Consent does not travel with the handset. A phone number that belonged to a consenting consumer in March may belong to somebody else by November. For aged or resold leads, one compliance source recommends you query the FCC's Reassigned Numbers Database for each number and consent date, re-scrub against a do-not-call registry pulled within the last 31 days, and confirm the inquiry sits inside an established business relationship window.

The FCC safe harbor under 47 C.F.R. § 64.1200(m) protects a caller when the database returned a wrong answer. It does not protect a caller who never asked. So the query is part of the process, not an optional extra.

For shared leads, meaning one form that fed several buyers, get the full seller list and the exact consent text, and check that you are on it.

If your solo ad vendor sells you "fresh" email leads from a list rather than sending clicks to your page, the same skepticism applies. Duplicates, disposable addresses and recycled contacts are common problems, covered in our guide to spotting disposable emails in solo ads and our breakdown of lead theft and the 21 vetting questions.

A clean consent record answers one question: may you contact this person? It does not answer whether the lead is real, interested or likely to buy. One compliance resource puts it this way: a compliant lead is not automatically high-intent, and a high-intent lead is not automatically compliant. A record without suppression logic, consent context or reliable timestamps is incomplete.

The useful move is to connect the two. The same source notes that compliance data becomes performance data once it is tied to campaign outcomes. A rise in complaints from one traffic path may point to misleading creative. Low answer rates may mean people did not expect the call. High duplicate rates may suggest weak identity controls.

For a solo ad buyer, that translates into a simple routine:

  • Put tracking on every link so you know which vendor and which email produced each opt-in.
  • Start with a small test order and check clicks against your logs before scaling. Our 50 to 200 click test walks through it.
  • Tag each lead record with its source, so a complaint or a bad batch can be traced back.
  • Pick order sizes you can afford to learn from, and increase only after the data holds up.

If you are ready to place an order after vetting, our page on how to buy solo ads traffic covers the process step by step.

Handling opt-outs and keeping suppression records

Proof of consent has a flip side: proof that someone withdrew it. Since April 2025, a person can revoke consent in any reasonable way, such as replying "stop" or telling you on a call, and you have 10 business days to honor it. Plan for that.

  1. Log every opt-out with its timestamp and the method used.
  2. Keep a suppression list that every campaign and every tool checks before sending.
  3. Link the suppression record to the original consent record, so you can show the full history of one person.
  4. Apply opt-outs across channels your business uses, not only the one where the request came in.

For email specifically, a practical read on email marketing best practices covers unsubscribe handling and list hygiene. Good list hygiene also helps deliverability, which is why we recommend warming a sending domain properly before you mail a new list. See our walkthrough on warming up your email domain.

Retention: what to keep and where

Compliance does not require a particular technology. One checklist stresses that it requires proof of consent and record retention, not a specific tool. A spreadsheet can work if it holds the right fields and the underlying captures are stored safely. What matters is that you can produce the record quickly.

A workable setup:

  • One folder or system per lead batch, with the vendor name, order date and invoice.
  • The consent fields from the list above, stored as columns.
  • Page captures or session replays for the form versions in use.
  • A dated copy of any registry scrub you ran.
  • The opt-out log and suppression list.

Give the batch a name you can find in a year. If you cannot find the proof in five minutes, you do not really have it.

Our perspective

Most people who write to us after a bad buy have the same story: they trusted a summary. A vendor said the traffic was clean, the leads were opted in, the list was fresh. Nobody asked for the logs.

Consent works the same way as traffic quality. A claim is not a record. We teach buyers to ask for the evidence before any money moves: the click logs, the tracking data, the source of the list and, if a lead is going to get a call or a text, the consent record behind it.

That is why our 21-question vetting framework treats compliance as part of vetting, not a separate topic. A vendor who cannot show where leads came from or what people agreed to is telling you something. Start with a small order, track every click, and let the data decide whether you scale.

We are not lawyers, and nothing here replaces one. If you plan to call or text leads at volume, have a TCPA attorney review your forms and process.

Philip Coble

Put the vetting process to work

If you buy traffic to build a list, the cleanest consent record is the one you create yourself: your own squeeze page, your own disclosure text, your own captured opt-in data, with tracking on every click. Our framework shows you how to verify a vendor before you spend, and our advanced vendor vetting checklist gives you the questions to ask. For a quick look at how network-level checks fit in, read 3 compliance checks before you pay.

Soloadsguide

Start at SoloAdsGuide.com to get the buyer's checklist and the vetting framework before your next order.

FAQ

No. Those two fields show that something happened at a time from a device, not what the person agreed to. You also need the disclosure text, the form URL, the user-agent string, the named sellers and the specific action taken. A record missing the wording is hard to defend.

Can I rely on my lead seller's compliance promise?

No. The caller bears the burden of proving consent, so a promise from the seller does not shield you. Ask for the full record, read it against the form, and keep it with your order and invoice. If a seller will not provide it, do not contact those leads.

Not automatically. Phone numbers get reassigned, so a person who consented months ago may no longer own the number. Check the Reassigned Numbers Database for each number and consent date, re-scrub against a recent do-not-call registry pull, and confirm the lead is still inside a reasonable relationship window.

No. Consent shows you may engage. It does not show intent, a working email or a real person. Use click tracking, a small test order and source tagging to judge quality, and keep consent records to judge whether you may contact them.

Sources

Want Verified Traffic Without the Guesswork?

PulseTraffic screens every seller, filters bot clicks in real time, and shows you verified buyer traffic labels before you spend a dollar.

Phil, founder of SoloAdsGuide.com and solo ads expert since 2014
About the Author

Phil

Phil is the founder of PulseTraffic.app, PulseTrack.me, and PhilSoloAds. He's been selling solo ad traffic to affiliate marketers since 2014 and writes about what actually works, without the hype.

Ready to Buy Verified Solo Ad Traffic?

Stop guessing. Start buying traffic from vetted sources with built-in click fraud protection.

Visit PulseTraffic.app