Contests with social network login: how to ask for votes without scaring people

What does signing in with Facebook, Google or Apple do in a contest?

It lets the contest recognise a supporter through an account they already have, so they skip building a new one. The contest then counts votes per account.

The flow is short. The supporter presses a sign-in button, a window from the identity provider opens, they approve, and they come back to the contest as a known voter. The password is typed on the provider's own page, not on the contest site. A permission screen in that window lists what the contest has asked to receive, and that list is set by the organizer, so it differs from contest to contest.

Read the permission screen on your own test

This is the single most useful thing you can do before asking anyone. Press the button yourself, stop at the permission screen and take a screenshot. It shows what supporters will see, and it tells you which privacy questions to expect. If the screen mentions anything beyond basic identity, such as posting or access to a friends list, say so in your ask and let people decide.

Social login often sits beside other options. Some contests offer it next to a plain registration form, and some pair it with a captcha. Your test tells you which.

Which privacy worries will supporters raise, and what do you answer?

Five come up again and again, and each has an honest answer that does not oversell.

Two habits that build trust

Show the screenshot from your own test, with the permission screen visible. And never promise what you cannot know. You can describe what the screen says; you cannot tell anyone how an organizer stores data. When a supporter asks something only the organizer can answer, point to the organizer's contact address rather than guessing.

Which sign-in button should you point each supporter to?

The one that is already signed in on their phone. Choose by what is open on the supporter's device, not by which network you prefer yourself.

The contest decides which buttons exist; your job is to tell people which to press. A few patterns hold across audiences:

• A phone where the Facebook app is signed in usually makes the Facebook button a one-tap step. This often suits local, family and community audiences.
• An Android phone signed in to a Google account makes the Google button the shortest route.
• An iPhone may offer Sign in with Apple, which many privacy-minded supporters already use.
• A shared or work computer may have no social account signed in. There, the sign-in window asks for a password, which slows people and puts some off.

What to put in the ask

Name the button in plain words: press Continue with Google, then Allow. If you have more than one audience, write one line per group rather than one long paragraph. Where an audience mostly lacks the networks offered, tell them so early, and use channels such as email outreach to reach them with a different explanation.

Why does the sign-in window sometimes fail on a phone?

Most failures come from where the link was opened, not from the supporter's account.

A link tapped inside a social app often opens in that app's built-in browser. Sign-in windows can behave badly there, close themselves or show a blank page. Pop-up settings, private browsing and a missing signed-in session cause similar trouble.

Give supporters a short ladder to climb when it fails:

1. Close the window and press the sign-in button again.
2. Open the link in the phone's main browser instead of inside the app, using the menu option to open externally or copying the link.
3. Check that the account is signed in on that device, and finish any extra confirmation prompt the provider shows.
4. Try the other sign-in button, if the contest offers one.
5. Write to the organizer with a screenshot.

The line we draw

We never suggest borrowing a friend's account, creating spare accounts or using accounts nobody owns. Each social account belongs to one person, and the vote should belong to that person too. If a supporter has no suitable account, they can skip this contest without any pressure from us.

How do you word the ask around the permission screen?

Tell people the sign-in is coming, what it will look like and that they stay in control. Keep the tone of a favour, not a task.

For friends and customers:

Could you vote for my entry? [entry link]. You will sign in with Google or Facebook, and a screen will show what the contest receives before you approve. Take a look, and only continue if you are comfortable.

For a cautious audience, add the screenshot from your test and one line: This is exactly what appeared for me.

For a cold audience reached by ads, put a line on the landing message: Voting uses a social sign-in. You can review what is shared before you approve. That sentence cuts down on surprised bounces.

Pairing the ask with the right channel

A short chat message suits a one-tap login; a longer email suits a cautious audience that wants to read first. More variants are in the templates for asking people to vote, and the creative and copy service turns them into posts, images and short video in your voice.

What changes when entrants or voters are young?

A great deal. Social networks set minimum ages, and a contest with minors needs a parent or guardian to agree to the entry and the promotion.

In practice that means three rules on youth projects:

• We never ask a young person to sign in with an account they are not allowed to hold, or with a parent's account unless the parent is present and has consented.
• We address the ask to parents, teachers and club leaders, who can decide on a young person's behalf.
• We pick channels with each platform's age and privacy rules in mind.

Our page on beauty, kids, pets and school contests describes the consent steps we complete before any promotion starts. A social login also changes who is in the audience: some adult supporters sign in happily, while parents may prefer a contest that offers email instead. Your own test shows which option the organizer built.

How do you pace asks, measure them and begin?

Social login makes voting quick, so a good ask can bring votes in a rush. Spread asks over days and audience groups instead, because steady arrivals read as what they are and leave you time to fix wording between waves.

Measure with the same three numbers as every protection: tagged visits per audience group, the entry counter before and after each wave, and the replies from supporters. Add one extra: a tally of the failures reported, split into in-app window problems, missing accounts and privacy refusals. Each type has a different remedy, and the tally shows which one to fix first. How we read results covers the reporting.

One thing sits outside our reach: how the organizer treats accounts, for example whether new or inactive accounts count. We cannot see that, so we do not predict it.

To begin, send the contest link, your entry, the deadline and the permission screenshot from your test through the free contest analysis. We reply with the rules read, the wording for each audience and a plan. For other checks, see all voting protection types.

How it works

1. Test every sign-in buttonPress each one on a phone and a computer, stop at the permission screen and take screenshots.
2. Write the ask and a privacy answer sheetOne line per audience, plus short honest answers to the five usual worries.
3. Send small waves by audienceTagged links per group, with a troubleshooting message ready for failed sign-ins.
4. Log the failures by typeSort reports into app-window problems, missing accounts and privacy refusals.
5. Compare visits with the counterAdjust the wording after each wave and keep the final days for reminders.