Third-party data

How third-party data enters enrichment workflows

Third-party data arrives when you buy, license, or otherwise obtain information you did not collect yourself. Advertising policy materials use that framing for user information from other sources 1. In sales ops the same idea covers firmographic appends, phone finds, and email waterfalls.

RichAPI's transparency page says waterfall lookups execute against licensed third-party data providers 2. Each response names the provider that answered 2. That receipt is how third-party coverage stays auditable next to first-party CRM fields.

A data broker is one supply pattern: an entity that collects and sells personal information 3. Enrichment vendors may license broker-like datasets, crawl public pages, or both. Ops rarely needs the full supply graph. It does need a named source on every write.

Third-party data is not automatically worse than first-party data. It is differently trusted. Verify emails. Check freshness. Refuse silent overwrites of customer-typed values. Pair third-party fill with match rate and fill rate on your own frozen sample.

Ads policy is stricter than CRM enrichment. Personalized ads rules allow using first-party data to create audiences, while using third-party data to create audiences for ads targeting is not allowed under the cited policy text 1. Keep ads audiences and CRM enrichment playbooks separate so policy language does not get copy-pasted into ops runbooks by mistake.

Credit math still applies. Profile and Company enrichment cost 1 credit per call and bill on any 2xx response 4. Third-party coverage that returns empty bodies still spends credits on those endpoints, so key quality matters before volume.

Store provider name, retrieval time, and field confidence when the API returns them. Without those stamps, third-party data becomes anonymous CRM fog within a quarter.

Contract language needs to match the runbook. If a vendor cannot state whether a field is modeled, observed, or inferred, treat confidence as low even when the UI looks polished. Third-party data without epistemology becomes decoration.

Segment risk by use case. Routing on industry is different from cold calling a direct dial appended from a broker-like path 3. Higher-risk channels need tighter verification and clearer suppression.

Watch for circular enrichment. If two tools enrich each other through shared reseller feeds, your CRM can converge on the same wrong title everywhere. Occasional human review on strategic accounts breaks that loop.

Document retention for third-party fields. When a person asks for deletion, you need to know which attributes came from licensed appends versus first-party collection so fulfillment is complete 12.

Price third-party coverage as a portfolio. One provider may win phones while another wins industry. Waterfall design exists so you are not forced into a single mediocre feed for every field 24.

Vendor concentration risk deserves a line in the runbook. If one third-party feed supplies most titles, a silent quality drop hits every sequence at once. Keep at least one alternate path for the fields that matter most 24.

Public sources and licensed feeds can both be third-party relative to your CRM. The operational difference is whether you can name who answered and when 2.

How to govern third-party appends

Write an allowlist of fields third-party sources may fill. Titles, industries, and employee bands are common. Customer-typed emails and billing contacts usually stay first-party only.

Require named providers. RichAPI already returns the answering provider on waterfall responses 2. Persist that field. If a vendor cannot name a source, treat the value as low trust.

Separate ads policy from CRM enrichment. The personalized-ads materials restrict building ad audiences from third-party data 1. Your enrichment runbook can still append firmographics for routing if legal review agrees.

Score providers on your file. Match rate next to fill rate and data accuracy is the usual framing for enrichment checks. Vendor slides are not a substitute.

Budget for verification after email appends. Waterfall email paths that bill zero on misses change the economics of trying multiple third-party sources 4.

Review decay. Third-party titles go stale. Schedule refresh windows the same way you schedule data decay checks on first-party rows.

Create an escalation path when third-party values conflict with customer tickets. Support should not guess. The runbook should say which stamp wins and who can override.

Keep a kill switch. If complaint rates rise after a new append source, pause that source without pausing the whole enrichment program.

Teach sellers a trust ladder that starts with first-party confirmed values, then verified channel fields, then licensed firmographics, then inferred scores. Messaging should get more cautious as trust falls.

Re-bid providers annually with the same frozen sample. Third-party markets move. Last year's winner can quietly decay while still billing.

Example of appending licensed third-party firmographics

A CRM import of partner leads has company domain and contact name but empty industry. Ops treats domain and name as partner-supplied inputs and industry as a third-party append candidate.

They run Company enrichment at 1 credit per call through RichAPI 4. The industry field is written with the provider name from the response where available and a retrieval timestamp 2.

Ads team wants the same file for Customer Match style uploads. RevOps refuses to copy third-party-enriched segments into an ads audience builder until legal reviews the personalized-ads constraints on third-party audience creation 1.

The enrichment scorecard still ships. Industry fill rate rises. Ad audience policy stays a separate ticket. That split keeps third-party data useful without dragging CRM ops into an ads policy violation.

Finance later compares credit receipts to industry fill on the partner cohort and approves the next partner sync under the same append rules 4.

A month later the same partner cohort is refreshed. Industry drift is measured against the original append stamps. Providers that slipped lose volume on the next sync 2.

Legal closes the ads-audience ticket with a written rule: enriched firmographics may stay in CRM routing, but ads audiences remain first-party only under the current policy reading 1.

Third-party data vs first-party data

Third-party data is obtained from outside your products. First-party data comes from people who interacted with what you operate.