> 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.

# Engagement Insights

> Passport views, render success, performance, device mix, and CTA or link engagement, so teams can see how consumers actually use each passport.

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

| Metric                       | Meaning                                                  |
| ---------------------------- | -------------------------------------------------------- |
| **Passport views**           | Successful passport rendering events                     |
| **Render success / failure** | Whether the passport rendered correctly for the consumer |
| **Render performance**       | How quickly passports become usable                      |
| **Device & browser mix**     | Distribution of devices and browsers consuming passports |
| **CTA interactions**         | Engagement with calls-to-action embedded in the passport |
| **Link interactions**        | Outbound 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](/passport-intelligence/scan-visibility); for credibility interpretation see [Trust Signals](/passport-intelligence/trust-signals).

## Related Docs

* [Passport Intelligence](/passport-intelligence/passport-intelligence)
* [Scan Visibility](/passport-intelligence/scan-visibility)
* [Trust Signals](/passport-intelligence/trust-signals)
* [Consumer Experience](/passports/consumer-experience)