How to set up a facebook app

App Dashboard - Meta App Development - Documentation

This document describes the App Dashboard interface and its settings. If you have just created a new app, you do not need to read all of this documentation and configure dashboard settings now; you can start building and testing right away and return to these documents to learn about relevant dashboard settings as needed.

The App Dashboard allows you to configure settings that may be required by the products, APIs, and SDKs that your app will be using. It also provides tools to aid with app development, such as API usage meters, the ability to create test users and test pages, and the ability to assign roles to other people who may be helping you with development. The dashboard is also used to begin the App Review, Business Verification, and Individual Verification processes, if required.

To access the App Dashboard, go to the Apps panel and click on the name of the app you'd like to configure. This will load the app in the dashboard and you can then adjust its settings.

Apps Panel

The Apps panel serves as the App Dashboard's entry point. It displays basic information about each of your apps: their IDs, your role on each of them, and the number of unread developer notifications they have received. It also allows you to remove yourself from apps that you have been invited to by other developers, remove your own apps, archive your own apps, and begin the Data Use Checkup process, if required.

You can access the Apps panel at developers.facebook.com/apps or by clicking the My Apps link in the header that appears on all developers.facebook.com sub-pages:

Toolbar

The toolbar displays basic app attributes and allows you to switch among your apps.

App Selection Dropdown

Allows you to switch among your apps, create new apps, and create test apps.

App ID

App IDs are generated upon app creation. They are unique to each app and cannot be changed. App IDs are typically not needed unless you are programmatically adjusting your app's settings, or querying endpoints that require your app ID (there are only a handful of these).

App Mode Toggle

This toggle displays your app's current app mode status and allows you to switch between modes.

All newly created apps start out in Development mode and should not be switched to Live mode until you have completed app development and are ready to release your app.

If you chose Business as your app type, you will not see a mode indicator because Business apps rely on access levels instead of modes.

App Type Indicator

This displays your app type. App types determine which products, permissions, and features are available to your app. If you chose Something Else when you created your app, you will not see this indicator.

Dashboard

The Dashboard panel is where you can find API usage meters as well as important notifications about required actions or upcoming changes that may impact your app.

Information Card

Occasionally we will release new products or announce upcoming changes that may affect your app and display them here (you'll also receive a corresponding developer notification, unless you have disabled notifications).

Required Actions

Important messages about your app will be displayed here. These typically have to do with actions related to maintaining data access. You'll also receive a developer notification about these requirements.

Application Rate Limit

Displays your app's Graph API application rate usage. Learn more about Application rate limits.

User Rate Limit

Displays the number of your app users who have reached their Graph API user rate limit. Learn more about User rate limits.

API Stats

Displays basic statistics about your app's Graph API requests.

Marketing API Stats

Displays basic statistics about your app's Marketing API requests.

Page Rate Limit

Displays your app's Graph API Page rate usage. Learn more about Page rate limits.

Facebook Login Activity

Displays basic statistics about your app's Facebook Login activity.

Products

See Products.

Settings

The Settings panel is split into two separate panels: Basic and Advanced.

The Basic panel allows you to provide more granular information about your app, such as its category, platform, and icon. It also contains settings commonly needed to complete App Review, such as URLs to your privacy policy and terms of service.

Learn more about Basic settings.

The Advanced panel allows you to configure uncommon settings, such as security settings, age- and geo-targeting restrictions, and allows you to upgrade your app to newer versions of the the Graph API and Marketing API.

Learn more about Advanced settings.

Roles

The Roles panel can be used to send app role invitations to other people who may be helping you develop your app. This panel can also be used by Administrators to remove a person from a role.

App roles control who has access to your app's settings, and who can use your app (grant it permission to access their data) while it's in Development mode.

Learn more about app roles.

Alerts

The Alerts panel is where you can access developer notifications that we may have sent you, such as App Review submission status updates and alerts about upcoming API changes.

You can control which developer notifications you want to receive by using the Developer Settings panel.

App Review

The App Review panel allows you to create and submit App Review submissions.

App Review is part of the release process — if your app will be used by people who do not have a role on your app, you will have to submit your app for review.

Learn more about the App Review process.

Products

Depending on what functionality your app needs, you may need to add a product to your app. Products span a wide range — they can be standalone software, SDKs, frameworks, plugins, or simply collections of APIs.

Adding a product to your app enables relevant functionality and API access. It also adds a new product-specific panel to the dashboard, and in most cases, provides an interface for you to configure additional product-specific settings. For example, Facebook Login allows you to control oAuth settings and requires you to add a redirection URL. You can supply this information using the Facebook Login panel after you add the Facebook Login product to your app.

The developer documentation for the products listed on developers.facebook.com/products will indicate whether or not you need to add a corresponding product to your app using the App Dashboard.

Product Use Certification

Some products require you to certify that you will use them in compliance with our Plaftorm Terms and Developer Polices.

You can complete initial certification by checking the checkbox in the Confirm Acceptance modal when adding these products to your app. You will also be required to annually recertify as part of the Data Use Checkup process.

Activity Log

The Activity Log is a historical record of changes made to your app through the App Dashboard. This panel will not appear until there has been activity on your app.

Build and Test - Meta App Development - Documentation

This document outlines the basic development and testing process for newly created Facebook apps. It also describes tools and settings available in the App Dashboard that may help you during development.

General Process

The development process will vary depending on your app's needs, but the basic flow begins with reading the documentation for each of the products, SDKs, and APIs that your app will rely on. All of our products are showcased on developers.facebook.com/products, and all of our documentation can be found at developers.facebook.com/docs.

Once you have identified and read any relevant doc sets, the next step is to make changes to your app's codebase and configure any App Dashboard settings that may be required by the products, SDKs, and API calls that you are implementing. If other people will be helping you develop and test your app, you can assign them app roles so they can configure app settings and help test Graph API permissions and features.

Finally, to verify that you have implemented everything correctly, you can test your app using your own Facebook developer account or with test users that simulate real Facebook users.

As a starting point, most Facebook apps use the Graph API to get data in and out of Facebook. Graph API endpoints require permissions, which apps can request from app users by implementing Facebook Login. Since getting data in and out of the Graph API is a common action, we have a set of SDKs to make calling Graph API endpoints easier. So, many developers start with those four doc sets.

App Types

App types determine the products that can be added to an app in the App Dashboard and which permissions and features can be requested for approval through the App Review process.

Learn more about app types.

App Modes

App modes apply to non-business apps and determine which permissions and features your app can use, and who can use your app.

Apps in Development mode can be granted any permission, but only from app users who have a role on the app itself. In addition, all features are active, but only for app users who have a role on the app.

Apps in Live Mode can be granted permissions by anyone, but only permissions that have been approved through the App Review process. Similarly, features are active for all app users, but only features approved through App Review.

All newly created non-business apps start out in Development mode and you should avoid changing it until you have completed all development and testing.

Note that app types also affect which permissions are available to an app. For example, user-related permissions are not available to Business apps, and business-related permissions are not available to Consumer apps. Apps that have chosen the Business app type do not have app modes at all and instead rely on access levels, which behave similarly.

Learn more about app modes.

App Roles

Apps in Development mode can only be used by people who have been granted a specific role on the app itself. If you are working with a team of developers and testers you can assign roles to each person so they can aid with the development and testing process.

Learn more about app roles.

Test Users

Test Users are test accounts that you can sign into in order to simulate real Facebook users when testing your app. Test users cannot interact with real Facebook users and any content or interactions generated by test users are only visible to other test users and anyone who has a role on your app.

Learn more about test users.

Test Pages

Test pages are pages created by test users that you can use to simulate real Facebook Pages when testing your app. Test pages are not discoverable by real Facebook users and can only be interacted with by other test users, or by people who have a role on your app.

Learn more about Test Pages.

Data Deletion Callback

If you have implemented Facebook Login, or if your app is typed as either a Consumer or Instant Game app, you must implement a Data Deletion Callback before it can be switched to Live mode. We will call your app's data deletion callback URL anytime one of your app users requests that you delete their data.

Learn more about the Data Deletion Callback.

Next Steps

Once you have completed app development and are ready to switch your app to Live mode, you can begin any processes that may be required to successfully release your app.

Configuring the application for integration with Facebook (up to and including version 10.0)

Integration of your accounts in Webim and Facebook is registered as an application of the network Facebook . This article explains how to create and configure such an application.

Important!

In accordance with the decision of the Tverskoy Court of Moscow dated March 21, 2022 to ban Meta products, we do not provide these services. Specify the details in our chat or write to the mail.

Check that your page meets all the necessary requirements

Log in to Facebook using the link, enter the login and password of the exact account (account) Facebook on behalf of which the page was created (or will be created) and the integration will be registered. It is recommended to use the account that owns the page. If she has a different role on the desired page, Facebook will not provide access to her for integration.

N.B.

Access for integration is granted only to page administrators. Also keep in mind that losing access to this account will render the integration unmanageable. Therefore, it may be useful to create a separate account for these purposes.
If Page of your project has not yet been created, create it now.
Make sure your project has Privacy Policy and preferably End User Agreement/Terms , located on separate web pages. Otherwise, write them now.
Make sure that your project has a logo or other unique image that characterizes it, and that you have intellectual rights to it and the logo bitmap file. Otherwise, take care of the logo now (logo size is 1024 x 1024 pixels).
Make sure that the account Facebook is provided with reliable data that you can confirm in case of verification (name, surname, date of birth, e-mail address, phone number, photo, etc.), and also have a passport or other document ready (for example , driver's license) confirming the identity of this account. Otherwise, supplement or correct these data. In the future, Facebook may ask you for additional information.

Facebook registration for Developers

Go to the main page of the Facebook for Developers service using this link. The developer page will open. The same account Facebook is used here as usual, but for those who start working with the service for the first time, it is required to additionally register their account. Click here Get started .

Facebook for Developers, main page
This will open the welcome window. Click here Continue :

Welcome window Facebook for developers
At this stage Facebook performs the first check. If you did not provide your phone number when registering or editing your account, an additional form may appear asking you to provide your phone number and confirm it. If the additional form does not appear, proceed to the next step of this instruction.

Create application

After the welcome window, a page appears with a button Create app . Click it.

Page with Create Application button
In the application type selection window, select Business .

Selecting the type of Webim
application
Then you need to specify Display name of the application (Display name) and App Contact Email . If necessary, please verify that you are not a robot (captcha).

Creating a Webim
application

Application preset

Next, the product setup page will open, displaying several sections for configuring the product. In the Messenger section, click the Set Up button.

Setting up the Webim 9 application0009
You will be taken to the Messenger settings for the app. Under Access Tokens click Add or remove pages . Select the page where you want to set up the integration (your company page) and click Next and then Done .

Adding page
In section Access tokens the page you added and button 9 will appear0003 Generate Token , clicking on which will open a confirmation window for generating a token. In this window, you will see a warning that, for security reasons, the generated access token will only be shown once. Immediately copy the marker and paste it into a previously opened blank text document to eliminate the possibility of loss.

Generated access token

Application setup on this can be considered complete. Information about integration with Facebook can be found in this article.

The activities of the Meta corporation, as well as its Facebook and Instagram platforms, are recognized as extremist and banned in the Russian Federation. ↩

Setting up a Facebook channel | Microsoft Learn

Article
03/16/2023
Reading takes 10 minutes

Omnichannel for Customer Service offers a set of capabilities that enhance Dynamics 365 Customer Service Enterprise by enabling organizations to instantly connect and interact with their customers over digital messaging channels. Access to Omnichannel for Customer Service requires an additional license. For more information, see the Dynamics 365 Customer Service Pricing Overview and Dynamics 365 Customer Service Pricing Plan pages.

Many customers use social media messaging channels such as LINE for their personal needs. Many also choose to use these messaging channels to interact with the business. The asynchronous nature of these channels gives customers the convenience of resolving their issues as they find time, unlike real-time channels such as chat for Dynamics 365 Customer Service, where the session ends when the chat window is closed.

note

If you use Facebook access tokens, please renew them on a 60-day schedule or as needed, as tokens can expire randomly. More information: Facebook Access Tokens

Prerequisites

The following prerequisites must be met before setting up a Facebook channel in Omnichannel for Customer Service.

Create a Facebook page and enable Messenger. More information: Creating and managing a page and messaging
Create a Facebook application. More information: Application development
Add Messenger and Webhooks to the Facebook application. More information: Setting up your Facebook app
If you will be using the test environment, set up test Facebook accounts so that agents can send and receive messages in Omnichannel for Customer Service.
Values for Application ID and Application Secret from fields App ID and App Secret in Facebook app > Settings > Basic .

Roles and Permissions

The following Facebook roles and permissions are required to integrate your Facebook app with Omnichannel for Customer Service.

Facebook users who do not have a role in the Facebook app must have permission pages_messaging to send messages to a Facebook page from Omnichannel for Customer Service. App owner must grant permission pages_messaging users so that they can send messages. More information: pages_messaging
If the Facebook app you're using is currently in development mode, then only Facebook users who have roles in the app can post to the Facebook page; messages can be received or routed to Omnichannel for Customer Service. More information: Application roles
In order for Omnichannel for Customer Service to get the customer's username from Facebook, the customer must request access to the business resource's user profile in their Facebook app. More information: Business resource user profile access

Setting up a Facebook channel

To set up a Facebook channel, follow these steps:

Create a Facebook channel account.
Set up Facebook workflow and work sharing settings

Create a Facebook channel account

In Dynamics 365, go to one of the apps and follow these steps.
- Customer service admin center
- Omnichannel admin center
1. In the site map, in item Customer Service , select Channels .
2. Under Accounts , for Messaging accounts , select Manage .
On the Accounts and Channels page, select Create an account .
Enter the following details:
1. On the page Channel Details enter a name and select Facebook in Channels .
2. On page Add Account , in the Application ID and Application Secret fields, enter the Application ID and Facebook Application Secret that you copied from the Facebook application.
3. To Add Facebook pages to this account follow these steps:
4. Select Add and in area Add Facebook Page enter the following data:
  - Page name: Facebook page name.
  - Page ID : ID for the Facebook page. To get the page ID, go to your Facebook page, select Details, and copy the value into the Page ID field.
  - Page access token: Specify the page access token in the Facebook app. To get a page access token, go to the Facebook app, then select Messenger > Settings . In the Access tokens section, select the page and copy the value into the Access token field of the page.
5. On page Callback Details , fields Callback URL and Verification Token are automatically populated when settings are saved. Use the information to set up webhooks in the Facebook app. Field values will not be generated if the Facebook page is reused across multiple channel instances.

Create a Facebook workflow

Follow the steps in Create a workflow to set up work routing and distribution.
Select the workflow you created for the Facebook channel and on the workflow page select Facebook setup and do the following:
1. In the Available Facebook Pages area, select a page from the list.
2. On page Language , select the desired language.
3. On page Behavior , set the following parameters:
  - Custom automatic messages
  - Poll after conversation
4. On page User functions , set the following parameters:
  - File Attachments: If set to Yes for both client and agent, clients and agents can send and receive file attachments. More info: Include attachments. The availability and support of media files depends on the Facebook app settings. More information: Facebook Updates
  - Facebook message tag : Set Yes to so that your agents can send messages to customers after 24 hours. When set to No , agents will not be able to respond to clients after 24 hours unless the client sends another message.
  If you enable the human agent's Facebook message tag during an active conversation between an agent and a customer, the agent must close the conversation and reopen it to communicate with customers after 24 hours of inactivity. Agents can start conversations with clients for up to seven days.
  
  To use the Facebook human agent message tag, you must also enable it in the Facebook app. For more information, see Facebook Developer Tools.
5. Check page Summary and select Create . The channel instance is configured.
Set up routing rules. More information: Set up job classification
Set up work distribution. More information: Work distribution options
Optionally, you can add a bot; Skip this step if you only have human agents in your conversations. More information: Bot configuration
In Advanced Options , configure the following options according to your business needs:
- Sessions
- Agent notifications
- Context variables
- Intelligent help bots
- Quick answers

Client interface

The client can start a conversation in any of the following ways:

Messenger on the Facebook page
www.messenger.com
Messenger app on a mobile device
Messenger Widget on Custom Website

If a customer starts a conversation from a Facebook page and then switches to a mobile device, the previous conversation is saved and the customer can continue the conversation.

The agent is notified of an incoming call request. More information: Using the Facebook channel

After the agent associates a Facebook social network profile with a customer or contact record, subsequent Facebook conversations are associated with the customer records and the customer summary is populated.

If the customer is not identified by name, you can create a new contact record.

The client can only send attachments if you enable them. If this setting is not enabled for clients, they can still try to upload the file. However, agents will not receive the file and will see an error.

Privacy notice

When you enable this feature, your data will be shared with Facebook and outside of your organization (both physically and in terms of compliance) (even if your organization is in a community region) for government organizations). For more information, see the technical documentation for the components here.

Customers are solely responsible for their use of Dynamics 365, this feature, and any related features or services, in compliance with all applicable laws, such as those relating to monitoring, recording, and storing end user interactions. This includes properly notifying end users that their communications with agents may be monitored, recorded or stored and, as required by applicable law, obtaining consent from end users before using this feature on them. Clients are also encouraged to have a mechanism in place to inform their agents that their communications with end users may be monitored, recorded or stored.

Set up a Facebook channel in Omnichannel Administration

Warning

Omnichannel Administration ended support on April 30, 2022. We recommend using the Customer Service Admin Center app to set up the latest features such as Unified Routing and Voice Channel. More information: The Omnichannel Administration app is deprecated

After you complete the prerequisites, you can add a Facebook channel for your organization by following these steps:

Creating a Facebook workflow
Creating a Facebook channel
Creating routing rules
Changing settings for a specific Facebook page

Create a Facebook workflow

Sign in to Omnichannel Administration.
Select Work Distribution Management > Workflows .
Select Create to create a Facebook workflow.
On the tab Work distribution , in the Channel field, select Facebook .
Provide other required information. For more information, see About workflows and how to create them.
Press button Save .

Create a Facebook channel

Select Channels > Facebook .
Select Create to create a Facebook feed.
On page Create a Facebook App , provide the following details:
- Name : The name of the Facebook application.
- Application ID : Facebook Application ID. To get the app ID, go to the Facebook app, select Settings > Base and copy the value in the field Application ID .
- Application secret : Application secret for the Facebook application. To get the app secret, go to the Facebook app, select Settings > Basic and copy the value into the App Secret field.
Select Save . Section 9 is enabled after the record is saved.0003 Facebook pages , and this allows you to add Facebook pages through which the client can connect to the agent.

Note

In this release, you can only create one Facebook app per organization. However, you can add multiple pages to the Facebook app.
Under Facebook Pages , select Add New Facebook Page to add a Facebook page.
On page Create Facebook page tab Account setup contains the following information:
- Page ID : ID for the Facebook page. To get the Page ID, go to the Facebook Page, select Details , and copy the value into the Page ID field.
- Page name : Facebook page name.
- Page 9 Access Token0004 : Page access token from the Facebook app. To get a page access token, go to the Facebook app, then select Messenger > Settings . In the Access tokens section, select the page and copy the value into the Access token field of the page.

Select Save to create the entry.

After adding the Facebook page, the values for fields Callback URI and Validation token are automatically generated. These values are used to set up webhook elements in the Facebook app.

Note

You can add several Facebook page ID (pages) to channel Facebook application . However, Facebook Page ID can only be associated with one Facebook Application . If you associate the same Facebook Page ID with multiple channels Facebook App , then the callback URI parameters and Validation token will not be generated automatically.

Creating routing rules

Select Work distribution management > Workflows .
Open the workflow created in step 1.
On the Routing Rule Elements tab , create a routing rule to route the message to the appropriate agent. Select entity as Facebook interaction context .

For example, you could create a rule to pass a Facebook chat from a client named Lesa to the default queue.

When you create conditions for routing rules, the Facebook Interaction Context (Conversation) entity allows you to set the following attributes:

Customer Name : The customer name is displayed in the "first name, last name" format.
Locale : See the Facebook developer documentation for a list of locales.
Time zone : The time zone is displayed as a number relative to GMT, such as "5.5".
User Page Scope ID : This is displayed as a numeric string.

Change settings for a specific Facebook page

In the Omnichannel Administration app, go to your Facebook app and select the Facebook page you want to change.
On tab General settings , you must enter the following information:
- Language : Select your preferred language for your Facebook page.
- Workflow : Select an existing workflow or create a new one.
- Allow clients to attach files : Set to Yes to allow clients to send file attachments to agents. Otherwise, set the value to No .
- Allow agents to attach files : Set to Yes to allow agents to send file attachments to clients. Otherwise, set the value to No .
Note
- For more information about attachments, see Enable file attachments.
- To learn about uploading media to Facebook, see the Facebook developer documentation. The availability and support of media files depends on the Facebook app settings. More information: Facebook Updates
- Enable your Facebook human agent message tag : Set to Yes to allow your agents to send messages to customers after 24 hours.
  Learn more