Repository navigation
Conversation
…sub-pages Co-authored-by: Toshi <toshi-noreply@coinbase.com>
Collaborator
🟡 Heimdall Review Status
|
youssefea
added a commit
that referenced
this pull request
Oct 6, 2026
* docs(builder-codes): add user analytics guide for app developers Adds a Track User Analytics section to the Builder Codes for App Developers page with a copy-paste prompt builders can give their coding agent to set up product analytics. * docs(builder-codes): make user analytics section tool-agnostic Addresses review feedback: removes the agent prompt, analytics tool names and Wagmi references; replaces them with steps describing what to measure and which onchain signals to use. * docs(builder-codes): drop deprecated base.dev attribution check Base Dashboard 2.0 no longer has the Onchain transaction-type view, so the Check base.dev step sent developers to a screen that no longer exists. Matches the overview page (#2024) and supersedes #2066. Co-authored-by: Toshi <toshi-noreply@coinbase.com> * docs(builder-codes): show where each analytics signal comes from Replaces the generic Track User Analytics steps with the concrete data sources behind each journey stage: - read the user identifier from the EIP-1193 provider (eth_requestAccounts, accountsChanged, chainChanged) and explain smart account addresses - list the in-app signal for open, connect, submit and success, including the wallet_sendCalls bundle ID and wallet_getCallsStatus resolution and EIP-1193 error code 4001 - explain where the user, Builder Code and success live for EOA transactions vs ERC-4337 UserOperations, the ERC-8021 suffix byte layout, and a Viem + ox function that returns one row per user action - define the active user, retention and funnel calculations Drops the guidance on which identifiers to collect; the section is about finding the right data, not prescribing a data policy. Co-authored-by: Toshi <toshi-noreply@coinbase.com> * docs(builder-codes): update Dashboard references for Dashboard 2.0 Base Dashboard 2.0 replaced the transaction and user counts with spot trading volume, borrow TVL and lending TVL derived from Builder Code activity, renamed apps to projects, and moved the code to Settings > Project Settings > Builder Code. - point the Builder Code location and code comments to the new path - document the Encoded String format (the ready-made dataSuffix) - replace the analytics benefit claims on the overview, app and agent pages with what the Dashboard shows today, linking to Track User Analytics for users, retention and conversion Co-authored-by: Toshi <toshi-noreply@coinbase.com> * docs: link to dashboard.base.org instead of base.dev base.dev now 302-redirects to dashboard.base.org. Points the Builder Codes links and the two data-driven-growth redirects straight at the canonical host. blog.base.dev, verify.base.dev and api.base.dev are separate services and are unchanged. Co-authored-by: Toshi <toshi-noreply@coinbase.com> * docs(builder-codes): drop Base Account example from smart account note Co-authored-by: Toshi <toshi-noreply@coinbase.com> --------- Co-authored-by: Youssef El Allali <youcefea99@gmail.com> Co-authored-by: Toshi <toshi-noreply@coinbase.com>
This branch has not been 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?
Removes the deprecated "Check base.dev" step from the Verify attribution sections of the two Builder Codes sub-pages, and renumbers the remaining steps (block explorer, then open-source tools):
docs/specifications/builder-codes/for-app-developers.mdxdocs/specifications/builder-codes/for-agent-developers.mdx#2024 (merged 2026-10-01, by a Builder Codes maintainer) removed this exact step from
builder-codes/overview.mdxand gave the reason "This is now deprecated". The same step was still on these two pages, which sent developers to the deprecated base.dev view to check attribution. After this change, all three pages give the same steps.Supporting sources:
Notes to reviewers
How has it been tested?
node scripts/lint-mdx.json both changed files: 0 errors, 0 warningsnode scripts/check-terminology.json both changed files: passednpm test: 113 passed, 0 failedgit grep "Check base.dev": no matches remainScreenshots
Not captured: the local Mintlify preview wasn't run for this automated change. The rendered change only removes one step from each list and renumbers the rest, as shown in the diff.
Generated with Toshi