Repository navigation
Add privacy-conscious visitor and Testnet tester analytics - #8
Merged
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.
What & why
Add Umami pageviews and explicit wallet, confirmed Testnet payment, payroll and disclosure events so onboarding can be measured without collecting private financial data.
Tracking runs only on the configured HTTPS production hostname. Payloads exclude wallet addresses, amounts, balances, transaction hashes, proofs, form input, raw errors and full URLs. Add
/privacywith opt-out and internal-testing exclusion, honor DNT/GPC, and keep automatic tracking/replay disabled. Tracker failures cannot interrupt wallet actions.ANALYTICS.mddocuments account configuration, recruitment checks and measurement limits for SCF evidence. The supplied public Website ID is recorded; visitor estimates and browser-reported events are explicitly distinguished from verified people or independently verified transactions.Area
App, analytics tests/CI, and documentation. No contract or SDK implementation changes.
How was this tested?
pnpm test:analytics: passed privacy filtering, configuration/hostname gates, preferences, DNT/GPC, pageview deduplication, queue limits, transport failure and submission-confirmation timing.pnpm --filter @lucent/app typecheck: passed.pnpm --filter @lucent/app build: passed with a dummy public Website ID.Checklist
Production activation
Configure the four
NEXT_PUBLIC_variables frompackages/app/.env.examplein Vercel Production, enable analytics, and deploy/rebuild the reviewedmain. Do not install a second default Umami snippet. Confirm a pageview and a disposable Testnet action in the live dashboard before recruiting testers. Live dashboard collection and payment smoke testing are still pending.