Which BNB Chain surface fits the next user action?
3 inputs shape the channel choice: the user action, the project proof, and the destination. PancakeSwap fits discovery in a trading context. BscScan helps interested users check an on-chain reference.
Binance Wallet is a separate visibility placement. Binance Square gives the project room to explain itself through updates. Choose the surface by the user's immediate need, not by the number of names on a channel list.
| Surface | Choose it if | Prepare first |
|---|---|---|
| PancakeSwap | Trading-context discovery is relevant | Token details, project description, destination links |
| BscScan | Users need to check an on-chain reference | Correct contract or address details, matching public information |
| Binance Wallet | A visibility placement suits the campaign goal | Approved creative, concise message, working destination |
| Binance Square | Project updates need explanation and context | Post drafts, editorial themes, account owner |
Keep each channel's role clear in the plan. A BscScan reference supports checking information; it does not explain the product. Binance Square posts can add context. A Binance Wallet visibility placement is a distinct activity. For a wider network comparison, see marketing by blockchain.
4 BNB Chain checks before activity goes live
4 checks connect project facts to campaign activity. They give each handoff a clear owner. They also stop the channel plan becoming a loose list of placements.
- Set the campaign goal: name the audience and the main action you want users to take.
- Check the source material: match public claims, contract references, links and project descriptions.
- Match channels to messages: give each selected surface one role and one destination.
- Confirm approvals and evidence: record who signs off and what proves activity is live.
Schedule content around the launch milestone. Do not treat posts as disconnected tasks. Before kickoff, agree what counts as completed work. For example, that could be a live post or an agreed placement. Keep the publication link, context and follow-up action together in the campaign record.
Our review checks public materials across pages, links and on-chain references. It shows whether those details agree. You get a specific list of conflicts to resolve before activity is scheduled.
If the project also serves other networks, keep BNB Chain information distinct. Coordinate it with Base marketing or Ethereum marketing where needed.
What we ask you to send
6 inputs let us check channel fit before recommending activity. Send existing materials, even if some are still being prepared. Mark anything pending so it is not mistaken for approved information.
- Project summary: one plain-language explanation of what is live and who it serves.
- Main action: the next step you want a user to take.
- Public links: website, social accounts and community destinations.
- On-chain details: relevant contract or address references, checked against project materials.
- Campaign assets: approved creative, token information and current descriptions.
- Approval contact: the person who can confirm edits and answer operational questions.
Then make the message fit the format. A short post needs one main point and a destination. An educational update can explain a user flow. A launch announcement should say what is available and where users can verify it.
We review public pages against the proposed message and links before scheduling. You get a checklist of missing or conflicting details. It is not a guess about what the project means.
For projects active on several networks, keep BNB Chain materials separate. Coordinate the wider TON marketing plan only where the same message applies.
How do BNB Chain campaign windows and reports work?
The campaign window is agreed for each activity before scheduling. Reporting records what went live, where it appeared, and which follow-up remains open.
| Surface | Activity | Window | What the report records |
|---|---|---|---|
| PancakeSwap | Project discovery activity | Agreed before booking | Confirmed activity and public evidence |
| BscScan | Reference and information check | Set by the campaign plan | Reference checked and any correction needed |
| Binance Wallet | Visibility placement | Confirmed for the agreed placement | Placement evidence and link, where available |
| Binance Square | Project updates | Matched to the posting plan | Published links and follow-up items |
Before the campaign starts, agree which links, screenshots or visible records confirm completion. Separate proof of publication from audience signals. Relevant questions, community discussion or data from your own analytics can inform the next decision. They are not substitutes for an activity record.
For Binance Square, keep the public description consistent across posts and destinations. If community activity is part of the plan, connect the posts to Binance Square community activity. That avoids creating a second, conflicting project story.
Platform decisions and the next BNB Chain move
Binance Wallet controls placement acceptance. Binance Square controls content distribution. Each platform also decides whether it features content or continues displaying it. We confirm only agreed work and document public evidence. No campaign partner can promise a feature or continued display.
- Reference risk: incorrect addresses or mismatched public information can undermine the project explanation.
- Message risk: unsupported claims can create confusion across posts and destination pages.
- Handoff risk: late creative approvals can leave planned activity waiting for project input.
Check each asset against the approved project source before it is sent for publication. Keep a fallback message ready if an asset needs correction. Record the person responsible for approving that change. For projects comparing several networks, Solana marketing offers a separate channel-planning reference.
Send us the project URL, contract reference, preferred launch window and current assets. We review the facts and channel fit. Then we send a written plan and quote within 2 working days.
Frequently asked questions
Which 3 project details should I send first for BNB Chain planning?
Start with 3 items: the project URL, the relevant contract or address reference, and your preferred launch window. Add the main user action you want to support. Those details let us compare project facts with the channels under consideration. We can then ask for any remaining material.
Can BscScan replace a project website or product explanation?
No. BscScan can help interested users check an on-chain reference. A reference alone does not explain the product. Send a current project description and the public pages that support it. We check that the address and campaign links match the information you have approved.
Are PancakeSwap and Binance Wallet the same kind of placement?
No. PancakeSwap can be relevant to discovery in a trading context. A Binance Wallet visibility placement is a separate campaign choice. We map each surface to a user need. Then we check the message, creative and destination that fit that activity.
How long does BNB Chain campaign preparation take?
Preparation follows the state of your assets and approval process. A ready project summary, checked address references and approved creative make the channel review more direct. Conflicting pages or missing approvals need attention before scheduling. You can send the current materials first, including items still in progress.
Can you promise that Binance Wallet or Binance Square will feature us?
No. Binance Wallet controls whether a placement is accepted. Binance Square controls how content is distributed. We confirm only agreed work and provide available publication or placement evidence. A platform may change how it presents content or how long it continues displaying it.
Tell us about your project
Answer four quick questions and a manager will send you a plan, timing and a price range within the hour. Everything stays confidential.
Loading the form…