Este documento foi atualizado.
A tradução para Português (Brasil) não foi concluída ainda.
Atualização em inglês: 6 de dez de 2023
Atualização em Português (Brasil): 19 de abr de 2022

Migration Guide: MBE, v2 to MBE, v3

This is an Alpha product. Ensure you have a dedicated technical Meta representative prior to building.

This guide describes the changes required to migrate existing Business apps on Meta Business Extension (MBE, v2) to be compatible with MBE, v3. Going forward, MBE will require these updates and is not backwards-compatible with the next version of the Graph API.

Key Benefits of MBE, v3

With MBE v3, third-party app developers can:

  1. Offer businesses simpler onboarding flows.

  2. Help reduce churn.

  3. Allow businesses to flexibly manage the features they want to enable for each Business app. For example, an online seller can initially set up messaging features with a business app, and later choose to enable their Facebook Shop with the same app. This is a great way to upsell businesses on multiple FBE features.

  4. Accommodate multiple business types in their integration with FBE. For example, a third-party app can offer one type of integration to a subset of businesses that only require advertiser tools, and separately offer another type of integration for businesses that only require messaging tools.

Before You Begin

Ensure your Meta partner manager is aware you are making this upgrade so they can properly support you if you need help.

Overview

Terminology

Feature: A particular integration that can provide outcomes for your businesses. Each integration has unique implementation requirements, and you can set which features you want to enable. Examples can include page_cta, chat_plugin, and so on. For a complete list, see this Feature list.

Vertical: Represents the type of business. You can integrate with one or more vertical, depending on the type of businesses you serve. A single business can also be set up on one or more verticals, depending on their needs. For a complete list, see this Verticals List.

Intent: An Intent is the MBE name for a particular use case. For example, the CATALOG_ADS intent is the name for the use case that allows your app to run catalog ads, to sync and promote your catalog's products and services. Intents appear on the feature menu and map to a set of multiple features that the business gets.

Intents using v3 are similar to “channel” from v2. Configuring an intent in your login flow is not required, but doing so will prompt your merchants or advertisers to complete onboarding to the specified intent prior to seeing the rest of the available intents in the feature menu. Leaving the intent out of your login flow will show merchants or advertisers the feature menu of all available intents for your vertical, and allows them to select their own intents at the start of MBE.

For a complete list, see this Intents list by Vertical.

Key Differences between v2 and v3

MBE, v3 introduces more granularity and controls over what features a business can enable during onboarding. As a result, we are upgrading our UI and changing our webhook and API responses to reflect this level of feature detail.

Based on the features you choose to enable and the vertical you pass in for the business, MBE displays a feature menu within the onboarding flow where the business can select the features they want to install. The business can then manage these features in Management view and add more by re-entering the flow on your surface or through the Management view surface.

This screen is displayed when the use_minimal_onboarding flag is set to true. Setting use_minimal_onboarding to false maintains the MBE v2 UI.

Recommendations

Because the set of features a business enables is dynamic and optional, we recommend that you build a framework for record-keeping. For each business:

  1. Keep a list of features that have been enabled and their associated assets.
  2. Synchronize with the Meta APIs to ensure this record of what features are enabled is updated and accurate.

Requirements

MBE, v3 allows a business user to:

  • Opt-in to the subset of your app’s features that are relevant to them

  • Add or remove features over time, independently of other features

As a result, the app integration needs to:

  1. Listen for updates. A webhook will be sent every time a business goes through the flow or updates business-enabled features.

  2. Once a webhook is received, check what features have been enabled by calling the FBE Installation API. Each time a business goes through the flow, they can enable or disable features.

  3. Within your platform, update the record of features that have been enabled for this business.

  4. Enable each feature based on the partner implementation details in the Feature List. For example, if you have enabled multiple features that require their own separate catalog, you must maintain the sync for each catalog. Pull from the Feature Configuration API if additional feature information is needed.

Your app should not assume that all assets your app supports will be returned. For example:

  • A business that sets up a Shop can also do so with just their Instagram account. Therefore, your app should not require businesses to set up a Page to enable this feature.

  • A business that sets up a Conversions feed to improve ad performance can do so without setting up a Page or Instagram call-to-action (CTA) button. Your app should not require a business to set up a Page or Instagram account to enable this feature.

Update Your Integration to v3

This section explains how to update your integration with the required changes for MBE, v3. As MBE, v3 is fundamentally different from MBE, v2, we recommend following these implementation guidelines to reduce potential interruptions for users.

Your users will not need to reauthenticate on MBE once your app has migrated - they will maintain their existing connections.

Step 1: Set Up Features and Respond to Updates

Step 2: Configure App-Supported Features

The features that display for your merchants in the feature menu are those that you configure within the MBE Developer Panel.

If you are a developer participating in the alpha launch of MBE, v3, contact your Meta representative and let them know which features you want to enable in your app. This information, along with the vertical you pass in for the business, defines the menu of features displayed in the MBE Developer Panel.

Step 3: Configure Verticals

When configuring verticals, be sure to send the appropriate vertical for each business in the extras configuration under business_vertical. For example, if it’s a hair salon, send ‘APPOINTMENTS’. If it’s a Shop that sells products, send ‘ECOMMERCE'.

If a business belongs to more than one vertical, send different verticals for each entrypoint on your surface (depending on what goal the business is trying to achieve). For example, if a hair salon offers both appointments and sells hair products, you can send ‘APPOINTMENTS’ from entrypoint 1 and ‘ECOMMERCE’ from entrypoint 2. Each entrypoint will need to have their own vertical-specific features configured to work properly.

A merchant or advertiser that goes through both verticals for onboarding will be “locked in” to the same Business Manager for each vertical, if the same external_id is used. Assets (Page, pixel, catalog) from the first vertical that a merchant onboarded with will be preselected in the second vertical, but a merchant will have the option to select different assets for their second vertical. All features installed by the merchant can be read on the Feature Configuration API.

Step 4: UI Changes

The updated onboarding flow (minimal onboarding) shows a ‘feature menu’ that displays a list of intents which are bundles of one or more features that you have enabled for your businesses. Businesses can select which intents they want to install. If you would like your business to install a particular intent first and then see the feature menu, pass in an intent param in the setup object. You can choose from the intents list for this parameter. If you want to perform an experiment around the UI update or don’t want this new updated UI, the parameter use_minimal_onboarding, in the flow_config object determines which UI to show. Use_minimal_onboarding set to false will maintain the MBE v2 UI.

Step 5: Management View

Management View with v3 surfaces all the features that the business has installed and links out to install even more features. The link to Management View has been updated to be:

<a href=”https://business.facebook.com/latest/business_app_store/manage_external_business_connection?asset_id=<page_id>&business_id=<business_id>&app_id=<app_id>&external_business_id=<external_business_id>"><button>Launch Management View</button></a>

Step 6: Enable Feature Changes

To enable these feature changes, the following APIs have been updated:

MBE, v2MBE, v3 Feature Changes

Webhook

Sent for every install and uninstall, details all features that have been installed (including from past installs). See also Updates to the Webhook.

FBE Installation API

Returns asset-level information, including top-level install and assets associated with each feature. See also Updates to the FBE Installation API.

Business/Feature Configuration API

Includes the feature instance ID for each feature. For some features, information (such as the CTA URL) is included and can be updated via the API. For other features, only the enabled flag is returned. You can modify both sets of these features by relaunching the onboarding flow or through the Management view. See also Updates to the Feature Configuation API.


Updates to the Webhook


A webhook is sent for every install and uninstall and only consists of the features the business has installed.

For uninstalls, a webhook is also sent with a response consisting only of installed features (for example, not including the uninstalled features). Each time a webhook is sent, pull from the FBE Installation API for the source of truth.

Response

{
  "data": [{
    "ad_account_id": "<ad_account_id>",
    "business_manager_id": "<business_manager_id>",
    "catalog_id": "<catalog_id>",
    "commerce_merchant_settings_id": "<commerce_merchant_settings_id>",
    "onsite_eligible": true,
    "profiles": [
      "<page_id>",
      "<instagram_profile_id>"
    ],
    "pages": [
      "<page_id>"
    ],
    instagram_profiles": [
"<instagram_profile_id>"
    ],
    "pixel_id": "<pixel_id>",
    "token_type": "<token_type>",
    "installed_features": [
        {
            "feature_instance_id": "<unique_id>",
            “feature_name” : string, 
            "feature_type": enum,
            "connected_assets": {
                “ad_account_id”: "<ad_account_id>",
                “business_manager_id”: "<business_manager_id>",
                “catalog_id”: "<catalog_id>",
                “commerce_merchant_settings_id”: "<commerce_merchant_settings_id>",
                “ig_profile_id”: "<instagram_profile_id>"               
                "page_id": "<page_id>",
                "pixel_id": "<pixel_id>",
            },
            “additional_info”: {
               “onsite_commerce_eligible”: bool
            }
        }
    
  }]
}

Response Fields

FieldDescription
ad_account_id

Type: string

Ad account ID selected by the user within FBE. You can use this ad account to manage ads if your app has ads_management permissions. See the connected assets of the installed_features list.

business_manager_id

Type: string

Business Manager ID used for FBE. See the connected assets of the installed_features list.

catalog_id

Type: string

Catalog ID selected by a user with FBE. A user can use this ID to manage their product catalog. See the connected assets of the installed_features list.

fbe_event

Type: string

FBE Event that indicates whether the event notification is an install or uninstall. See the connected assets of the installed_features list.

flow

Type: string

Indicates which intent a user onboarded with (for example COMMERCE, CREATIVE, and so on). See the connected assets of the installed_features list.

commerce_merchant_settings_id

Type: string

Commerce Merchant Settings ID used to enable partners to read information regarding the selected FBE Commerce Merchant Settings. See the connected assets of the installed_features list.

onsite_eligible

Type: boolean

Commerce onsite eligibility. Indicates whether the selected assets are eligible for onsite commerce. The merchant must still have intent for onsite and select returns/shipping/payments on the partner site. See the connected assets of the installed_features list.

profiles

Type: array

List of profiles (a Facebook Page ID and/or an Instagram Business Profile ID). Use these IDs to create separate Graph API requests for other Facebook integrations you may have. See the connected assets of the installed_features list).

pages

Type: array

List of Facebook Page IDs. Use these IDs to create separate Graph API requests for other Facebook Page integrations you may have. See the connected assets of the installed_features list.

instagram_profiles

Type: array

List of Instagram Business profile IDs. Use these IDs to create separate Graph API requests for other Facebook/Instagram integrations you may have. If the field is not included, this means it's only Instagram-related scope. For example, instagram_basic is not included in the access token and/or the business has not connected any Instagram Business profile with FBE. See the connected assets of the installed_features list.

pixel_id

Type: string

Unique pixel ID for this business that you should store and use to fire pixel events. See the connected assets of the installed_features list.

token_type

Type: string

Token type. Indicates whether the access_token received is a default User access token or a System user access token.

installed_features

Type: array

List of features this business has integrated with/installed through the onboarding flows. See the current feature list.

feature_instance_id

Type: array

ID that uniquely represents each installed feature. Can be used in the future to modify or uninstall a particular instance. It is the same as the feature_instance_id referenced in the Feature Configuration API and Webhook.

feature_type

Type: string

Type of the feature installed. The feature list table has the entire set of features available. You only need to track the features you have enabled.

connected_assets

Type: array

List of assets that are specific and relevant to each feature. Asset descriptions correspond to the ones mentioned at the top of this table.

additional_info

Type: array

Additional information about the connected feature.


Updates to the FBE Installation API


The updated API model sends the list of each feature the business has enabled and the connected assets for each feature. The main change is the addition of the installed_features field. This payload is the same as the Webhook response.

After receiving the webhook, follow these recommended steps:

  1. Call the FBE Installation API with the received external business ID and access token. This API contains the source of truth for installed features and their connected assets. Keep a proper record of these feature configurations.

  2. Enable these features for that business (specifics on what “enabling” means are in the feature list table), and pull any additional needed information about the features from the Feature Configuration API.

The following code sample shows an example request to the FBE Installation API and the corresponding API response. Within the response, the additional v3 fields are highlighted.

Request

CURL -X GET 
'https://graph.facebook.com/<API_VERSION>/fbe_business/fbe_installs?fbe_external_business_id=<fbe_external_business_id>&access_token=<access_token>'

Response

{
  "data": [{
    "ad_account_id": "<ad_account_id>",
    "business_manager_id": "<business_manager_id>",
    "catalog_id": "<catalog_id>",
    "commerce_merchant_settings_id": "<commerce_merchant_settings_id>",
    "onsite_eligible": true,
    "profiles": [
      "<page_id>",
      "<instagram_profile_id>"
    ],
    "pages": [
      "<page_id>"
    ],
    "instagram_profiles": [
      "<instagram_profile_id>"
    ],
    "pixel_id": "<pixel_id>",
    "token_type": "<token_type>",
<!--UPDATES BELOW-->
    "installed_features": [
        {
            "feature_instance_id": "<unique_id>",
            “feature_name” : string, 
            "feature_type": enum,
            "connected_assets": {
                “ad_account_id”: "<ad_account_id>",
                “business_manager_id”: "<business_manager_id>",
                “catalog_id”: "<catalog_id>",
                “commerce_merchant_settings_id”: "<commerce_merchant_settings_id>",
                “ig_profile_id”: "<instagram_profile_id>"               
                "page_id": "<page_id>",
                "pixel_id": "<pixel_id>",
            },
            “additional_info”: {
               “onsite_commerce_eligible”: bool
            }
        }
    ]
  }]
}

Updates to the Feature Configuration API Response


The updated model includes the feature instance ID for each feature and new fields that consist of an array of all features of that type installed by that business (example: multiple page CTAs).

For the non-customizable features described in the feature list, only a feature instance ID and an enabled flag displays. You can update only the customizable features with a POST request.

This model is different from the FBE Installation API because it provides additional feature information beyond the connected assets, including enabled status and specific feature customizations. After calling the FBE Installation API, use this API if more information is needed about the feature’s enabled status or configurations.

Read

You can read the current feature configuration status of any business with the following request:

CURL -X GET 
'https://graph.facebook.com/<API_VERSION>/fbe_business/?fbe_external_business_id=<fbe_external_business_id>&access_token=<access_token>'

Update

To update all features, use the following POST request:

CURL -i -X POST \   
  -F 'fbe_external_business_id=<fbe_external_business_id>' \
  -F 'business_config={business_config object}' \
  -F 'access_token=<access_token>' 
  "https://graph.facebook.com/<API_VERSION>/fbe_business"

Response

{
  "page_cta": {
     "feature_instance_id": id1,
     "enabled": true,
     "cta_button_text": "Book Now",
     "cta_button_url": "https://partner-site.com/foo-business1",
     "below_button_text": "Powered by FBE Partner"
  },
  "page_ctas": [
    {
        "feature_instance_id": id1,
        "enabled": true,
        "cta_button_text": "Book Now",
        "cta_button_url": "https://partner-site.com/foo-business1",
        "below_button_text": "Powered by FBE Partner"
    },
    {
        "feature_instance_id": id2,
        "enabled": true,
        "cta_button_text": "Book Now",
        "cta_button_url": "https://partner-site.com/foo-business2",
        "below_button_text": "Powered by FBE Partner"
    }
  ],
  “ig_cta”: {...}
  "ig_ctas": [{...}, {...}],
  “ads”: [
    {
      "feature_instance_id": id3,
      “enabled”: true,
    },
    {
      "feature_instance_id": id4,
      “enabled”: true,
    },
  ],
  ...
}

Testing

Prior to testing, send your Meta representative:

  1. Features you want to enable.

  2. User IDs of the individuals who will test the flow.

  3. Your test app id so that we can allowlist that app for v3.

  4. Give your Meta representative a role on your test app if you need help with testing.

To test these v3 changes, go through the onboarding flow and ensure:

  1. You receive a webhook upon install and uninstall.

  2. Webhook, Installation API, and Feature Configuration API have the updates mentioned above (accurately shows installed and uninstalled features).

  3. The Feature menu reflects the features you want your businesses to install (by vertical).

You can test the onboarding flow by:

  1. Going through Business Login.

  2. Going through the Business Apps (if applicable)

Make sure to send the correct business configuration object for the features you want, and the UI you want to see in Business Login and Business Apps.

Feature List

MBE, v3 offers the following features that you can enable for your businesses. All of these features can be passed in via the FBE Installation API (during the installation flow), but as noted in the table, not all are configurable via the Feature Configuration API (after the merchant or advertiser has already installed MBE).

Feature Name and TypeDescriptionAdditional Implementation DetailsConfigure in FCA?

Facebook Page Call to Action

page_cta(s)

CTA button on the business's Facebook Page.

None

Yes

Instagram Call to Action

ig_cta(s)

CTA button on the business's Instagram Profile.

None

Yes

Messenger Call to Action

messenger_menu

CTA button in Messenger when a user is messaging the business.

None

Yes

Messenger Send Availability Thread Intent

thread_intent

Messenger suggestion for business admins to easily send their appointment availability to a user in chat.

None

Yes

Page Card

page_card

Enables card with the business's featured services on their Facebook Page.

Requires Catalog Implementation

Yes

Messenger Chat

messenger_chat

Enables Messenger integration directly onto your website. This feature allows your customers to interact with your business anytime with the same personalized, rich-media experience they get in Messenger.

If

messenger_chat

returns

enabled: true

from the Feature Configuration API:

Get the page_id via Webhook or the FBE installs endpoint guide.

Yes

Collaborative ads

collaborate_ads

Enables brand advertisers to safely collaborate with a retailer or a marketing partner and achieve advertising goals, such as target product for sales using retailer-provided content.

Collaborative Ads API

-

AR Commerce

ar_commerce

Allows users to upload AR assets to a brand's catalogs.

Alpha Launch - Contact your Meta representative for more information.

-

Creative

creative

Allows users to create creatives on partner platforms and share it back to the user's Business Manager.

Creative Onboarding

-

IG Creators as Sellers

ig_ceators_as_sellers

Onboards users to the program, allows them to link an offsite shop, imports items, and creates a Shop, supporting the ‘creators as sellers’ workflow.

Alpha Launch - Contact your Meta representative for more information.

-

Pixel

pixel

Snippet of JavaScript code that allows you to track visitor activity on a website. It works by loading a small library of functions that can be used whenever a site visitor takes an action (called an event) that you want to track (called a conversion).

Fire Pixel Events

-

CAPI

pixel

Creates a connection between an advertiser’s marketing data and the Facebook systems that optimize ad targeting, decrease cost per action and measure results. In the case of direct integrations, this entails establishing a connection between an advertiser’s server and Facebook.

Conversions API

-

Catalog

catalog

Object (or container) of information about products, enabling users to upload and sync their inventory.

Catalog Implementation

-

Ads

ads

Allows you to create Facebook ads and view ads insights.

None

-

Facebook Shop

fb_shop

Allows businesses to easily set up Facebook Shops. It can be used for both commerce offsite and onsite Shops.

Commerce Onboarding

-

Instagram Shop

ig_shopping

Allows businesses to easily set up Instagram Shops. It can be used for both commerce offsite and onsite Shops.

Commerce Onboarding

-

Custom Audience

custom_audience

Allows businesses to optimize their ad targeting by targeting custom segments, website visitors, mobile app visitors, or people similar to them.

Custom Audience Onboarding

-

Messaging

messaging

Allows businesses to easily set up and manage conversations with their customers at scale on Facebook and Instagram.

Messaging Onboarding

-

Lead Ads

lead_ads

Enables businesses to run Lead ads on Facebook.

Lead Ads API

-

Customer Data

customer_data

Use Facebook to help understand who your customers are and craft strategies to re-engage and acquire more customers.

Alpha Launch - Contact your Meta representative for more information.

-

Checkbox Plugin

checkbox_plugin

Allows you to display a checkbox on your website forms that allows users to opt-in to receive messages from your bot in Messenger.

Checkbox Plugin; send domain in the setup config.

-

Checkbox Plugin Marketing

checkbox_plugin_marketing

Allows you to display a checkbox on your website forms that allows users to opt-in to receive marketing messages from your bot in Messenger.

Checkbox Plugin; send domain in the setup config.

-

Sample Code for messenger_chat

<div class="fb-customerchat"
            page_id=PAGE_ID 
</div>

Verticals List

Identify which vertical(s) your app belongs to:

Use CaseVerticalSome Prominent Features

My app enables businesses to bring their ads in front of the right customers.

Ads Targeting

Custom Audience Targeting

My app makes it easy for businesses to book services.

Appointments

IG CTA, Page CTA, Messenger CTA, Catalog

My app helps businesses to create eye-catching content without the help of a professional graphic designer.

Creative

Creative integrations with Ads

My app helps commerce businesses to increase sales and streamline their online ordering process.

Ecommerce

Catalog, Messenger Chat

My app enables restaurants to streamline online orders.

Food and Drink

IG CTA, Page CTA, IG Stories Sticker, Messenger CTA

My app helps businesses to collect, track, and nurture leads.

Lead Ads

Lead Ads

My app enables businesses to improve marketing decisions with detailed ad insight.

Measurement and Optimization

CAPI

My app supports businesses in managing their customer communication at scale.

Messaging

Messenger chat plugin, Send availability

My app makes it easy for businesses to book reservations.

Reservations

IG CTA, Page CTA, Messenger CTA

My app makes it easy for businesses to understand who their customers are, as well as engage and acquire more customers.

Data Integration

Customer Data, CAPI/Pixel

My app makes it easy for businesses to create and manage custom audiences for use in Meta Ads.

Data Integration

Ads, Custom Audience

Intents (Use Cases) by Vertical

Ads

Intent (Use Case) Intent Name Description Features

I would like to run ads using this app.

ADS

Use marketing features to help engage followers, build your audience, and boost sales.

Ads, CAPI/Pixel

I would like to run catalog ads using this app.

CATALOG_ADS

Sync and promote your catalog products or services.

Ads, CAPI/Pixel, Catalog

I would like to understand the performance of my ads and optimize for conversions.

CONVERSIONS_API

Optimize ad targeting, decrease cost per action, and measure results.

Ads (optional), CAPI/Pixel

I would like to run ads using this app. (Collaborative Ads)

COLLABORATIVE_ADS

Use marketing features to help engage followers, build your audience, and boost sales.

Collaborative Ads

Creative

Intent (Use Case) Intent Name Description Features

I would like to let this app share pictures and videos with my media library to improve my posts on Facebook and Instagram.

CREATIVE

Build your audience by using creative features to engage followers.

Creative

I would like to use items in my catalog to create images or videos with this app.

CREATIVE_WITH_ASSETS

Promote your products or services by syncing your catalog.

Creative, Catalog

E-Commerce

Use Case (Intent) Intent Name Description Features

I would like to showcase my products on Facebook.

FB_SERVICES

Reach new customers by offering your products directly on Facebook.

FB Shop, Ads (optional), Catalog, Page CTA, Messenger Send Availability Thread Intent, Messenger CTA

I would like to showcase my products on Instagram.

IG_SERVICES

Help people find your shop by tagging your products in posts and stories on Instagram.

IG Shop, Ads (optional), Catalog, IG CTA

I would like to add Messenger Chat Plugin on my website so customers can message me directly.

MESSENGER_CHAT

Connect more actively and effectively with customers.

Messenger Chat

Send appointment updates over FB Messenger

CHECKBOX_PLUGIN

Add a checkbox to your website that customers can use to opt-in to receiving appointment updates from your business page

Checkbox Plugin

I would like to build a marketing contact list linked to order data that I can communicate with via FB Messenger

CHECKBOX_PLUGIN_MARKETING

Add a checkbox to your website that customers can use to opt-in to receiving marketing messages from your business page. Sync order data to make your marketing more effective.

Checkbox Plugin, Customer Data

I would like to understand the performance of my ads and optimize for conversions.

CONVERSIONS_API

Optimize ad targeting, decrease cost per action, and measure results.

Ads (optional), CAPI/Pixel

I would like to run ads using this app.

ADS

Use marketing features to help engage followers, build your audience, and boost sales.

Ads, CAPI/Pixel, Catalog (optional)

I would like to enable this app to upload media to my media library.

AR_COMMERCE

Use augmented reality features to help engage followers and build your audience.

AR Commerce, Catalog

I am a Creator and would like to sell products on Instagram.

IG_CREATORS_AS_SELLERS

Help people find your shop by tagging your products in posts and stories on Instagram.

IG Creators as Sellers

Appointment

Use Case (Intent) Intent Name Description Features

I would like to showcase my services on Facebook.

FB_SERVICES

Reach new customers by offering your services directly on Facebook.

Page CTA, Page Card, Catalog, Messenger CTA, Messenger Send Availability Thread Intent

I would like to showcase my services on Instagram.

IG_SERVICES

Reach new customers by offering your services directly on Instagram.

IG CTA, Catalog

I would like to add Messenger Chat Plugin on my website so customers can message me directly.

MESSENGER_CHAT

Connect more actively and effectively with customers.

Messenger Chat

Send appointment updates over FB Messenger

CHECKBOX_PLUGIN

Add a checkbox to your website that customers can use to opt-in to receiving appointment updates from your business page

Checkbox Plugin

I would like to build a marketing contact list linked to order data that I can communicate with via FB Messenger

CHECKBOX_PLUGIN_MARKETING

Add a checkbox to your website that customers can use to opt-in to receiving marketing messages from your business page. Sync order data to make your marketing more effective.

Checkbox Plugin, Customer Data

I would like to understand the performance of my ads and optimize for conversions.

CONVERSIONS_API

Optimize ad targeting, decrease cost per action, and measure results.

Ads (optional), CAPI/Pixel

I would like to run ads using this app.

ADS

Use marketing features to help engage followers, build your audience, and boost sales.

Ads, CAPI/Pixel, Catalog (optional)

Reservations

Use Case (Intent) Intent Name Description Features

I would like to showcase reservations on Facebook.

FB_SERVICES

Reach new customers by offering your reservations directly on Facebook.

Page CTA, Page Card, Catalog, Messenger CTA, Messenger Send Availability Thread Intent

I would like to showcase reservations on Instagram.

IG_SERVICES

Reach new customers by offering your reservations directly on Instagram.

IG CTA, Catalog

I would like to add Messenger Chat Plugin on my website so customers can message me directly.

MESSENGER_CHAT

Connect more actively and effectively with customers.

Messenger Chat

Send appointment updates over FB Messenger

CHECKBOX_PLUGIN

Add a checkbox to your website that customers can use to opt-in to receiving appointment updates from your business page

Checkbox Plugin

I would like to build a marketing contact list linked to order data that I can communicate with via FB Messenger

CHECKBOX_PLUGIN_MARKETING

Add a checkbox to your website that customers can use to opt-in to receiving marketing messages from your business page. Sync order data to make your marketing more effective.

Checkbox Plugin, Customer Data

I would like to understand the performance of my ads and optimize for conversions.

CONVERSIONS_API

Optimize ad targeting, decrease cost per action, and measure results.

Ads (optional), CAPI/Pixel

I would like to run ads using this app.

ADS

Use marketing features to help engage followers, build your audience, and boost sales.

Ads, CAPI/Pixel, Catalog (optional)

Food and Drink

Use Case (Intent) Intent Name Description Features

Send appointment updates over FB Messenger

CHECKBOX_PLUGIN

Add a checkbox to your website that customers can use to opt-in to receiving appointment updates from your business page

Checkbox Plugin

I would like to build a marketing contact list linked to order data that I can communicate with via FB Messenger

CHECKBOX_PLUGIN_MARKETING

Add a checkbox to your website that customers can use to opt-in to receiving marketing messages from your business page. Sync order data to make your marketing more effective.

Checkbox Plugin, Customer Data

I would like to understand the performance of my ads and optimize for conversions.

CONVERSIONS_API

Optimize ad targeting, decrease cost per action, and measure results.

Ads (optional), CAPI/Pixel

I would like to run ads using this app.

ADS

Use marketing features to help engage followers, build your audience, and boost sales.

Ads, CAPI/Pixel, Catalog

Lead Ads

Use Case (Intent) Intent Name Description Features

I would like this app to access the leads generated through lead ads.

LEAD_ADS

Run lead ads to grow your audience and find new customers for your business.

Lead Ads, Ads

Measurement and Optimization

Use Case (Intent) Intent Name Description Features

I would like to understand the performance of my ads and optimize for conversions.

CONVERSIONS_API

Optimize ad targeting, decrease cost per action, and measure results.

Ads (optional), CAPI/Pixel

Data Integration

Use Case (Intent) Intent Name Description Features

I would like Meta to help me understand who my customers are and craft strategies to re-engage and acquire more customers.

CUSTOMER_DATA

Engage your customers and connect with people that might like your business.

Customer Data, CAPI/Pixel

I would like to create and manage custom audiences for use in Meta Ads.

CUSTOM_AUDIENCE

Optimize your ad targeting by targeting custom segments, specific platform visitors, or people similar to them.

Ads, Custom Audience