Winners come out of a Fisher–Yates shuffle driven by crypto.getRandomValues, the browser's cryptographic generator. Every eligible entry carries the same odds, and no account wins twice in one draw.
FEATURE / GIVEAWAY
Threads giveaway picker:your replies are the entries.
Pick a post, load its replies, filter by the rules you announced, then draw. No giveaway bot to authorize, and the entry list never leaves your server.
Built in · Cryptographic shuffle · Nothing leaves your server
DRAW RESULTSFAIR DRAW
Shuffling entries…
3 winners from 248 eligible entries
Loading replies needs an access token with the threads_read_replies permission.
01 / HOW IT WORKS
Four steps from a post to a winner.
Everything runs on the dashboard you deployed, against the posts you already sync — the same place you read your analytics.
- Pick the post
Choose any synced post from the picker. The tool walks the Threads conversation endpoint page by page and loads up to 10,000 replies.
- Set your conditions
Switch on the rules you announced. Each one narrows the pool and the eligible counter updates as you type, so you know what you are drawing from.
- Add the prizes
Name each prize and how many winners it takes. One draw can hand out a grand prize and a batch of runner-ups at the same time.
- Draw and announce
Winners come out of a cryptographic shuffle. Copy the formatted result and paste it straight into your announcement reply.
02 / ENTRY CONDITIONS
The rules you announced, applied to every reply.
Conditions stack. Turn on what you promised in the post, and the panel tells you how many entries survive before anything is drawn.
threads-analytics · giveawaySTACKABLE
one-per-accountOne entry per accountSomeone who replied nine times counts once. Their first qualifying reply is the one that stays in the pool.
keywordMust include a keywordRequire a hashtag or phrase. Comma-separate several and a reply qualifies if it contains any one of them.
mentionsMust tag friendsSet how many @mentions a reply needs — the classic tag-two-friends rule, counted automatically instead of by eye.
deadlineReplied before a deadlinePick the exact cutoff. Anything that arrived after your stated closing time drops out of the pool.
has-textMust have comment textEmpty replies and bare reposts are filtered out, so a blank entry can't take a prize.
excludeExclude specific accountsSearch the entrant list and remove alt accounts, teammates, or previous winners. Your own replies are excluded before the list is even built.
03 / TRY A DRAW
Toggle the rules. Watch the pool change. Draw.
A working replica of the giveaway panel with twelve sample replies. Every switch filters the list in real time, and the draw runs the same cryptographic shuffle the product ships.
ENTRY CONDITIONS
PRIZES
- Mechanical keyboard× 1
- Sticker pack× 2
ENTRIES9 eligible3 filtered out
WINNERS · No draw yet — set your conditions, then draw.
- @mina.codes#giveaway count me in @leo.writes @hana.builds
- @leo.writes#giveaway been waiting for this one @mina.codes @noah.dev
- @hana.builds#giveaway @sora.ui @kai.exe you two need this
- @noah.devcount me in!
keyword - @sora.ui#giveaway @kai.exe
- @mina.codes#giveaway bumping this @sora.ui @noah.dev
dedupe - @kai.exe#giveaway 🎉 @mina.codes @leo.writes
- @ava.design#giveaway just made it @hana.builds @noah.dev
- @yuki.mdlove this dashboard
keyword - @theo.ships#giveaway @ava.design @yuki.md joining in
- @lila.dev#giveaway @theo.ships
- @ren.tech#giveaway @lila.dev @yuki.md good luck everyone
Sample replies, real logic. On your deployment the panel reads the actual thread of the post you pick.
04 / WHY IT'S FAIR
Randomness you can explain, on a server you own.
A giveaway is only worth running if the people who entered believe the result. Here is exactly what happens between the reply list and the winner.
The host's replies are dropped on the server before the pool is built, so answering entrants in the thread can't put you in your own giveaway.
Threads only exposes replies. Repost, follow, and like requirements have to be confirmed by hand on the winners — the panel says so instead of pretending otherwise.
Replies are fetched with your own encrypted token and filtered in your browser. No third-party giveaway service ever sees your entrants.
Replies need an access token with the threads_read_replies permission — the token guide covers it step by step.
Read the token guideRun your next giveaway on your own dashboard.
Deploy Threads Analytics, connect your Threads account, and the giveaway panel is already waiting in the sidebar — nothing else to install.
Entries, conditions, and results all stay on your deployment.