A steadier launch rhythm for token page social signals

Where should token-page activity begin?

Start by matching each requested action to the correct token page. That simple check keeps your plan focused on the destinations your community uses.

1. Confirm the token name, ticker, contract address and network.
2. Share the exact page links for each platform you want included.
3. Mark the action for each page: watchlist add, reaction or vote.
4. Tell us your launch window and who can approve changes.
5. Review the agreed schedule and how we’ll record the work.

These are five practical checkpoints, not five separate campaigns. Our page-and-pair review checks that the links match your token and requested pair before we schedule anything. The trending campaigns overview can help place this work beside other launch visibility.

If you want the terms explained first, see token page social signals explained.

A launch rhythm your community can follow

A useful plan follows your launch communications instead of treating every page as an isolated task. We agree which actions belong on which destinations, then coordinate them in a paced sequence.

Picture a community manager covering three time zones after a quiet month of posting. The team is preparing a launch announcement, but its members check different market-data pages. We would confirm the selected pages, map each action to its destination and align the schedule with the announcement plan. That gives the manager one clear set of details to share with the team.

If DEXScreener is the main destination, our DEXScreener reactions service covers that page-specific work. For example, say your team wants watchlist adds on one destination and reactions on another. We keep those actions distinct in the plan and in the final record. A watchlist add is not reported as a vote, and activity on one service is not presented as activity on another.

For vote activity on DEXTools, see DEXTools votes and community trust score.

What arrives at each point in the work

You get a clear plan before activity, followed by a page-by-page record after the agreed work. Here is what your team can expect at each point.

Say your announcement moves after the schedule is agreed. Your approver can tell us, and we can review the timing before work proceeds. The record stays useful because it separates what was requested, what was completed and what appeared on the pages when checked.

This is not the same request as a featured placement. DEXScreener Boost and DEXTools Nitro are separate platform features; a request for either should be named clearly. You can review DEXScreener trending if your plan also includes platform-specific visibility.

For the corresponding DEXTools option, see DEXTools trending.

What can each platform decide?

Your team controls the token details it supplies, the pages it requests, the actions in the plan and the timing of its communications. Those inputs let us coordinate the agreed work and make the final record easier to check.

Each platform controls its page eligibility, interface, display and review decisions. That means agreed watchlist, reaction or vote activity cannot promise a trending position or lasting visibility. We commit to the specified work and report what we can verify on the selected pages.

Keep your own review simple: check the contract and network, then open every page link. Name one approver and note the launch milestones that matter to your team. Then consider the page record alongside community participation and your other launch activity. A page check shows what was visible at that time; it does not tell you how every visitor responded.

If the team is still deciding which activity fits, our trending campaigns overview can help frame the options. We can also keep this request limited to page actions, rather than blending it with a separate DEXScreener Boost request.

Bring the page details into one brief

A short, accurate brief gives us what we need to check the destinations and coordinate your selected actions. At Brand Community, we review the token and page details with your team before scheduling, then share the page references used for the delivery check.

Include these four items:

• Token name, ticker, contract address and network.
• Exact links to the CoinMarketCap, CoinGecko, DEXTools or DEXScreener pages.
• The action requested for each page: watchlist add, reaction or vote.
• Your launch window, any restricted periods and an approving contact.

If a page is missing or points to an unexpected pair, we’ll ask before proceeding. That small pause protects the accuracy of the plan and avoids sending work toward a page your team did not intend to include.

When you’re ready, send those details through contact. We’ll check the token-page links with you, confirm the action list and agree the schedule before activity starts.

How it works

1. Share the token pagesSend the token, network, pair and exact page links with your launch window. We check that the destinations match your brief.
2. Choose the page actionsMark watchlist adds, reactions or votes for each platform. We confirm the action list and how we’ll record it.
3. Agree the scheduleWe align the paced sequence with your launch communications and confirm it with your approver.
4. Check and hand overWe carry out the agreed work, review the selected pages and share the record with your team.