Give the right pair a place in your launch plan
Picture a research collective publishing weekly notes on the evening before an AMA. They want readers to find the same token and pair the team will discuss. We would first make sure the Birdeye destination in the brief matches that choice.
Birdeye trending support is a visibility placement coordinated around a selected token and trading pair. It can cover Solana, Base, or another chain when you provide the asset details and intended destination. We confirm what the request covers before arranging the work, so the team is not left guessing which pair the campaign refers to.
This is useful when a launch plan needs a defined on-chain discovery touchpoint. It is separate from a token listing or a change to your project profile. If you’re comparing discovery channels, start with trending campaign options. They can help you map which destinations belong in the same plan.
Say your project has two active pairs and an AMA focused on just one. We’d note the chosen pair in the written plan and keep the other one out unless you ask us to include it. That small clarification gives your team a cleaner handoff.
What should we check before choosing a Birdeye destination?
Start with the exact asset and pair you want people to find. A token name alone may not identify the right destination when the project spans chains or has several active pairs.
The chain and asset
Send the token name, contract address, network, and Birdeye asset or pair URL if you have it. We compare those details with the destination in your request and flag anything that needs your confirmation. If the project is active on Solana and Base, identify the asset for each network. Don’t group them under one general request.
The pair and the launch moment
Tell us which pair best fits the campaign and which alternatives to leave out. Include your preferred campaign window and any launch milestones that affect coordination. For example, the AMA may discuss a Base pair while your Solana pair remains the main project market. Tell us which one this request should follow.
If you’re weighing other on-chain destinations, compare the request with GeckoTerminal trending or DEXTools trending. Those are separate services, so the Birdeye brief should name only the work you want handled here.
Four checks make the kickoff easier
A short kickoff review helps both teams agree on the same asset, destination, and handoff. We use four checks before confirming the written plan:
- Match the asset. Share the token name, contract address, and network. We check that the information points to the asset you intend to feature.
- Choose the pair. Include the Birdeye asset or pair URL and identify the preferred pair. Tell us if another pair should be excluded.
- Set the coordination window. Note the campaign window you have in mind and any launch activity we should account for. We confirm timing after reviewing the request and availability.
- Agree on the handoff. Name a project contact who can approve the details. Tell us what delivery evidence your team needs, and we’ll record the agreed format in the plan.
Before we start, we return any missing or inconsistent details as a focused question. Your team can then confirm the brief without sorting through unrelated requests. A complete handoff also makes it easier to check the finished work against what you approved.
The written plan keeps the work easy to follow
Your written plan brings the key choices into one place. It records the destination, the coordination window, what we agree to do, and how we’ll show the work afterward.
| Part of the plan | What we agree together |
|---|---|
| Destination | Network, token, Birdeye page, and selected pair |
| Coordination | Requested campaign window and project contact |
| Work | The activity included in the confirmed request |
| Handoff | Evidence format and the destination it should reference |
This gives your team a simple way to review the request before kickoff and the delivery record afterward. The record names the selected asset or pair. Your team can check it against the plan instead of treating it as a general campaign update.
If the contract, network, or pair changes while we’re preparing, tell us before confirmation. We’ll revisit the details with you and update the written plan if needed. For another discovery surface, see DEXScreener trending; a separate destination gets its own details and handoff.
Keep Birdeye clear beside your other launch channels
Birdeye can sit alongside other discovery and community work, as long as each request has a clear destination. Keep the network, pair, coordination window, and evidence separate for each channel. Then your team can see what was planned for Birdeye and what belongs elsewhere.
For example, a project may want a Birdeye request and a separate CoinGecko search bar trending plan. We would list those as distinct activities rather than treating one as part of the other. You can also review trending campaigns to consider how other placements fit into the launch.
Birdeye controls how its interface displays and rotates assets. It also controls any review or ranking decisions; we can’t set a token’s position or duration. We commit to the coordination and evidence agreed in writing, not to a platform outcome.
To start, send us the Birdeye URL, network, contract address, preferred pair, campaign window, and evidence your team needs. We’ll review those details, clarify anything missing, and return a written plan for your approval.
How it works
- Share the destinationSend the Birdeye URL, network, contract address, and preferred pair. Add your project links, campaign window, and the contact who can approve the request.
- Check the asset detailsWe review the token and pair information against your chosen destination. If something is unclear, we ask you to confirm it before agreeing the work.
- Agree the written planWe record the destination, coordination window, work, and evidence format. Work begins after the plan and availability are confirmed.
- Coordinate the agreed workWe handle the confirmed coordination and keep your project contact informed about the handoff or any questions.
- Review the delivery recordWe share evidence tied to the selected destination so your team can check it against the written plan.
Frequently asked questions
What should I send first for a Birdeye request?
Start with the token name, contract address, network, and Birdeye asset or pair URL. Add your preferred campaign window and the evidence your team wants to receive. If you have several pairs, name the one this request should cover. A project contact who can confirm details helps us settle the brief without guesswork.
Can one request cover a Solana token and a Base token?
Yes, but list the assets separately so each network and pair is clear. For example, you can send one contract and destination for Solana, then a second set for Base. We’ll review each intended destination and confirm what the written plan includes before coordination begins.
What can my team check in the Birdeye handoff?
The record refers to the destination and work agreed in your written plan. We confirm the evidence format with you before kickoff, so your team knows what it will receive. If you need the record to identify a particular Birdeye asset or pair, include that when you share the URL.
When can the Birdeye work be ready?
We confirm timing after reviewing the asset, pair, campaign window, and availability. Once those details are agreed, the written plan sets out the coordination window and handoff. Complete information at the start helps avoid extra clarification, especially when a project has more than one chain or pair.
Can you promise a particular position or time in Birdeye trending?
No. Birdeye controls how its interface displays and rotates assets, along with any review or ranking decisions. We can commit to the coordination and evidence agreed in writing, but not to a particular position or duration. Your plan will make clear what work we are responsible for.
Does Birdeye support include DEXTools or DEXScreener work?
No, those are separate destinations and need their own agreed work. A Birdeye request identifies its own token, pair, and evidence format. If you want two or more platforms considered, list each one in your request so we can keep the activities and handoffs distinct.
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…