Meta Business Extension
Facebook Business Extension (FBE): What It Is and Why It Triggers a Separate App Review
You finished building the "Connect with Facebook" button on your SaaS platform. Your standard Graph API App Review is approved. But your merchants still cannot connect — Meta's reviewer says your app is not available to public users. This is the FBE Integration Review wall. It is separate from standard App Review, has its own process, its own requirements, and its own reasons for rejection. Most SaaS platforms do not know this gate exists until they hit it.
What Facebook Business Extension Actually Is
Meta Business Extension (MBE / FBE) is a popup-based onboarding framework that lets businesses connect their Facebook and Instagram presence to your platform in one flow — creating or linking their Business Manager, Pages, Meta Pixel, Ad Account, and Catalog in a single session. It replaces having to integrate separately with the Business Manager API, the Pages API, and the Marketing API.
If your platform lets client businesses connect their Meta accounts to use features like ad management, catalog sync, pixel firing, Messenger chat, or Instagram Shopping — you are building an FBE integration, and you need Integration Review before any public merchant can use it. When Pixel and Conversions API are part of the integration, server-side tracking has its own setup, and our Facebook Conversions API setup guide covers datasets, tokens, and when App Review applies.
Who uses FBE
E-commerce platforms, booking apps, restaurant ordering tools, ad management dashboards, marketing automation SaaS — any platform that lets businesses connect their own Meta assets.
What FBE provides
A single popup flow that handles Business Manager selection, Page linking, Pixel creation, Catalog setup, and Ad Account connection — plus webhooks delivering access tokens per merchant installation.
Who is locked out
Until Integration Review is approved and you launch, only your app's admin and developer roles can use the FBE flow. No public merchant can onboard.
Key difference
Standard App Review approves individual permissions for your app. FBE Integration Review approves your entire onboarding flow and verifies the integration end-to-end before any merchant can use it.
What You Need Before You Even Start Building
FBE is not open to all developers. Three requirements must be in place before any implementation work begins:
Allowlist required first. You must contact your Meta representative and have your app added to the FBE allow list before you can start implementation. Skipping this step means you will encounter errors no matter how complete your code is.
Business App type only. Your Meta app must be created with the Business app type. Consumer app types are not eligible for FBE. If you built a Consumer app, you need to create a new app of the correct type.
Meta Business Verification required. Your Business Manager must be a verified business. Unverified Business Managers cannot own a Business-type app eligible for FBE. This verification step alone often takes 2–4 weeks and causes multiple document submission attempts.
The Permissions That Still Require Standard App Review
FBE Integration Review does not replace the standard Meta App Review process for individual permissions. Depending on which FBE features your integration uses, certain permissions still need to be approved through standard App Review before Integration Review can be completed:
catalog_management
Required for Catalog sync. Needs standard App Review with a screencast showing the permission being requested, inventory being pushed, and Catalog-powered features working after sync.
ads_management
Required for Ad Account connections and ad creation features. Needs Advanced Access via App Review for serving client ad accounts beyond your own Business Manager.
business_creative_management
Required for creative integrations. May require App Review depending on the scope of access your integration requests.
manage_business_extension
Private permission for the FBE framework itself. Granted by your Meta representative as part of the allowlist process — not submitted through standard App Review.
This means many FBE integrations require completing standard App Review for individual permissions before submitting for Integration Review — two separate processes, both needed. See our guide on Meta Advanced Access and App Review for how the permission tiers work.
How the FBE Integration Review Process Works
Once implementation is complete, Integration Review is submitted through the FBE Developer Panel inside your Meta app dashboard — not through the standard App Review interface. The process is high-level; the exact implementation steps are your responsibility as a developer. Here is what the review gate involves:
1
Complete the checklist in the Developer Panel's Overview tab — all integration requirements must be implemented and confirmed
2
Go to the Integration Review tab and fill in your platform details — login credentials for Meta's reviewer, your Authentication URL, and your Webhooks Callback URL (both must be production-ready, not test URLs)
3
Provide a screencast video showing the complete end-to-end onboarding flow — Business Login popup, asset selection, uninstall, and Management View — plus a demo merchant screencast showing the Meta Pixel firing correctly
4
Meta's reviewer logs in using your provided credentials and tests the flow — ensure those credentials are not used in your own testing during the review period to avoid conflicts
5
If approved: use the Launch Status tab to make the integration available to public merchant users. If rejected: address the feedback and resubmit — rejections reset the review timeline
Only app administrators and developers with a role on the app can use the FBE flow while review is pending. Meta makes all Integration Review decisions independently. No outcome can be guaranteed.
Common Reasons FBE Integration Review Gets Rejected
Test or staging URLs submitted for Authentication URL or Webhooks Callback — Meta requires production-ready endpoints
Screencast missing the full end-to-end onboarding flow — reviewer cannot verify the Business Login, asset selection, and uninstall flows
Missing demo merchant Pixel firing screencast — required when Pixel/Conversions API is part of the integration
Test credentials provided to reviewer are also used for developer testing — causes conflicts and authentication failures during review
Individual permissions (catalog_management, ads_management) not yet approved via standard App Review before Integration Review submission
Business Manager not verified — the verified business requirement is checked as part of the review process
App was built with Consumer app type instead of Business app type — requires a new app to be created