Repository navigation
Conversation
… developers Adds a Track User Analytics section to the Builder Codes for App Developers page describing what to measure and where each signal comes from, without naming analytics tools or wallet libraries. Supersedes #2077.
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Collaborator
🟡 Heimdall Review Status
|
Collaborator
Author
|
Closing in favor of #2077. The same changes have been pushed there so the review stays in one place. Generated with Toshi |
This branch was successfully deployed
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.
What changed? Why?
Adds a Track User Analytics section at the end of the Builder Codes for App Developers page. It tells app developers what to measure (active users, retention, conversion) and where each signal comes from, so they can build their own analytics now that Base Dashboard doesn't show these metrics.
This supersedes #2077 and addresses all review feedback there:
useAccountand the Wagmi note. The transactions step now points to onchain signals that work with any stack: the Builder Code suffix (linking to Verify Attribution), the sending wallet address, and receipt status (success vs. revert)Notes to reviewers
@youssefea, thanks for the review on #2077. This is the reworked version. I'll close #2077 once you're happy with this one.
Unchanged and out of scope: the Wagmi and Viem setup sections earlier on the page, and the older Dashboard references on the Overview page and under Verify Attribution.
How has it been tested?
node scripts/lint-mdx.json the changed file: 0 errors, 0 warningsnode scripts/check-terminology.js: passednode scripts/validate-docs-structure.js: passed (no navigation changes)mint devScreenshots
To be added. Verified locally at
/specifications/builder-codes/for-app-developers#track-user-analytics.Generated with Toshi