A contacts database built into your server dashboard for Discord giveaways. It turns the data participants submit across all your giveaways into one profile per member, so you keep a searchable, exportable audience instead of scattered per-giveaway entry lists.
Participant CRM
Every Giveaway Entry Builds a Member Profile You Keep
Link a task field to your CRM once, and every Discord giveaway you run keeps filling it: one profile per member, holding every email, handle, and country they ever submit. When a giveaway ends the list doesn't. Email the same members about your next drop, sync them to Brevo, and keep reaching them after they mute or leave your server.
The participant CRM is a contacts database built into your Discord giveaway dashboard. Each member who submits data through your giveaways becomes one contact. A member who enters six giveaways is still one profile, with everything they ever submitted collected on it.
What a profile holds is up to you, defined by reusable Data fields. Name, email, date of birth, and country come built in, and you add your own for anything else: a wallet address, a game username, an order number. Each field also decides what a re-submitted value does. Keep the latest, lock the first, or keep them all.
The contacts grid shows your whole collected audience at once. Search any value, filter by field or fraud flag, open a member for their full submission history, and export the current view to CSV whenever you want the data somewhere else.
How It Works
From a linked task field to an audience you can search, in the order the data flows
- 1
Set up your Data fields
A Data field is one reusable piece of information you want to keep about your members. Name, email, date of birth, and country come built in, and you add your own for anything else: a wallet address, a game username, an order number. Each field has a type (text, email, URL, date, country, or number) that validates what participants can submit.
Two settings shape how a field behaves over time. "On re-submit" decides what a new value does: keep the latest, lock the first value forever, or keep every distinct value. And a field marked as belonging to one person only, like the built-in email, watches for the same value appearing on two accounts.
- 2
Link a task field when you build a giveaway
When you build a custom task that collects data, every field you add has a "Save to Data field" option. Pick a Data field there and the task field is linked: its input type locks to match, it becomes required, and every value it collects flows into the member's profile from then on, in every giveaway that uses it.
Fields you leave unlinked stay on that single giveaway's entry. A throwaway survey question stays local, and the fields you will want again, an email, a wallet, get linked once and collect forever. You decide what is worth keeping.
- 3
Entries file into one profile per member
Each participant becomes one contact, tied to their Discord account. Whatever they submit lands on that contact. A first value fills the field, and a re-submitted value follows the field's own rule, replacing, locking, or adding alongside.
Every profile also carries a history: each value a member ever submitted, when, and from which giveaway. An email that changed two months ago is still there, one click deep, so a profile is never just its current snapshot.
- 4
Conflicts and shared values raise flags
Because the CRM knows each member as one identity, it notices when the story stops adding up. A locked field that receives a different value, a birthday that suddenly changes, flags that entry red as an identity mismatch. A one-person-only value showing up on a second account flags it yellow as a likely alt. Both land in the same per-entry fraud review as the bot and duplicate-device checks, and the member's profile lists the other accounts they share values with.
Giveaways can name bypass roles, VIPs or boosters who skip every task and enter instantly. The CRM covers them too. Mark the Data fields you need, an email or a delivery address, and a bypass member is asked to fill in whatever is missing before their instant entry counts. They keep their shortcut, and you still get the details you need to deliver their prize.
- 5
Work the grid, then take the data anywhere
The contacts grid is one row per member, one column per Data field. Search across every collected value, build filters like "country is France" or "email is not empty", filter to flagged members only, sort by any field, and show or hide columns to fit what you are doing. Open a member for their full profile, history, and linked accounts, and fix a typo'd value right there. Every edit is recorded in the server audit log.
Then take the data where you need it. Export the filtered view to CSV in one click, look a member up inside Discord with the staff-only /member-info command, or let the Brevo integration sync collected emails to your mailing lists automatically.
Setups This Enables
The same profiles, working three ways
Sponsored prizes with winner details already on file
A sponsor needs accurate recipient details before they hand over a funded account or a physical prize. Collect name, email, and the sponsor-specific account ID as required entry tasks, and by the time you draw a winner, everything delivery needs is already on their profile.
An email list that compounds
Link one email field and every giveaway from then on grows the same list. With the Brevo sync on, each new address lands in your mailing list on its own, so next month's reachable audience grows out of the giveaways you already run.
Winner handling without leaving Discord
A winner opens their claim ticket and your staff run /member-info right there to see the details already on file, the email or account ID that delivery needs. The reply is visible only to the staff member who asked, and the lookup lands in the audit log.
The Audience You Collect Is Yours to Keep
First-party data is the audience a platform can't take back
Your reach on Discord, like on every platform, is rented. A rules change, a ban, or a member muting your server cuts it to zero. A giveaway is one of the few moments a member willingly hands you first-party data, because they want to win. That data is the one audience asset fully under your control.
A typical giveaway tool leaves that data inside the single giveaway that collected it, so it expires with the giveaway. The CRM folds it into per-person profiles instead, so every giveaway you run compounds the same asset: a contact list that grows, stays current, and remembers each member across everything they entered.
Because the CRM knows each participant as one identity, the same profiles also work for you at entry time. A locked field that suddenly changes flags the entry, an email shared by two accounts surfaces as a likely alt, and your VIP bypass roles can be required to have their details on file before an instant entry. Collecting the data and trusting the data become the same system.
Combine It With
The features the CRM plugs into
Participant CRM Questions
Data intake, re-submits, alt catching, exports, and which plan you need
Related Features
Task Verification
How every task gets verified, from instant Discord checks to video codes.
Explore Task VerificationPrize Pools & Code Delivery
An encrypted prize code vault. Each winner gets a code reserved and revealed privately in their claim ticket.
Explore Prize Pools & Code DeliveryAn Audience You Own
One profile per member, built from the giveaways you were running anyway. Searchable, exportable, and yours for good.