CoinMarketCap community verification: account and badge review

Which account record are we preparing for review?

The first review set contains the community account URL, project name, official website, and public channels. Those 4 source groups let us compare the account with the identity your project presents publicly. The work concerns a verified CMC community account, its profile badge, and posting as the project.

It does not combine those tasks with a token listing or a visibility placement. That distinction helps your team define the requested outcome before collecting materials. For a listing application, see CoinMarketCap listing support. For a wider platform task map, use listings and verification.

The review is suited to teams that control an official community account and can confirm project details. You retain responsibility for factual claims and account authority. We arrange the supplied information into a readable request set. If the project has already contacted CoinMarketCap, include the submitted details. That gives us a clear starting record and reduces duplicate preparation. We flag differences for your approval rather than choosing a project identity on your behalf.

What identity signals should the CMC profile align?

The profile review compares the account name, project links, logo, and short description with the project's current public identity. These 4 identity signals form a practical consistency check. We record mismatches and return them to your team for confirmation before preparing the request.

Start by assembling the following:

• Account URL and the authorized account owner's contact.
• Official website and current social or community links.
• Project name, logo, and concise description used publicly.
• Any verification details previously sent to CoinMarketCap.

You receive a list of unclear or conflicting details, not invented credentials or unsupported claims. Your contact confirms the canonical project name and links. The account owner approves profile edits and any action made under the project name. If a tracker profile also needs correction, CoinMarketCap listing support addresses the listing task separately. For a different tracker, review CoinGecko listing support. Keeping the records separate makes each requested update easier to assign.

How does posting as the project fit the account handover?

The account owner remains the named approver for profile edits and project posts. Our work organizes the authorized posting workflow and clarifies which actions belong to your team. The project retains account control throughout the engagement.

Before work begins, identify one person who can confirm project facts and approve account-side changes. We then note who supplies information, who approves copy, and who performs each agreed action. This simple role record helps prevent mixed instructions from different team members. It also gives the account owner a clear basis for reviewing the prepared materials.

Posting as the project is part of the community-account outcome in scope. It is not a substitute for routine moderation or ongoing community operations. If your team needs continuing engagement work, see community growth and engagement. You receive the agreed profile and request materials, plus a handover of actions still assigned to your team. Account credentials are not requested through an unsecured channel. Access arrangements are agreed before any account-side coordination.

What happens across the 5 preparation checkpoints?

The work follows 5 checkpoints, from intake to a documented handover. Each checkpoint has a clear owner, so your team can see what is ready and what still needs approval. The sequence covers our preparation and coordination, not the platform's review.

1. Collect the record: You send the account URL, official links, project identity details, and prior submissions.
2. Compare the profile: We review the supplied identity signals and return specific questions or mismatches.
3. Confirm the facts: Your designated contact approves the details and any proposed profile text.
4. Coordinate submission: We support the agreed workflow with the authorized account owner.
5. Document the handover: You receive a record of prepared materials, completed work, and open actions.

The first checkpoint begins when the relevant links and a responsive project contact are available. Missing details are listed before the request is treated as ready. We keep the handover focused on what was prepared and who owns each next action. If your project is planning a separate visibility placement, compare it with trending campaigns. That work has a different purpose and should have its own scope.

Which parts of community verification remain CoinMarketCap's decision?

The platform controls the badge decision, review sequence, response time, and any continued verification status. Our commitment covers the agreed profile preparation, account-owner coordination, and handover record. The 5 preparation checkpoints do not convert agency work into platform approval.

For a useful internal record, keep the approved project details beside the submission materials. Assign one contact to answer factual questions and preserve the version the account owner approved. If CoinMarketCap requests clarification, your project supplies the accurate information and decides whether to make a change. We can organize the response materials within the agreed scope.

Before kickoff, confirm these points:

• Who can approve project identity details?
• Which account owner can perform the account-side actions?
• Has the team already submitted a request or profile information?

These checks help separate tasks we can prepare from decisions reserved to the platform. They also give your team a clear record of what was submitted and what remains pending.

How should you separate a badge request from other CMC work?

The account badge, an asset listing, and a visibility placement are 3 distinct work scopes. A community verification request concerns the account and project posting. A listing application concerns the asset profile. A visibility campaign addresses a separate placement objective.

A badge request does not submit an asset listing or arrange a placement. Likewise, a listing request does not prepare the community account. If your team has more than one goal, name the immediate priority and identify the person who can approve account actions. We will define the verification scope separately and give you a practical next-step list. To start, send the community account URL, official project links, and any prior submission details. We will review that record, identify missing decisions, and return the proposed scope for your approval.

How it works

1. Send the account recordShare the community account URL, official project links, and prior submission details. Name the person authorized to approve changes.
2. Review identity detailsWe compare the supplied profile and public project information. We return mismatches or questions for your team to resolve.
3. Approve the materialsYour project confirms the final details and proposed profile text. The account owner retains control of account actions.
4. Coordinate the requestWe support the agreed submission workflow with the authorized account owner and record the prepared materials.
5. Receive the handoverWe summarize completed preparation and identify follow-up actions assigned to your team or CoinMarketCap.