What TradeDesk does
TradeDesk builds Footprint from source-backed location, address, place, operating and relationship evidence where coverage supports it.
METHODOLOGY GUIDE
How Operational Footprint evidence is built
How TradeDesk builds operational footprint views from mapped locations, source rows, evidence groups and coverage notes.
Search is the entry point.Review is the outcome.
01What this page explainsHow mapped locations, address/place evidence, operating evidence, group scope and quantity support should be read.
02Who it is forReviewers and buyers who need to understand Footprint before relying on map or location evidence.
03After readingYou should know why map markers, source rows, group-derived records and quantity labels need source inspection.
Quick answer
At a glance
The short version reviewers should understand before reading the detailed methodology.
What it does not do
TradeDesk does not treat every address as an operating site or treat a registered office as proof of occupation.
What users should verify
Check whether evidence is company-only or group-derived, mapped or unmapped, address/place or operating, and whether quantities are proxy-only.
Method
How it works
Simple steps first, with the detailed source and caveat text below.
- 01
Collect footprint records
Bring together covered source rows with address, place, location, environmental or operational context.
- 02
Separate evidence types
Distinguish address/place evidence from operating evidence before reading the footprint view.
- 03
Map what can be mapped
Show map markers only where location context is strong enough, while keeping unmapped evidence visible.
- 04
Apply company or group scope
Use explicit relationship evidence before showing group-derived footprint context.
- 05
Expose quantities and caveats
Label source-row proxies, quantity-not-ready states and registered-office caveats clearly.
Product surfaces
What users see in the product
The methodology connects directly to surfaces where users inspect evidence or record review work.
Operational FootprintMapped and unmapped location evidence, address/place context and operational signals where covered.Company OverviewThe starting view for identity, filings, status, source coverage and profile context.Ownership and peopleDirectors, PSCs, controlled entities and relationship evidence that explain who is connected.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 |
|---|---|
| Mapped location | A record has enough location context to appear on the map. |
| Unmapped location | A record has address or place context but cannot be reliably mapped in the current view. |
| Address/place evidence | Evidence that an address or place appears in covered records. |
| Operating evidence | Source-backed context that may support operational activity where coverage supports it. |
| Company-only view | Evidence matched directly to the selected company. |
| Group view | Evidence connected through explicit relationship metadata such as parent or controlled-entity records. |
| Quantity not ready | A source exists but does not yet provide a stable measured quantity for review. |
| Source-row proxy | A row count used as an evidence-volume indicator, not a measured volume. |
| Map marker category | A visual grouping for the type of footprint evidence behind the marker. |
Detail
Method detail and caveats
Use these sections when you need the source-level detail behind the quick answer.
What operational footprint is for
Operational Footprint helps reviewers inspect where a company appears to have location, address, place or source-backed operational context. It is designed for review, not as a complete map of every site or activity.
A footprint view can include company-only records and group-derived records where relationship evidence supports the connection. The page should make scope, source rows and caveats visible so reviewers know what they are looking at.
Mapped and unmapped locations
| Location state | Meaning | How to read it |
|---|---|---|
| Mapped location | A location has enough location context to appear on the map. | Use it as a place to inspect evidence, source rows and relationship context. |
| Unmapped location | A record has address or place context but cannot be reliably mapped in the current view. | Keep it in the evidence list and avoid treating map absence as record absence. |
| Grouped location | Several source rows have been grouped around a similar address, place or relationship context. | Open the group to inspect the rows and understand the grouping basis. |
Address, place and operating evidence
Footprint evidence can describe an address, a place reference or operating context. These are related but not identical.
A registered office, correspondence address or historic address may support identity or relationship context without proving current operation at that place. Operating evidence needs supporting source context, such as source rows that connect activity, assets, public-sector records, environmental records, IP records or other operational signals to the company or group.
Address evidence
Shows that an address appears in covered records. It may support identity, filing, correspondence or relationship context.
Place evidence
Shows that a place or location reference appears in covered records and can be inspected as part of the footprint trail.
Operating evidence
Shows source-backed context that may support real-world operational activity where coverage supports it.
Company-only and group scope
Company-only scope includes evidence matched directly to the selected company. Group scope can include evidence connected through parent, subsidiary, control or relationship records where TradeDesk has relationship evidence.
Group context should be read with care. A group-derived record helps reviewers understand connected footprint context, but it should not be treated as a direct company record unless the source evidence supports that connection.
Source rows and evidence groups
Source rows are the underlying records. Evidence groups are a review-friendly way to collect related rows around a location, source family, relationship or footprint theme.
The grouped view helps reviewers scan, but the source rows remain the inspectable trail. When the group view and source rows appear to differ, use the rows and coverage notes to understand why.
Quantity and source-row proxy
Some source families do not provide a review-ready quantity yet. In those cases, TradeDesk may show a source-row count or proxy so reviewers can see evidence volume without overstating precision.
A quantity not ready or source-row proxy label means the view is using available rows as a practical evidence indicator. Reviewers should inspect the rows before relying on the volume shown.
Registered office caveats
A registered office can be important company evidence, but it is not always an operating site. Some companies use professional service addresses, group offices or correspondence locations.
TradeDesk should keep registered-office evidence visible while distinguishing it from operating evidence where possible.
Group-derived evidence
Group-derived evidence depends on relationship evidence. The product should show why a location or footprint signal is connected to the company view, such as a parent, controlled entity or other relationship path.
When relationship evidence is unavailable or weak, group-derived footprint should be read cautiously and the source trail should be inspected.
Limits and caveats
What the view cannot prove on its own
These limits keep methodology pages readable without hiding uncertainty.
Coverage varies by source, geography, company type, plan access and matching confidence.
No match is not proof that a location, permit, record or activity does not exist elsewhere.
A registered office, correspondence address or historic address does not prove operational occupation.
Source-row counts are not measured volume unless the product labels a measured quantity as ready.
Group view uses explicit relationship metadata only and should not be read as direct company evidence without inspecting the path.
TradeDesk is a review aid, not a certification or footprint assurance.
FAQ
Common questions
Does an unmapped record mean the evidence should be ignored?
No. It means the record could not be reliably mapped in the current view. The source row may still matter.
Is every address an operating location?
No. Address evidence may describe identity, correspondence, registration or relationship context. Operating context needs supporting evidence.
Why can group locations appear on a company footprint?
They can appear when relationship evidence connects the company to a parent, controlled entity or group context.
What does source-row proxy mean?
It means a source-row count is being used as an evidence-volume indicator because a more precise quantity is not review-ready in that source family.
Related pages
Keep reading by review question
Evidence MethodologyHow scattered records are collected, matched, grouped and kept inspectable.How TradeDesk WorksThe product model, evidence links and review workflow.Data Sources & CoverageWhat sources are covered, what no match means and why recency varies.Review WorkspaceHow to read the workspace and run the review workflow.Corrections & DisputesHow to ask TradeDesk to review something that appears wrong or incomplete.Trust CentreSecurity, AI transparency, legal and governance resources.