Facebook Login Use Case

This document shows you how to create and customize an app with the Facebook Login use case in the App Dashboard.

This guide assumes that you have read and implemented the requirements for creating an app with Meta.

Step 1: Start the app creation process

There are a number of ways to create an app.

  • If you just came from the registration flow, click the Create First App button
  • If you are on the App Dashboard , click Create App in the upper right
  • If you are on the dashboard for an existing app and want to create a new app, select the dropdown menu in the upper left, and click the Create New App button

Step 2: Select your use case

Select the Authenticate and request data from users with Facebook Login use case.

You can click the chevron to the right of the description to view what else you can do with this use case and the requirements for this use case.

Click the Next button.

You will be able to customize your use case later on the app Dashboard.

Step 3. App details

In this step you will add:

  • A name for your app
  • The email address to be used to contact you about this particular app

Optionally, you can link this app to an existing Business Account using the dropdown menu, or you can add this later.

Click Create App to save your app's details.

Step 4. Customize your app

In the Authentication and account creation section you will see that Facebook Login and the public_profile permission have automatically been added to your app. This allows your app to use Facebook Login and ask your app users for permission to access the Default Public Profile information.

Click the Customize button.

Customize Facebook Login and requesting user data

Settings

Facebook Login allows you to control oAuth settings, and add a deauthorization callback URL and redirect URI validator.

Quickstart

The Facebook Login quickstart allows you to quickly get the code to implement Facebook Login into your app.

Permissions

You will see a list of permissions that are available in the Facebook Login use case with a full description and requirements for each.

  • email – Can be added if your app needs a person's email address
  • public_profile – Automatically added and can not be removed
After you add a permission to your app, you can see the status for that permission:
  • Ready for live mode – This permission has been approved in App Review and you can publish your app
  • Ready for testing – You can test API calls to endpoints that require this permission and complete App Review permission testing requirements
  • Verification required – This permission requires a verified Meta Business Account added to the app
You can also see the number of successful API calls you have made to endpoints that require each permission.

Step 5. Add more use cases

Click the Go back button in the upper right or Use cases in the left side menu to add more use cases to your app.

These are the use cases most commonly used with the use case you chose when you created this app.

Use caseAvailable permissions to add and code to implement

Use additional Facebook user data for personalization – Choose data permissions to personalize the app experience for users logging in with their Facebook account.


Only add permissions that your app will use.


All of these permissions require App Review before you can publish your app and go live.

user_age_range

user_birthday

user_friends

user_gender

user_hometown

user_likes

user_link

user_location

user_photos

user_posts

user_videos

Track engagement with App Events – Meta App Events allows your app to understand how people engage with your business across, devices, platforms and websites.

Meta App Events

Get real-time notifications with Webhooks – Get automatic HTML notifications when app users make changes related to the permissions that you've added to your app.

Meta Webhooks

Next Steps

Now that you have successfully customized your Facebook Login use case, let's update the settings for your app on the app Dashboard.

See Also

To learn more about the concepts, endpoints, and permissions mentioned in this document, please visit the following guides: