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
  • Render Success and Performance
  • CTA and Link Engagement
  • Device and Browser Visibility
  • How Teams Use It
  • Coming Soon
Passport Intelligence

Engagement Insights

Was this page helpful?
Previous

Investigation Timelines

Next
Built with

Engagement Insights is the consumer-experience layer of Passport Intelligence. It moves beyond “was the passport requested?” to answer “did it render, did it perform, and did the customer engage with it?”.

What’s Measured

MetricMeaning
Passport viewsSuccessful passport rendering events
Render success / failureWhether the passport rendered correctly for the consumer
Render performanceHow quickly passports become usable
Device & browser mixDistribution of devices and browsers consuming passports
CTA interactionsEngagement with calls-to-action embedded in the passport
Link interactionsOutbound link clicks from the passport experience

Render Success and Performance

A scan that doesn’t lead to a successful, performant render is a poor consumer experience — even if the resolver returned a 200. Engagement Insights makes this visible by surfacing render success rate and render performance alongside view counts, so teams can detect:

  • regressions in template or theme rendering
  • performance degradations on particular devices or browsers
  • markets or audiences where experience quality is weaker

CTA and Link Engagement

Where passports include calls-to-action or outbound links, Engagement Insights captures interactions with them. This allows brand and product teams to measure which content actually resonates with consumers, and to iterate on passport configuration with evidence rather than instinct.

Device and Browser Visibility

Distribution by device and browser supports both experience-quality investigation and product decisions about where to invest in optimisation. This is particularly valuable for global brands serving many markets through a single passport infrastructure.

How Teams Use It

  • Digital & product teams measure consumer engagement and refine passport content
  • Customer experience monitor render quality across the device landscape
  • Brand & marketing identify content that drives interaction
  • Engineering detect template, theme, or performance regressions early

Coming Soon

Planned extensions include section engagement (visibility into which passport sections consumers actually read), action outcomes (telemetry on what happens after a CTA is taken), and additional engagement depth signals.

For activity-side context see Scan Visibility; for credibility interpretation see Trust Signals.