Pre-Entry Tab
The Pre-Entry tab controls how entrants log in, what details you collect from them, and who can enter your Competition.
We need to know who each entrant is, so you can contact them if they win. Choose the ways entrants can log in from Allow login with: Email, Facebook, X, Google and Apple are all on by default. Click the × on any you don't want.
By default, entrants log in after completing their first action. If they log in with a social network, we prefill as much of their details as that network shares with us.
Turn on Pre-Entry Login to make entrants log in before they see your entry methods. It's handy for cutting down fraud, for example by only allowing Facebook or Google logins.
Entrants then see the login options first:
Logging in isn't an action on its own, so it doesn't earn an entry. Turn on Automatic Entry (it appears once Pre-Entry Login is on) to award an entry the moment someone logs in.
We add a Bonus action to your Competition when you save, and complete it automatically for each entrant who logs in.
You can change the text entrants see before and after completing any action with this format: Text before completion // Text after completion.
Build Competition Subscriber List is on by default. Entrants get a checkbox to hear about your future campaigns, and everyone who ticks it joins your subscriber list.
When your next campaign is ready, open its Promote tab to email your subscribers about it.
Promotion emails skip anyone who has already entered, and every email carries an unsubscribe link.
Ended Competitions keep getting visits from shared links and old posts. Turn on Capture Subscribers After Competition Ends and those visitors see a name and email form under the ended message, so they can still join your list.
Visitors who are already logged in subscribe in one click. They join the same list as Build Competition Subscriber List and appear on your Users page.
Signing up here sends no email and creates no entry.
Turn on Contestant Verification to make entrants prove who they are before they can enter. You can require:
- Email Address Verification: we email a 4-digit code to confirm the address
- Phone Number Verification: we text a 4-digit code (this needs a Twilio integration)
Verification is asked for even if Pre-Entry Login is off.
If you turn verification on after your Competition has started, entries already made by unverified entrants stay valid.
To verify phone numbers, connect Twilio first under Site Settings > Integrations and then refresh the editor. Twilio sends each entrant a 4-digit code by SMS on your behalf.
Every Competition asks for a name and email address. Click Add Field to collect more, like a phone number, address, company or your own question (on the Business Plan & above).
Pick from the ready-made fields or click Add Custom Field to build your own:
You can sync custom fields to your email provider, and they're included in Webhooks.
Turn on Minimum Age to set how old entrants need to be (for example 13, 18 or 21). We add a date of birth field to the entry form, and entrants under your minimum age can't enter.
You can change the field's Format, Label, Placeholder and Hint, and choose whether it's Required. Entrants see it alongside their name and email:
We support 27 languages out of the box. Pick one under Language and the widget and its emails are translated for you.
We don't translate text you've written yourself, only the fixed text in the widget and actions.
Your Competition is open worldwide by default. Use Include or Exclude locations to allow or block specific countries (not cities).
Entrants outside your allowed countries see a message that the Competition isn't available where they are.
We use MaxMind to work out where each entrant is. It occasionally gets an IP address wrong, and entrants can check their IP and request a fix.
Gleam checks every entry against 20+ signals and automatically invalidates suspicious ones. The Fraud Level slider sets how strict that is. It's High by default.
Off
- Very low invalidation threshold
- CAPTCHA disabled
- Login verification disabled
- No protection against malicious VPNs or data centres
- Entries from the same network or device are accepted (handy at live events), unless the entrant was previously banned
Low
- Basic invalidation threshold
- CAPTCHA enabled
- Login verification enabled
- No protection against malicious VPNs or data centres
Medium
- Medium invalidation threshold
- CAPTCHA enabled
- Login verification enabled
- Protection against malicious VPNs and data centres
High (Default)
- High invalidation threshold
- CAPTCHA enabled
- Login verification enabled
- Protection against malicious VPNs and data centres
Very High
- Very high invalidation threshold
- More aggressive Cloudflare challenges
- Login verification enabled
- Protection against malicious VPNs and data centres
Invalidated entries show as Invalid on your Actions / Entries page, so you can review them before you draw a winner. They don't count in your reporting, and entrants are never told.
Our team watches for fraud on every campaign. We may adjust your Fraud Level if it's blocking genuine entrants or letting too many suspicious entries through.
CAPTCHA is part of your Fraud Level. It's on from Low upwards, where we challenge entrants who look suspicious, and off when Fraud Level is set to Off.
See Next Article
How to Enter Tab
The How to Enter tab is where you choose the actions entrants complete to earn entries, and control when and how often they can do them.