Analytics and Tracking

Third-Party Data

Also called 3PD, purchased data, broker data

Audience information bought or licensed from an outside source rather than gathered from your own customers.

Quick facts: Third-Party Data

Category
Analytics and Tracking
Also called
3PD, purchased data, broker data
Level
Intermediate
Affects
Targeting accuracy, compliance exposure, email deliverability
Where to see it
Ad platform audience managers, CRM enrichment tools, data vendor contracts
In this article4
  1. How third-party data works
  2. Why third-party data matters
  3. Where third-party data goes wrong
  4. How to act on it

How third-party data works

A data broker gathers information from many places at once — websites, apps, panels, loyalty schemes, public records, offline purchase histories — then combines it into segments and licenses those segments to advertisers. You might buy them to target an audience on an ad platform, or to append attributes such as company size or income band onto records you already hold.

The defining feature is the missing relationship. You have never met these people, and in most cases neither has the broker. The chain between the person who ticked a box on some unrelated site and the segment you are buying can be several companies long, and none of them is you.

Why third-party data matters

Mostly it matters because it is shrinking, and plans built on it need rewriting. Browsers have removed or restricted the shared identifiers these segments depended on, mobile platforms made cross-app tracking a per-app choice, and the large advertising platforms have closed their own third-party segment marketplaces. What used to be a purchase is now increasingly something you have to build from your own customers.

The legal position pushes the same way. Consent obtained by a broker rarely names you specifically, so leaning on it is fragile, and in California passing or receiving this kind of data can count as a sale or sharing with all the obligations that follow. It is one of the few areas where the compliance risk and the commercial trend point in the same direction.

Where third-party data goes wrong

Accuracy is the quiet problem. You cannot audit how a segment was assembled, how recently it was refreshed, or what proportion of it is inference rather than observation, so a poor list and a good one look identical in the invoice. Appended fields age fastest of all — job titles and company details change constantly, and a stale append quietly misdirects your targeting for months.

The other failures are more clear-cut. Assuming the vendor’s paperwork transfers your responsibility, when you decide what to do with the data and therefore carry the duty. Merging bought records into a mailing list, which damages deliverability as reliably as it breaks the law. And cold emailing a purchased list, which in most of the markets I work in is simply not permitted.

How to act on it

Treat it as the last option rather than the first. Build first-party data and ask customers directly wherever you can, because those sources are cheaper, more accurate and yours to keep.

If you do buy, ask specific questions before signing: where the data originated, the exact consent wording the person saw, how often it is refreshed, and whether the contract indemnifies you if the provenance turns out to be poor. Test a small slice against records you already trust before scaling. And never let bought records flow into an email list — use them, if at all, for advertising audiences where the platform sits between you and the person.

Do and do not

Do

  • Ask for provenance, consent wording and refresh frequency
  • Test a small sample against customers you already trust
  • Build first-party sources before buying anything

Do not

  • Email a purchased list under any circumstances
  • Assume the vendor's paperwork removes your responsibility
  • Merge bought records into your customer database unchecked

Questions people ask about this

Can I email a list I bought?

In most markets I work in, no. Consent to receive marketing has to be given to you, and a broker's permission does not transfer with the file. Beyond the law, mailbox providers judge you on complaints and spam-trap hits, so a purchased list can damage the deliverability of the messages your real subscribers asked for.

Is third-party data the same as third-party cookies?

They are related but not the same. A third-party cookie is a technical mechanism set by a domain other than the one being visited, often used to build these segments. Third-party data is the information itself, which can also come from offline sources, panels and data partnerships. Losing the cookie shrank the supply, but it did not remove the category.

What should I ask a data vendor before buying?

Where the records came from, the exact wording people agreed to, how the file is refreshed and how old the oldest records are, which regions it covers, and what the contract says if the provenance is challenged. Ask for a sample you can test against customers you already know. Vague answers to any of those are the answer.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.