For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
  • Getting Started
    • Introduction
    • Getting Started
    • Tia — Operations Assistant
    • Architecture
    • Security Architecture
  • Onboarding & Plans
    • Onboarding Overview
    • Plans & Subscriptions
    • Tia Credits
  • Tenancy & Governance
    • Roles & Members
    • Audit Log
    • Notifications
    • Economic Operators
  • Authoring Studios
    • Content Studio
    • Theme Studio
    • Advanced Studio (Track B)
  • Product Module
    • Products
    • Custom Fields
    • Global Search
    • Identifiers
    • Product Import
    • Bulk Editing
    • Bulk Updates
    • Resolver & GS1 Digital Link
    • GS1 Digital Link Contract
  • Localisations
    • Overview
    • Market Packs
    • Multilingual Content
  • Domains & Custom Hostnames
    • Domain Architecture
    • Resolver Domain Flow
    • Custom Hostname Setup
    • DNS Setup Guide
    • Resolver & Passport Rendering
    • Custom Hostname Lifecycle
    • Troubleshooting
  • Passports
    • Overview
    • Passport Operations
    • Lifecycle States
    • Controlled Update & Break-Glass
    • Content & Templates
    • Themes & Presentation
    • Consumer Experience
    • Publication Lifecycle
    • Brand Setup & Readiness
    • Drafts
  • Passport Intelligence
    • Passport Intelligence
    • Intelligence Overview
    • Scan Visibility
    • Trust Signals
    • Engagement Insights
    • Investigation Timelines
    • Data & Privacy
    • Roadmap
  • Minting
    • Overview
    • Lifecycle
    • Architecture
    • Limits & Performance
    • Token Preview
    • Exports & Print Jobs
    • Carrier Output Profiles
    • Bring-Your-Own Serials
    • Security
    • FAQ
  • API Reference
    • API Credentials Guide
    • API: Credentials
    • API: Products
    • API: Identifiers
    • API: Import
    • API: Batches
    • API: Attachments
    • API: Bulk Updates
    • API: Minting
    • API: Resolver
    • API: Search
On this page
  • What’s Measured
  • Geography
  • Product-Level Visibility
  • Resolver Outcomes
  • How Teams Use It
Passport Intelligence

Scan Visibility

Was this page helpful?
Previous

Trust Signals

Next
Built with

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

MetricMeaning
Resolver attemptsAll requests reaching the resolver, including invalid and rejected ones
Valid scansResolver requests that successfully resolved to a passport
First scansThe first valid scan recorded for a token
Repeat scansSubsequent valid scans against the same token
Unique passportsDistinct passports involved in the scan window
Unique productsDistinct products involved in the scan window
Resolver outcomesDistribution of outcomes (resolved, not found, revoked, ineligible, etc.)
Activation effectsScan events that triggered first-scan activation

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

For evidence-led review of suspicious activity, see Trust Signals and Investigation Timelines.