Airdrop campaign plan: eligibility, screening and claims

4 records that make an airdrop report useful

4 report rows connect campaign rules to the final distribution. Keep each record tied to a decision your team can explain. Do not rely on entry counts alone.

Use the same labels from announcement through wrap-up. Keep a version of the rules, the final eligible list and the allocation record. Assign an owner for each file before promotion begins.

A useful report also names open questions. Separate an unclaimed allocation from a failed transaction. Those cases need different follow-up. A token launch marketing checklist can place the airdrop alongside other launch tasks. Keep their reporting separate.

Which eligibility rules should participants see first?

3 rule groups make eligibility easier to understand: entry conditions, qualifying actions and exclusions. Put them on one canonical page before announcing the campaign.

Entry conditions should identify the supported network, required wallet details and participation window. Qualifying actions should explain what evidence counts. They should also show where to submit it. Exclusions should explain how the team handles repeat entries, missing evidence and rule conflicts.

Then check the rules from a participant’s view:

• Clarity: can a person tell whether they qualify before starting?
• Evidence: is each requested action verifiable by the review team?
• Exceptions: does the page explain how unclear cases are assessed?
• Changes: is there one official place for corrected instructions?

Do not revise criteria silently after entries arrive. Publish a correction and keep the earlier version. Explain what changed. If the project is preparing listings, keep those decisions separate. CoinGecko listing guidance and CoinMarketCap listing guidance cover different review processes.

3 screening checks before you finalize eligibility

3 checks give reviewers a consistent starting point: wallet activity, repeated submission details and timing patterns. Treat each as a reason to review. None is automatic proof that an entry should be excluded.

Set the review procedure before entries open. Write down which signals trigger a second look. Name who can approve an exclusion. Record the reason for each decision, including accepted entries that needed review.

• Wallet evidence: compare only activity relevant to published criteria.
• Submission details: look for repeated information that needs clarification.
• Timing patterns: flag clusters for review without assuming intent.
• Human review: document how reviewers resolve uncertain cases.
• Appeals: provide a route for participants to question a decision.

Ask only for information the team needs. Never request private keys or seed phrases. Limit access to participant details. Give access only to the people responsible for review. Explain how the data will be used.

If community tasks are part of eligibility, plan them separately from distribution rules. The Telegram community guide can clarify channel roles and participant instructions.

5 planning steps from first message to live

5 steps move the campaign from an initial request to a live participant path. Give each step a decision owner. That keeps approvals from getting lost between teams.

1. Set the objective: Name the audience and the action the campaign should support. Choose evidence you can review later.
2. Draft the rules: Write entry conditions, qualifying actions, exclusions, timing and the support route. Check every task against the rules.
3. Set screening and allocation: Select review signals. Decide how to handle edge cases. Document the allocation method.
4. Test the claim path: Walk through the instructions with the intended wallet and interface. Check network selection, address formatting and fallback messages.
5. Publish and review: Point every announcement to one authoritative rules page. Track questions, decisions, claims and follow-up evidence.

A launch date should follow the readiness check. It should not replace it. If reviewers disagree on an eligibility edge case, resolve it before entries open. If a claim instruction changes, update the canonical page. Update the messages that point to it, too.

1 rules page, 3 communication jobs

1 canonical rules page should anchor 3 communication jobs: explain participation, answer support questions and announce changes. Social posts can summarize. Participants still need one source of truth.

Prepare these items before promotion:

• Announcement: purpose, eligibility, task path and official links.
• Support replies: answers for wallet, evidence and claim questions.
• Status update: a format for corrections or distribution notices.
• Channel ownership: the account that can publish an official change.

Check that each link reaches the intended project page. Keep reward and allocation language consistent across posts. Tell participants what information the team will never request. Show them how to identify official project accounts.

If creators will promote the campaign, provide one written set of rules. Review their summaries before publication. The crypto KOL campaign guide covers creator briefs and review responsibilities. Keep creator posts subordinate to the canonical page. A short post should not introduce new eligibility terms.

Which distribution and claim path fits your review process?

3 common models cover most planning choices: direct distribution, participant claim and tiered allocation. Match the model to the approved eligible list. Also consider the support your team can provide.

For any model, ask a second reviewer to compare the final allocation with the approved list. Test the participant path. Prepare a response for delayed or unclear transaction status. On-chain transfers cannot be reversed through campaign support. Network confirmation and wallet display remain outside the project’s control.

A managed airdrop campaign can support eligibility review, communications and distribution records. Send DigitalMedia1 your draft rules, intended audience and proposed claim model. We can review the decision points and return a practical checklist.

How it works

1. Name the objectiveSet the audience and the action the campaign should support. Choose evidence you can review after distribution.
2. Write participant rulesDocument entry conditions, qualifying actions, exclusions, timing and support. Check the wording against every campaign task.
3. Set review and allocationChoose screening signals and record how reviewers handle uncertain cases. Confirm the allocation model before entries arrive.
4. Test the participant pathWalk through the instructions with the intended wallet and interface. Check network selection, address details and fallback messages.
5. Publish and reportUse one official rules page and monitor participant questions. Compare the final records with the campaign objective.