Only if you want “Continue with Facebook” in your app. Optional.
This page is optional. It's only needed if you want a "Continue with Facebook" button on your app's login screen, alongside email and Google.
If you don't want it, skip this page entirely and tell us — we'll leave the button out. Nothing else in your app depends on it.
Is it worth doing?
Honest answer: it depends on your market.
Facebook login raises sign-up rates in regions where Facebook accounts are near-universal. In markets where people mostly use Google or Apple accounts, it adds a button almost nobody presses — and Meta requires you to keep the app compliant with their platform terms, including a working privacy policy URL and periodic re-verification.
Adding it later is straightforward. If you're unsure, skip it, launch, and see whether anyone asks.
Setting it up
At developers.facebook.com → My Apps → Create App.
- Use case: Authenticate and request data from users with Facebook Login
- Name it your company name. This name appears on the login screen users see — "Continue as… to YourCompany" — so use the trading name your customers know, not an internal one.
- In the app dashboard, add the Facebook Login product
- Add both platforms: iOS with your bundle ID, and Android with your package name
Android also needs a key hash, which comes from our signing key. Ask us and we'll send it — it's not something you can generate yourself.
Going live
A new Facebook app starts in development mode, where only people listed as developers or testers can use the login. Real users get an error.
To switch it on: complete the Data Use Checkup, add a Privacy Policy URL (your website's privacy page is fine), then flip the app to Live at the top of the dashboard.
Skipping this is the usual reason Facebook login "doesn't work" after launch — the app was never taken out of development mode.
What to send us
Find these under App settings → Basic:
| Value | Where to find it |
|---|---|
| App ID | A long number |
| Client Token | Under Advanced on the same page |
| Display Name | Exactly as entered — it must match, character for character |
Ordinary email is fine for these; they're app identifiers, not account credentials.