Connecting PostHog

If PostHog already records your sessions, UXSense analyzes those replays directly — nothing new to install on your site.

What you need

• A PostHog personal API key (starts with phx_) with access to session recordings. Create one in PostHog under Settings → Personal API keys.
• Your PostHog project ID (visible in your PostHog project URL or settings).
• Your PostHog host if you're on EU cloud or self-hosted (defaults to US cloud).

Connect

Go to Connections → PostHog → Connect, paste the key and project ID, and save. UXSense verifies access and shows the connected project and organization on the card.

What UXSense reads

Session recordings (the rrweb event streams PostHog stores) and their metadata — duration, click counts, the person's distinct ID. Recordings are fetched on demand during analysis, rate-limited well inside PostHog's API limits.

Backtest your last release

The moment PostHog is connected, you can run a backtest from the Drift page: UXSense reads a sample of your historical recordings, rebuilds the behavioral load map as it stood before your last release shipped, and scores that release's pull requests against it — "what Drift would have said before you shipped."

Two honest limits, shown on every backtest report:

• Path replay doesn't run on history. The deterministic tier needs a live preview deployment, and a shipped release's previews are gone. Backtests use the probabilistic signals only, so verdicts cap at WARN.
• Coverage is what it is. The report states what share of interactions resolved to stable element identities. Installing the UXSense snippet stamps your components and takes coverage to near-total for future checks.

Privacy: backtest recordings are fetched transiently and never stored — only the derived behavioral map (aggregate weights per element, no replay content) is retained.

Disconnecting

Disconnect from the same card any time. Analyses stop reading PostHog immediately; nothing keeps polling.