feat: forward analytics identifiers on session creation - #23
Merged
Merged
Conversation
Hosts can pass an analytics() getter returning the visitor's current analytics distinct id and session-replay URL; both are read at connect time (they typically arrive after mount) and forwarded as analytics_distinct_id / analytics_replay_url on POST /widget/session so the platform can join demo calls to the visitor's analytics session. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
alec-bell
approved these changes
Aug 18, 2026
Contributor
|
🎉 This PR is included in version 1.3.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an optional
analytics?: () => WidgetAnalyticsContext | undefinedoption (hook + component + mount). When the host provides it, the widget reads the visitor's current analytics distinct id and session-replay URL at connect time and forwards them asanalytics_distinct_id/analytics_replay_urlin thePOST /widget/sessionbody, so the platform can join demo calls to the visitor's analytics session.connect()runs on a user click when they exist.POST /v1/widget/session) ignores unknown keys today and gains storage/emission in autophonix/thunderphone PR "feat(analytics): cross-tag replay+posthog sessions" — safe to ship in either order.Verification:
npm run lint(tsc) clean, vitest 8/8 (new exact-body test for the analytics fields), tsup build clean.🤖 Generated with Claude Code