Keep your coin growing
Use each creator dashboard signal for its real job while you maintain the project people return to.
TL;DR
- Keep the story moving with creator posts, milestone posts and broadcasts.
- Use Overview for lifecycle state, Earnings for the creator economy and Analytics for attention.
- Visits and engagement are not trades, holders or revenue.
Launch is the beginning of the relationship. Creator posts and milestone posts keep progress visible. Broadcasts turn an update into a shared moment inside the Coin Pod. Analytics shows how people find and engage with the project, while APIs let a team extend the token into its own apps and services.
Those tools remain relevant as the project moves through its lifecycle and graduation. The dashboard can show what changed; it cannot decide what deserves your attention or replace showing up for the community.
Give every dashboard area one job
| Area | Use it for |
|---|---|
| Overview | Lifecycle status, setup progress and market activity |
| Earnings | Accrued creator fees, distribution settings and available payout controls |
| Analytics | Page attention, referrers, geography and engagement signals |
| Venues | The coin’s shared visual space |
| Avatars | Published designs, minted avatars and sales activity |
| API keys | Software acting within the permissions granted for the coin |
Start with state: has the lifecycle or setup changed? Then look at market activity, community questions and unusual attention as separate signals. Use posts and broadcasts to explain meaningful changes; update the public identity only when the project itself has changed.
Keep attention separate from performance
Overview and the public coin page show buys, sells, price, volume and graduation progress. Analytics shows interaction with Orbit surfaces. A page view is not a purchase, a returning visitor is not automatically a holder and engagement is not revenue.
Some analytics can be empty or based on limited measurement while collection matures. Use it as directional context, not audited reporting or proof that an invitation created market value.
Protect powerful access
An API key secret is shown once. Store it in a secret manager or protected environment variable, grant the narrowest useful scope and revoke it if exposure is possible. A management key can perform meaningful actions for the coin.
Good to know
Avatar minting is available on Day 0. Trading remains paused platform-wide for the first four days; creator settlement and holder claims remain behind their current controls.
Common questions
What should I check when visits rise but trades do not?
Treat the rise as attention first. Compare referral and engagement context with the coin’s lifecycle, market activity and community questions before deciding what it means.
How should I announce a material metadata change?
Explain what changed and why through the project community, then verify the saved public page. The metadata checkpoint in Create your first coin remains the reference for the fields and preview.
What if an API key may have appeared in public code?
Revoke it, create a replacement with the narrowest useful scope and move the secret into protected configuration. Do not wait for evidence that somebody used it.