Facebook (Meta) Messenger¶
Within our Cognigy.AI platform, you're able to connect your Cognigy resources to your Facebook (Meta) Messenger channel by using our Messenger Endpoint integration.
Generic Endpoint Settings¶
Find out about the generic endpoint settings available with this endpoint on the following pages:
- Endpoints Overview
- Data Protection & Analytics
- Transformer Functions
- NLU Connectors
- Session Management
- Handover Settings
- Real-Time Translation Settings
Inject & Notify Support
You can use the Inject & Notify feature with this type of Endpoint.
Specific Endpoint Settings¶
Facebook (Meta) Page Setup¶
This dropdown menu is where your Cognigy.AI is provided with the credentials to access your Facebook Messenger App.
Page Access Token¶
The page access token is provided by Facebook (Meta) as an authentication variable to allow communication with your page.
App ID¶
This value is a unique App ID used by Facebook (Meta) to identify you app.
App Secret¶
Your Facebook (Meta) app's Secret that is a randomly generated value from Facebook (Meta). The value of this field must be the SECRET associated with the Page access token and App ID entered the previous fields.
Help Center
For more information on how to configure the Page Access Token, App ID, App Secret, head over to our Help Center article here.
Facebook (Meta) Profiles¶
In your Facebook (Meta) Endpoint, you will notice a section called Facebook Profiles. Here you can enable or disable several settings regarding how to handle contact profiles for the Facebook (Meta) Endpoint.
Request Profile Data¶
The Request Profile Data
exposes a contact's Facebook Profile information, such as their name and profile picture, in your Flow. If enabled, you can access this profile information in ci.data.profile in your Flow. The table below shows some common information you will find in the ci.data.profile object.
Key | Description |
---|---|
Id | The Facebook user's PSID. Each Facebook user has a unique ID for each Facebook Page they talk to. |
first_name | The user's first name. |
last_name | The user's last name. |
profile_pic | A url linking to the profile picture of the user. |
locale | Information about the user's locale. |
timezone | The user's time zone. |
gender | The user's gender. |
Data exposed in ci.data.profile
Not every user on Facebook will have the same data exposed in the profile object. This depends solely on what data they have on their Facebook profile, and what their privacy settings are.
Update Contact Profiles¶
If this setting is enabled, then the information a Facebook user has on their profile will be copied over to their contact profile. This is very useful in order to easily fill the contact profile with useful data.
Merge Contact Profiles¶
Each user on Facebook has a unique ID, a PSID, for each Facebook page they talk to. This means that if you own two or more Facebook Pages, you will not be able to immediately identify users across these pages, since they will have a different ID for each page. However, if you enable this setting, we will fetch all of a user's PSIDs for your pages and merge these profiles into one profile. This means that you can easily identify a single user across all of your pages, and thus personalize the chat even more.
Requires a Business
In order to perform the API calls necessary to get all the PSIDs for the user, the same Business needs to own all the Facebook Pages. More information at: https://www.facebook.com/business
Messenger Settings¶
Here you can configure whether typing indicators should be used and how many milliseconds of delay there should be between each message.
Help Center
For more detailed information on how to set up a Facebook Messenger Endpoint, refer to our Help Center articles here.