What TradeDesk does
TradeDesk shows what source-backed context is visible and gives freshness cues where source dates are available.
SOURCE GUIDE
How to read data coverage and freshness
What TradeDesk sources can cover, what no match means, what may be unavailable or plan-gated, and why freshness varies.
Search is the entry point.Review is the outcome.
01What this page explainsThe combined view of source categories, no-match states, plan access and source freshness.
02Who it is forUsers following older Data Coverage & Freshness links from product surfaces or footer navigation.
03After readingYou should know whether to open Data Sources & Coverage or Data Freshness & Limitations for more detail.
Quick answer
At a glance
The short version reviewers should understand before reading the detailed methodology.
What it does not do
TradeDesk does not guarantee every source is live, complete or matched for every company.
What users should verify
Check the source family, coverage label, freshness label and linked evidence before relying on a view.
Method
How it works
Simple steps first, with the detailed source and caveat text below.
- 01
Read coverage first
Understand which source categories are covered, unavailable, no-match or plan-gated.
- 02
Then read freshness
Check whether records are current from source, periodic, historic, lag-possible or date-unavailable.
- 03
Open source evidence
Use source rows and coverage notes for exact scope, dates and matching context.
- 04
Capture open questions
Use Review Workspace checks and notes where coverage or timing affects the review.
Product surfaces
What users see in the product
The methodology connects directly to surfaces where users inspect evidence or record review work.
Company OverviewThe starting view for identity, filings, status, source coverage and profile context.Operational FootprintMapped and unmapped location evidence, address/place context and operational signals where covered.Review WorkspaceThe workflow area for review cases, checks, owners, notes, monitoring and evidence links.Evidence modeA company-profile view for inspecting source-backed rows, grouped evidence and coverage notes.
Labels
What the labels mean
Short definitions for terms that appear across evidence, footprint and review views.
| Label | Meaning for reviewers |
|---|---|
| Coverage | How much relevant evidence is available in the current view. |
| Freshness | How recent the visible source context appears to be. |
| No match | No matched record was observed in the covered source and current view. |
| Unavailable | The field or source family is outside the current view, jurisdiction or pipeline. |
| Plan-gated | The source or detail may require another plan or enabled module. |
| Source lag possible | Upstream publication or ingestion may be delayed. |
Detail
Method detail and caveats
Use these sections when you need the source-level detail behind the quick answer.
What sources are covered
TradeDesk organises covered public, licensed and source-derived records into company profile, ownership, people, operational footprint, benchmark context and Review Workspace views.
Coverage depends on the source family, plan access, jurisdiction, source freshness and matching confidence. A source can be covered generally while still returning no matched record for a specific company.
| Source family | What it can support | Common limits |
|---|---|---|
| Company registry and filings | Identity, status, filings, officers, PSCs and statutory events. | Filing depth, disclosure level and update timing can vary. |
| Ownership and people records | Directors, PSCs, controlled entities and relationship evidence where available. | Names, roles and relationship paths can need source inspection. |
| Operational footprint sources | Locations, address/place evidence, public-sector records, IP records and other source-backed footprint signals where covered. | Not every address is operating evidence and not every record can be mapped. |
| Review Workspace records | Checks, notes, owners, monitoring and evidence links created by the team. | Internal review context depends on what users add and maintain. |
| Benchmark context | Observed signals compared with a selected reference group inside Review Workspace. | Benchmark context depends on cohort selection, coverage and available source families. |
Sources update on different timetables
TradeDesk combines datasets that do not all refresh on the same timetable. Some sources are updated frequently, some are updated periodically and some arrive as source-defined snapshots or extracts.
Because of that, recency can vary between companies, signal areas and jurisdictions.
Coverage shows how much relevant evidence is available. Freshness shows recency, not certainty.
Coverage labels
| Coverage label | Meaning | How to use it |
|---|---|---|
| Broad coverage | Multiple relevant source categories are available. | Review the evidence across signal areas and check dates. |
| Good coverage | Several relevant signal areas are covered. | Useful for contextual review, while depth may still vary. |
| Moderate coverage | Useful evidence exists, with clear gaps. | Treat uncovered areas separately rather than filling gaps by assumption. |
| Limited coverage | Only a narrow evidence base is available. | Interpret cautiously and avoid strong conclusions. |
| Minimal coverage | Very little relevant evidence is currently available. | Use linked sources and other checks before relying on the view. |
Freshness labels
| Freshness label | Meaning | How to use it |
|---|---|---|
| Current from source | A recent source date is known. | Check the evidence for exact timing. |
| Periodic source update | The source refreshes periodically rather than continuously. | Allow for publication or ingestion lag. |
| Historic snapshot | Data reflects a snapshot rather than a live register. | Read it as historic context. |
| Source lag possible | Upstream publication or ingestion may be delayed. | New information may exist but not yet be visible. |
| Date unavailable | A reliable timestamp is not currently shown. | Use source evidence for recency cues. |
Important limits
- Coverage varies by jurisdiction, company type, source availability and matching confidence.
- Plan access can affect which source families, evidence rows or specialist views are visible.
- A no match result means no matched record was observed in the covered source and current view.
- Unavailable means the source family or field is not present in the current product view.
- Registry data and licensed datasets may be corrected after TradeDesk first ingests or displays them.
- One page-level refresh date may not describe every signal on the page.
- Source systems can contain delays, omissions or later corrections.
Limits and caveats
What the view cannot prove on its own
These limits keep methodology pages readable without hiding uncertainty.
Use this combined page for orientation, then open the dedicated Data Sources & Coverage or Data Freshness & Limitations page for detail.
Coverage varies by source, jurisdiction, company type, plan access and matching confidence.
No match means no matched record was observed in the covered source and current view. It is not proof of absence.
Source rows and evidence groups support review. They are not certification, recommendation or final assurance.
TradeDesk helps teams organise and inspect evidence. The customer team owns the review purpose, policy context and recorded decision.
FAQ
Common questions
Why is there less information on some companies?
Observable coverage varies by source, sector, jurisdiction and company footprint.
Does low coverage mean a company is higher concern?
No. Low coverage means there is less relevant evidence available for that view.
Does a recent date mean the whole page is current?
Not necessarily. Different signal areas can refresh on different timetables.
Can TradeDesk change source data?
TradeDesk can correct its own presentation, but some upstream records must be corrected by the source authority.
What does plan-gated mean?
It means the source family or deeper detail may be available only on another plan or enabled module.
Related pages
Keep reading by review question
Evidence MethodologyHow scattered records are collected, matched, grouped and kept inspectable.Operational Footprint MethodologyHow to read mapped locations, source rows, evidence groups and footprint caveats.How to Read BenchmarksHow cohorts, coverage and observed signals should be read.How TradeDesk WorksThe product model, evidence links and review workflow.Data Sources & CoverageWhat TradeDesk can cover and how to interpret no-match or unavailable states.Review Workspace GuideHow reviews, checks, owners, notes and evidence links work together.Corrections & DisputesHow to ask TradeDesk to review something that appears wrong or incomplete.Trust CentreSecurity, AI transparency, legal and governance resources.