The short answer
Ask who actually generated the traffic, what the disclosure named, how many parties the merchant consented to, and whether the record can be produced with its timestamp and page URL. An aggregator sits between you and the consent event, so the further the chain runs the weaker the consent gets — and you are the one placing the call, whoever collected the record.
Aggregated leads are not automatically a compliance problem, but they are always a chain, and every link is a place where the record you would need to defend a call can go missing.
Ask down the chain
| Question | What a weak answer sounds like |
|---|---|
| Who ran the ad and hosted the form? | "A network partner" |
| Can I see the page the merchant saw? | "I can describe it" |
| Exactly what did the disclosure name? | "Our partners" |
| How many buyers is this consented to? | Silence, or a range |
| Can you produce the record with timestamp, IP and URL? | "It is in our system" |
| Do you scrub, and with whom? | A yes without a provider name |
Why the chain weakens consent
A merchant who filled in a form under one brand and agreed to hear from "funding partners" has consented to a category rather than a company. When your name appears on the caller ID, the consent has to stretch to cover a party the merchant could not have identified — which is exactly the argument that gets made against it.
If you buy aggregated anyway
- Get the disclosure text and a screenshot in writing before the first order, not after a complaint.
- Require that consent records be producible within a stated number of days, in the agreement.
- Scrub on your own side regardless of what the vendor says they do.
- Keep source tags on every record so that if one channel produces a problem you can identify the rest of it.
That last one matters more than it sounds. A complaint arriving on an untagged record tells you that something in your buying is wrong and gives you no way to find out what.