Repository navigation
Measure consented developer demo use and operation outcomes - #124
Merged
mattConnHarbour merged 5 commits intoNov 16, 2026
Merged
Conversation
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
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.
Add optional, consented measurement to the five developer demos and gallery using SuperDoc's existing GA4 property. Capture exposure, explicit selection, editor readiness, trusted editing, implementation-resource use, and bounded operation outcomes from real callbacks: review commands, field updates, synchronized collaboration, agent jobs, answers and saved versions.
The shared production-only adapter is installed during normal release assembly, not in downloaded local quickstarts. Refusal, withdrawal, DNT/GPC, opt-out and private URLs suppress tracking. Payloads contain fixed categories only, with canonical URL/title/referrer overrides. No document text, prompts, filenames, rooms, user identities or raw errors enter events. No CRM identification, new analytics provider or scheduler.
Validation: all 80 release/analytics script tests pass; all five apps build; Vue type check and six version-history server tests pass. Chromium desktop and phone-sized WebKit checked gallery-to-editor navigation, actual editor readiness and consent accepted/declined. QA intercepts Google transport and does not pollute production analytics. Production ingestion remains an explicit post-release check.
Companion changes add the homepage handoff event and complete-day Growth/weekly reporting. Preserve current demo versions and existing automatic release controls. This is a fork PR because the contributing account has read-only access to superdoc/demos; maintainer review/merge and the normal trusted release are required.
Privacy verification: Google now runs only in the isolated www.superdoc.dev frame introduced by homepage PR235. A real Google library test under the frame route CSP intercepted all collection requests, found no private synthetic document/title/room values, and sent zero production collection requests. Desktop Chromium and phone WebKit consent/decline checks pass. Later private navigation removes the frame without altering app navigation. Deploy homepage PR235 before this gallery release.
Prospective coverage: Josh clarified this standard applies to every future posted demo and example. The existing release test job now executes the real analytics adapter for every manifest route, checking stable IDs, readiness events and consent refusal; an unregistered future route cannot acquire transport. Future gallery entries fail CI until coverage is registered. README documents coordinated bounded frame/reporting updates, actual operation callbacks, post-release ingestion checks and format-specific limits. Preserve existing posts and private customer links.