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.
That last row is the whole product. Developer reports are explicit that they count original commit authors in public repositories and undercount everyone else, closed-source teams included. Useful, and a different question from the one an investor asks when they want names.
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, product team credit, board standing, published work. That direction matters. This is not a scraped wallet list; it 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 honestly distinguish showed up from verified.Projects, companies, and opportunities too
The projects view covers products 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 pretending to be 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. 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 and sits on the Company plan. 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 plan acts on it. Attestations make participation durable, community boards make standing public, and programs bring the next cohort in. Tracker is built for ecosystems of several hundred projects. If yours is larger, raise it when you talk to us and we will tell you exactly what to expect at your size.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. That is the point. “At least this many, and here is how much of it is verified” is a number that survives the follow-up question, which a total you cannot substantiate does not. Read the on-chain figures the same way. Each carries its coverage label, and a metric the chain’s public data cannot support says unavailable rather than zero.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.
Choose a plan
What the Ecosystem plan covers and how billing works.