Giveaway Multi-Accounting: How Sweepstakes Catch Duplicate Entries

Giveaway multi-accounting almost always starts the same way. Someone finds a giveaway with a decent prize, enters with their main email, then enters again with a second address. And a third. Maybe they fill in the bonus actions on each one. A week later the winner is announced, and it isn't them, or worse, they get an email saying all of their entries were disqualified.

Every entry. Not just the extra ones.

If you searched for a way to enter a lottery or giveaway from several accounts without that happening, this post won't give you one. What it will do is explain how sponsors actually spot duplicate entries, why the browser was never the deciding layer anyway, what the rules usually let you do to improve your odds, and how to push back if you were disqualified when you'd only entered once.

And if you're running the promotion rather than entering it, skip to the testing section near the end.

The short answer

Official rules almost always cap entries per person, and often per email address or per household. Entering under several identities breaks that cap. The usual result isn't "your extra entries get removed"; it's "every entry you made is void", sometimes with a ban from the sponsor's future promotions.

Using made-up or borrowed identities to win is a step further. Depending on where you live, that can be treated as fraud rather than a broken rule.

What irritates me is where that cap usually lives. Paragraph nine of a PDF, linked in six-point grey under the entry button, written by a lawyer who was paid by the clause. Then the sponsor acts wounded when people miss it. Put the limit next to the button or stop pretending it was obvious.

Why sponsors care so much about one entry per person

Giveaways aren't charity. A brand runs one to reach new people: email sign-ups, follows, people who might actually buy something later. Every duplicate entry is a fake "new person" the brand paid a prize to acquire. If one person submits a few hundred entries, the sponsor's numbers are polluted and, more to the point, every honest entrant's odds just shrank.

There's a legal reason too. In the US, broadly speaking, a promotion that combines a prize, chance and some form of payment can count as an illegal lottery, which is why sweepstakes remove the payment element ("no purchase necessary") and publish official rules. Those rules are the sponsor's promise that the draw is run fairly. A sponsor that knowingly lets one person stack entries is breaking its own published terms. Other countries frame it differently, but the "run it fairly, by your published rules" expectation is close to universal.

So when a sponsor checks for duplicates, it's protecting the people who played straight. Honestly, that's the part the "how do I get more entries" crowd tends to skip.

How duplicate entries actually get detected

Detection on a serious promotion is layered. None of these layers is decisive alone. What sinks a set of entries is that several of them point the same way.

1. The entry details themselves. This is the cheapest check and catches the most. Email addresses get normalised: Gmail, for example, ignores dots in the part before the @ and delivers "name+anything" to the same inbox, so j.smith+win1@ and jsmith+win2@ collapse to one person. (Google documents both behaviours in its Gmail help pages, and you can check them by emailing a dotted version of your own address.) Postal addresses get standardised. Phone numbers get compared. Names and dates of birth that repeat across "different" entrants stand out.

2. Network signals. Several entries from the same IP address in a short window get grouped. Some sponsors treat that as "one household". Datacenter and VPN ranges often push an entry into manual review.

Which brings me to a rule I think is lazy. One entry per household treats four unrelated adults in a flatshare as a single person because of how the landlord's router happens to be wired, and the people it penalises are the ones who did nothing wrong.

3. The device and browser. This is the layer people fixate on. A browser exposes a lot about the machine it runs on: how it draws a hidden canvas image, the GPU name reported through WebGL, the installed font list, screen size, timezone and language. Combine them and you get a fingerprint that's fairly stable for one device. We've covered the less obvious signals in our piece on audio, font and hardware fingerprinting. Some promotions buy this from fraud-scoring vendors such as SEON or Fingerprint (the company behind FingerprintJS); others rely on whatever their giveaway tool provides. A timezone that disagrees with the claimed location is a classic flag, the same timezone mismatch logic ad platforms use against fake clicks.

4. Behaviour. How fast forms get filled. Whether bonus actions are completed or just clicked. Ten entries that arrive at suspiciously regular intervals. Referral chains where every "friend" referred is another entry from the same cluster.

5. Human review. Many sponsors look at the shortlist before drawing, or at the potential winner afterwards. A reviewer with a spreadsheet of entries sees patterns no script needs to.

6. The prize claim. This is the one that matters most, and it has nothing to do with browsers.

The layer nobody can get around: claiming the prize

Before a prize changes hands, the potential winner is typically asked to confirm their identity and sign a declaration (often called an affidavit of eligibility) stating they met the rules, plus a release, and often tax details for larger prizes. Rules commonly say that if the winner can't be verified, or turns out to have broken the entry limit, the prize is forfeited and an alternate is drawn.

Think about what that means for multi-accounting. Entries under invented names can't claim anything, because the invented person can't prove they exist. Entries under your own name in several places get matched to you at exactly the moment you step forward. And entries under a friend's or relative's identity mean either they claim the prize (it's theirs, legally) or someone signs a false declaration, which is where a rules breach can start to look like fraud.

That's the contrarian bit, and I think it's the most useful thing here: the fingerprint debate is mostly beside the point. Even a browser that produced a genuinely distinct device for every entry wouldn't change what happens at the claim stage.

So if I were building a promotion tomorrow, I'd spend almost nothing on device fingerprinting and almost everything on the claim step. One signed declaration does more work than a year of canvas hashes. Most promotion tooling is built the other way round, which is both expensive and backwards.

What giveaway multi-accounting actually costs

Every entry void, not just the duplicates. Most official rules reserve that right in plain words.
Forfeited prizes, and in some cases a sponsor asking for a prize back if the breach comes out after delivery.
Bans from future promotions run by that sponsor, agency or giveaway platform.
Fraud exposure if fake or borrowed identities were used to obtain a prize. The specifics depend on where you live, and "it was just a giveaway" isn't a defence anyone should count on.
Your time. People who build spreadsheets to justify entry-stacking rarely count the hours. Compared with the expected value of one entry in a large draw, the maths is bad before any of the risks above.

Legitimate ways to get more chances

You've got more options than people assume, all inside the rules.

Daily or recurring entry. Plenty of sweepstakes allow one entry per person per day. Entering every day you're allowed to is the single biggest legitimate lever.
Bonus entries the sponsor offers. Following an account, referring a friend who genuinely enters, answering a quiz. These exist because the sponsor wants them. Do them honestly.
Alternative method of entry. Many US sweepstakes offer a free mail-in entry alongside the online one. Read the rules for how many mail-in entries each person may send.
Household members entering for themselves. If the rules allow one entry per person rather than per household, an eligible adult in your home can enter with their own details on their own behalf. If the rules say per household, they can't.
Entering more promotions rather than one promotion more times. Boring, effective.
Skipping the ones with no published rules. No entry limit, no eligible territories, no named administrator? My view: don't enter. There's nothing to hold the sponsor to when the draw happens.
For actual lotteries, the legitimate way to increase your odds is buying more tickets from the official operator. Online lottery accounts are generally one per person, with identity and location checks set by the operator. Stricter, not looser.

If you were disqualified and only entered once

This happens, and it's the most sympathetic reason anyone lands on a post like this. Shared Wi-Fi in a flat, a family computer, a university network, a mobile carrier that puts lots of customers behind one IP address: any of them can make honest entrants look like a cluster.

What to do:

Read the official rules and find the sponsor or the administrator (sometimes a separate promotions agency) and their contact details.
Write to them. Give the one email address you entered with, the date, and the plain explanation: "I share an internet connection with three flatmates who also entered with their own details."
Don't open new accounts to "fix" it. That turns a misunderstanding into an actual breach.
Accept that most rules make the sponsor's decision final. A polite, specific message is your best shot; a furious one isn't.

Expect it to be slow. Promotions inboxes are usually an agency alias nobody owns, and a fortnight of silence is normal rather than a signal. Genuinely frustrating, and I don't have a trick for it.

For sponsors, agencies and QA teams: where an antidetect browser legitimately fits

If you run promotions, you need to know your duplicate checks work before real entrants find the gaps. That's a testing problem, and it's one an antidetect browser handles well, because each profile behaves like a separate, internally consistent device.

On your own staging or test promotion, create entries from profiles with deliberately different device characteristics, locations and timezones, and confirm your deduplication groups the ones it should, your geo-eligibility check refuses the regions it should, and your winner-review step flags what it should. Each JustBrowser profile sets 40+ identity parameters together, which makes those test cases repeatable.

Sensible ways teams use JustBrowser around giveaways:

QA on your own promotion. Run the test entries above in staging or a test mode, never against a live promotion that real entrants are in. The same approach works for testing lead-gen forms across geos.
Checking geo-restricted eligibility. A promotion open to one country should show the right rules and refuse ineligible regions. Profiles pinned to different locales let you see what each audience sees.
Ad verification. Confirming the ads promoting a giveaway render correctly in each target market, as covered in our ad verification workflow.
Agency work in client-owned accounts. Staff logging into a client's giveaway tool or social accounts, with the client's permission, without mixing that client's sessions with another client's. Team seats are free, and a seat can run the profiles shared with it.

What JustBrowser is, in plain terms: a custom Chromium engine with native C++ integration (not an extension), patched on every upstream Chromium release, with 40+ identity parameters. It runs on Windows x64 and macOS (Apple Silicon). It doesn't include proxies; you bring your own and route them per profile. A local REST API and CDP let you script test runs with Playwright, Puppeteer or Selenium. If you're new to the category, what an antidetect browser actually is is a better starting point than this post.

What it isn't: a tool for entering promotions more times than the rules allow. We'd rather lose that customer.

Two sister products sit on the detection side of the same problem: ClickzProtect for bot filtering (its glossary of bot-detection terms pairs well with this post) and JustAnalytics for cookieless analytics on where promotion traffic really comes from.

Frequently Asked Questions

Is it against the rules to enter a giveaway with multiple accounts?

Almost always, yes. Official rules set an entry limit per person, and often per email address or household. Entries above that limit are void, and most rules let the sponsor disqualify every entry from a person who tried to exceed it, not just the extras.

Can an antidetect browser get me extra sweepstakes entries?

It would only be a way to break the rules, and it doesn't touch the check that decides the outcome: before a prize is released, the winner is usually asked to prove who they are and sign a declaration that they followed the rules. JustBrowser isn't built or sold for multiplying entries, and we won't explain how to use it that way.

How do giveaway sites detect duplicate entries?

By combining layers: normalised entry details (email variants, addresses, phone numbers), network signals such as shared IP addresses, device fingerprints from the browser, behavioural timing, referral patterns, manual review, and identity checks at prize claim. No single layer decides it; the cluster does.

I only entered once and was disqualified. What can I do?

Find the sponsor or administrator named in the official rules and contact them in writing. Explain the context, such as a shared household connection or a shared family computer, and give the single email you entered with. Rules usually make the sponsor's decision final, so be polite and factual, and keep a copy.

Is entering a sweepstakes multiple times illegal?

Going over an entry limit is mainly a rules breach that ends in disqualification. Using invented or borrowed identities to win or claim a prize is different: depending on the jurisdiction it can be treated as fraud. This isn't legal advice; if you're unsure, read the official rules and ask a lawyer where you live.

Run the promotion in a staging or test mode, create test entries that resemble separate devices, locations and households, and confirm the deduplication, geo-eligibility and winner-review steps catch what they should. Distinct browser profiles make that kind of QA repeatable.

Try JustBrowser

Native Chromium antidetect browser — not extension-based. Real C++ engine patches at the canvas / WebGL / audio / font / screen layer, so 40+ identity parameters are genuine, not faked. Local REST API and CDP for Playwright, Puppeteer, Selenium. Windows x64 and macOS (Apple Silicon). $9.99/month or $99.99/year. 7-day free trial, card required — cancel any time in the seven days and you are not charged. Unlimited profiles.

Get started → · How it differs from Multilogin / GoLogin / AdsPower