TCPA Compliance for Legal Leads
What legal lead buyers require in the documentation trail, why the chain of custody matters here, and where the rules themselves are published. This page does not tell you what the law requires: it tells you where to read it.
This page describes commercial practice: what buyers of legal leads ask for, what they reject, and how the documentation trail is built in this industry. It deliberately does not summarize or interpret the TCPA, the Telemarketing Sales Rule, Do Not Call obligations or any state equivalent.
That is not caution for its own sake. These requirements are set by the FCC and the FTC and tested continually in the courts, and the position has moved repeatedly, including on what counts as valid consent and whether it can be shared between companies. Any summary written today can be wrong within months, and a wrong summary is worse than none. Read the sources below, and get advice on your own arrangement.
TCPAWorld: a specialist blog on TCPA litigation and FCC proceedings, published by a law firm rather than an independent outlet, and a running record of what is changing. Some posts are paywalled. This is the first place to look when you hear that something has changed.
FCC, telemarketing and robocalls and FCC, Do Not Call: the agency that makes and amends the rules implementing the TCPA.
FTC, Complying with the Telemarketing Sales Rule and the rule text: the registry and telemarketing requirements the FTC enforces.
All of these cover the United States only. If you generate or sell leads into other jurisdictions, the equivalent rules there are different and are not covered anywhere on this site.
Why this matters in legal
Every vertical that calls consumers has a documentation problem. In legal it is sharper:
- Case values make buyers careful. A firm weighing a claim worth a great deal has reason to ask who generated the lead, on what page, with what disclosure. A few networks that buy legal leads ask publishers to document or disclose their traffic sources before traffic begins.
- The documentation is part of the product. Several legal sellers advertise a consent certificate or documented consent with each lead, and one network that buys legal leads says leads missing consent records may be rejected.
- Claimants are already in contact with lawyers. A consumer who feels they were contacted improperly, in a vertical where everyone around them is a litigator, can be a well-connected complainant.
What buyers ask for, in practice
This is drawn from what sellers advertise and what networks that buy legal leads ask of publishers. It is not a statement of requirements, so check what each buyer asks for.
| Element | What it is | Why buyers want it |
|---|---|---|
| Consent certificate | A third-party consent certificate URL or token generated at submission | Independent evidence of what the consumer was shown and when. Several legal sellers advertise one, and one network says leads missing consent records may be rejected. |
| The disclosure text itself | The exact wording displayed on the form, and which companies it named | Buyers want to see whether they were covered by what the consumer agreed to, and may supply the wording they want. A few networks that buy legal leads require consent disclosures on publisher forms. |
| Timestamp | When the consumer submitted, and when you delivered | Establishes lead age, and anchors the record in time if it is ever questioned. |
| Source identification | The page, campaign and publisher: a sub ID on every record | Lets a problem be isolated to one source rather than tainting your whole file. |
| Scrub evidence | Records of DNC and litigator checks | Ask buyers running calling operations what they want checked, and keep a record of what you checked before the record reached them. |
| Retention | The above, kept and retrievable for an agreed period | A complaint can arrive long after the lead was sold, and one network requires publishers to produce records on request within a short deadline. Evidence you cannot retrieve is evidence you do not have. |
An avoidable failure: the consent certificate is generated correctly at capture and then dropped somewhere in the delivery chain, whether lost in a field mapping, truncated by a form post, or not carried through a CRM integration. The lead arrives without proof that exists on your side. Test end to end with real records into each buyer's endpoint, and check the token is intact on arrival rather than assuming it is.
The chain of custody problem
Legal leads can pass through several hands, and several companies in this market both buy and sell them: a publisher captures, a generator or aggregator buys and resells, a firm eventually calls. The commercial consequence is simple and worth stating plainly.
Whoever makes the call is holding a record someone else created. They did not see the page, did not write the disclosure, and cannot verify how the consumer was asked: they have only what was passed to them. That is why provenance gets questioned, and why a seller who cannot describe their own supply chain is hard to buy from.
The practical consequences:
- If you buy traffic, you inherit the capture practices behind it. Diligence on a publisher (seeing their actual pages, their actual disclosure wording, their certificate setup) is the same work as diligence on your own capture, and skipping it means putting records into live litigation that you cannot account for.
- If you sell, expect to be asked. Be able to say which source produced any given record, what that page said, and what evidence accompanies it.
An operational checklist
These are things to have in place, not rules to comply with. What the rules require is in the sources above.
-
Decide your disclosure wording with counsel, before launch
Not from a competitor's page, not from a template found online, and not from this guide. Buyers may tell you what they need named; your own counsel decides what you put on your page.
-
Generate a consent certificate on every form, from day one
It cannot be backfilled. Leads already sold without one stay without one, which is why this goes in before you buy a single click.
-
Put a sub ID on every record
So that a problem traced to one campaign or publisher can be isolated and cut rather than contaminating your whole file.
-
Run any scrubs inside the capture flow
If your buyers want DNC or litigator checks, run them before delivery, fast enough not to age the lead. A nightly batch is both too slow for the lead's value and too late to prevent a delivery.
-
Test the full delivery path per buyer
Send real records to each buyer's endpoint and confirm the certificate, timestamp and source arrive intact. Re-test after any change to your forms, your mapping or their integration.
-
Set a retention period and prove you can retrieve
Agree how long you keep the record and the evidence, then actually pull a random old record and see whether you can produce everything. A gap is better found now than during a complaint.
-
Diligence every supplier the same way
See their pages and their disclosure wording yourself. A supplier who will not show you is telling you something.
-
Watch for changes, and have someone whose job it is
Frequently asked
What is TCPA compliance in lead generation?
Used loosely in the industry, it means being able to show that the consumers in your file agreed to be contacted in the way they are being contacted, and holding the evidence of that. What the TCPA actually requires is set by the FCC and tested in the courts, and this page does not restate it. TCPAWorld tracks how it is changing. Your own position is a question for counsel.
Do I need a consent certificate to sell legal leads?
No rule on this page says you do. Commercially, several legal sellers advertise a third-party consent certificate with each lead, and one network that buys legal leads says leads missing consent records may be rejected. Which certificate to use is usually decided by what your buyers accept.
Can consent be shared between companies?
This question has been contested, and the answer has moved. It is exactly the kind of thing this page will not state, because a sentence written today can be wrong by the time you read it. Read TCPAWorld for the current state of play and the FCC for the rules in force, then take advice. Commercially, assume your buyers will have their own position on it and ask them what they require.
Who is liable if a lead I sold generates a complaint?
Not a question anyone should answer from a web page, and it depends on the facts, the contracts and the current state of the law. Commercially, indemnity terms can cover exactly this point, so expect it to come up in your contract and have your own counsel look at the wording rather than accepting a buyer's standard clause.
Does a DNC listing stop me selling a lead?
What is a litigator scrub and do I need one?
Checking numbers against commercial databases of known repeat TCPA plaintiffs and their attorneys before calling. TCPAWorld reports on repeat filers and the firms behind them. Whether you need one is a question for your buyers and your counsel, so ask each buyer whether they want it.
How long should I keep consent records?
What retention period applies is for the rules and your counsel to determine. The practical point this page can make: complaints can arrive long after the lead was sold, and evidence you cannot retrieve is evidence you do not have. Whatever period you settle on, test retrieval on a real old record rather than assuming your storage works.
Keeping the documentation trail intact at volume
Juiced is lead distribution software for companies that sell leads. You set the fields on each lead type, such as a consent certificate URL and a source sub ID, and mark them deliverable so they reach each buyer with the lead by webhook, email or text. Juiced has no compliance or scrubbing tools, so the evidence itself comes from your capture.
Scale your lead business, without limits
Juiced puts you in full control of your leads, routing, and revenue, so you can automate, optimize, and grow without chaos.
