> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://tieback.io/docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://tieback.io/docs/_mcp/server.

# Scan Visibility

> Resolver attempts, valid scans, geography, and product-level scan activity for Digital Product Passports, presented in one brand-scoped workspace.

Scan visibility is the foundation of Passport Intelligence. It tells you *whether* and *where* your Digital Product Passports are being scanned, *how* the resolver responded, and *which products and passports* are driving activity.

## What's Measured

| Metric                | Meaning                                                                   |
| --------------------- | ------------------------------------------------------------------------- |
| **Resolver attempts** | All requests reaching the resolver, including invalid and rejected ones   |
| **Valid scans**       | Resolver requests that successfully resolved to a passport                |
| **First scans**       | The first valid scan recorded for a token                                 |
| **Repeat scans**      | Subsequent valid scans against the same token                             |
| **Unique passports**  | Distinct passports involved in the scan window                            |
| **Unique products**   | Distinct products involved in the scan window                             |
| **Resolver outcomes** | Distribution of outcomes (resolved, not found, revoked, ineligible, etc.) |

## Geography

Scan activity is summarised by geography, giving operators a fast read on where passports are being interacted with across markets. Geographic breakdowns are interpreted alongside trust signals so that unusual cross-market activity can be reviewed in context.

A richer **geolocation confidence** model is on the roadmap and will further qualify location-based signals.

## Product-Level Visibility

Scan activity rolls up by product, so operators can quickly see which SKUs are generating the most consumer interaction and which are quiet. This makes it straightforward to:

* correlate scan activity with launches, campaigns, and seasonal demand
* identify products that warrant additional consumer-facing investment
* spot inactive products that may need investigation

## Resolver Outcomes

Scan visibility is intentionally honest about *all* resolver activity, not just successful scans. Outcomes such as rejected, revoked, or not-found requests are surfaced because they often carry the most operational and brand-protection signal.

## How Teams Use It

* **Operations** verify resolver health and coverage across markets
* **Brand & marketing** measure real-world engagement with launched products
* **Compliance** confirm that issued passports are reachable and being served correctly
* **Brand protection** correlate unusual scan patterns with [Trust Signals](/passport-intelligence/trust-signals)

For evidence-led review of suspicious activity, see [Trust Signals](/passport-intelligence/trust-signals) and [Investigation Timelines](/passport-intelligence/investigation-timelines).

## Related Docs

* [Passport Intelligence](/passport-intelligence/passport-intelligence)
* [Trust Signals](/passport-intelligence/trust-signals)
* [Investigation Timelines](/passport-intelligence/investigation-timelines)
* [Data and Privacy](/passport-intelligence/data-privacy)