What TradeDesk does
TradeDesk shows freshness context where available so reviewers can understand how recent the visible evidence appears to be.
SOURCE GUIDE
How to read freshness and limitations
How to read source timetables, freshness labels, update lag and limitations across TradeDesk evidence views.
Search is the entry point.Review is the outcome.
01What this page explainsWhy source dates, update lag, snapshots and evidence limits vary across TradeDesk views.
02Who it is forReviewers and operations teams who need to understand recency before relying on a source-backed summary.
03After readingYou should know why page-level dates are not enough and how to capture freshness concerns in review work.
Quick answer
At a glance
The short version reviewers should understand before reading the detailed methodology.
What it does not do
TradeDesk does not make every source live, remove upstream publication lag or guarantee that one page date describes every field.
What users should verify
Open linked evidence, check source dates, note snapshot timing and record follow-up checks when timing matters.
Method
How it works
Simple steps first, with the detailed source and caveat text below.
- 01
Read the source family
Different sources update at different speeds and may have different source-defined dates.
- 02
Check the freshness label
Use labels such as current from source, periodic update, historic snapshot or source lag possible.
- 03
Inspect linked evidence
Open source rows for exact dates, scope and source context where available.
- 04
Record timing concerns
Capture follow-up checks or notes in Review Workspace if recency affects the review purpose.
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 |
|---|---|
| Current from source | A recent source date is known for the visible item or source family. |
| Periodic source update | The source refreshes on a schedule rather than continuously. |
| Historic snapshot | The data reflects a point-in-time extract. |
| Source lag possible | Upstream publication or ingestion may be delayed. |
| Date unavailable | A reliable source timestamp is not currently shown. |
| Correction | An upstream or TradeDesk presentation change that can alter a displayed record later. |
Detail
Method detail and caveats
Use these sections when you need the source-level detail behind the quick answer.
Sources update on different timetables
TradeDesk combines datasets that do not all refresh on the same timetable. Some sources update frequently, some update periodically and some arrive as source-defined snapshots or extracts.
Because of that, recency can vary between company profile fields, ownership records, operational footprint evidence, benchmark context and review workflow records.
Freshness labels
| Freshness label | Meaning | How to use it |
|---|---|---|
| Current from source | A recent source date is known. | Open the evidence for exact timing and scope. |
| 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 and capture follow-up checks if needed. |
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.
How teams should use freshness context
Use freshness context as part of the review trail. If timing matters, open the linked source, check dates, record follow-up checks and capture unresolved questions in Review Workspace.
Freshness labels are there to support careful review. They should not be treated as automated decisions or guarantees about the current state of a company.
TradeDesk is a review aid. It does not certify, recommend or rate companies.
Limits and caveats
What the view cannot prove on its own
These limits keep methodology pages readable without hiding uncertainty.
One page-level date may not describe every source family or field on the page.
Registry data and licensed datasets can be corrected after ingestion or display.
Source systems can contain delays, omissions or later amendments.
Coverage and freshness are context labels, not automated decisions or guarantees.
If timing matters, the review trail should record what was checked and when.
FAQ
Common questions
Does a recent date mean the whole page is current?
Not necessarily. Different source families and signal areas can refresh on different timetables.
Can upstream records change after TradeDesk displays them?
Yes. Source systems can be corrected, amended or updated after an earlier ingestion or display.
What should reviewers do when freshness is unclear?
Open linked evidence, check source dates where available, and record any follow-up checks in the review workflow.
Related pages
Keep reading by review question
Data Sources & CoverageWhat is covered, what is unavailable and how to interpret no-match results.Evidence MethodologyHow scattered records are collected, matched, grouped and kept inspectable.Review WorkspaceHow to read the workspace and run the review workflow.Corrections & DisputesHow to ask TradeDesk to review an issue or data concern.Operational Footprint MethodologyHow mapped locations, source rows, group scope and footprint caveats should be read.Trust CentreSecurity, AI transparency, legal and governance resources.