The layer this sits on
Tracker is additive to whatever measurement you already run, not a second opinion on it. Each layer answers its own question well and stops in a different place.
Commit counts measure output in public repositories. Tracker answers who is behind it and how much of that is confirmed by someone other than the person claiming it.
The cohort is chosen by the builders
Tracker’s builder cohort is everyone who lists your company as one of their ecosystems, enriched with what the graph knows: attested participation in your campaigns, verified roles, project team credit, board standing, published work. The cohort is people who claimed the affiliation themselves, and every claim carries its proof grade. Filters separate attested participants, attested winners, proof-backed engagement, and disputed records, so a program report can distinguish showed up from verified.Projects, companies, and opportunities too
The projects view covers the projects in your ecosystem with their on-chain context where the deployment supports it. Figures state their coverage and their timestamp, and an unavailable metric says unavailable rather than zero. Sections degrade independently, so one unavailable source empties its own panel rather than the page.Campaign connectors
Connectors bring in evidence from the platforms your community works on. Availability depends on your company’s plan. See pricing. The GitHub connector reads merged pull requests from public repositories using Dapping’s own access rather than any credential of yours, and turns them into skill evidence. It is a different mechanism from the tagged-repository signal a community board can count, which reads repository topics rather than merged work. Zealy and Galxe connect with your organizer keys and bring quest and points standings in as engagement context for your team; Galxe standings never become skill claims.What it pairs with
Tracker tells you what is there; the rest of the ecosystem toolset acts on it. Attestations make participation durable, community boards make standing public, and programs bring the next cohort in.The number you can defend
Tracker gives you a floor rather than a census: the cohort is people who chose to claim your ecosystem, so anyone building on you who has never touched Dapping is not counted. “At least this many, and here is how much of it is verified” is a number that survives the follow-up question. Read the on-chain figures the same way, starting from on-chain data and coverage.Continue on Dapping
Open your company hub
Open your company hub to see the builders and projects tied to your ecosystem.
Related guides
Use Ecosystem Tracker to understand projects, builders, companies, and opportunities
The segment-by-segment guide to the Tracker.
Attest participation at scale
Turn program participation into the verified signal the Tracker reads.
Plans and billing
See a hub’s current plan, change one, and read what no plan changes.