Meta App Review

Meta App Review: How I Prepare a Submission That Gets Approved on the First Attempt

Meta App Review: How I Prepare a Submission That Gets Approved on the First Attempt

The checklist I follow before pressing submit: matching permissions to real features, recording a screencast reviewers can follow, and removing every reason for a reviewer to say no.

Why first-attempt Meta App Review approval matters

Every rejected Meta App Review costs more than the review period itself. The launch waits, the client waits, and the next submission is read by a reviewer who now has a reason to look harder. After integrating Facebook Pages, Instagram, Messenger and WhatsApp APIs in production products, I treat App Review as part of the engineering work, not as paperwork at the end.

The goal is simple: a reviewer who has never seen the product should understand what it does, see exactly where each permission is used, and confirm that the usage follows Meta's Platform Terms and Developer Policies, within a few minutes. Everything in this guide serves that goal.

Step 1: Map every permission to a real feature

The most common mistake I see is requesting permissions “just in case”. Every permission in the submission must map to a feature the reviewer can see working. If a permission is not visible in the screencast, it gets rejected, and it makes the rest of the submission look less credible.

  • List every Graph API call the app makes and the permission each call needs.
  • Remove permissions that are only planned for a future feature. You can request them later in a separate review.
  • Check whether Standard Access is enough. Many apps need Advanced Access only for a few permissions, for example when they serve businesses they do not own.
  • Write one sentence per permission describing the user-facing feature it powers.

I keep this mapping in a small table inside the project repository. It becomes the source for the use-case descriptions, the screencast script, and later for the resubmission audit if anything goes wrong.

Step 2: Complete the App Review prerequisites first

Many submissions fail for reasons unrelated to the product. Before I submit, the app settings and business setup must be complete.

  • Business Verification is complete for the Business Portfolio that owns the app, when the requested access requires it.
  • The privacy policy URL is public, loads without login, and describes Meta data specifically.
  • A data deletion callback or data deletion instructions URL is configured and working.
  • App icon, category, and contact email are set and match the product.
  • The reviewer can reach the app: a public URL or an installable build, plus working test credentials.

Step 3: Write use-case descriptions for a stranger

Reviewers do not know your product, your customers, or your internal vocabulary. I write each permission's description as a short story: who the user is, what they are trying to do, which screen they use, and what data the app reads or writes through the permission.

A weak description says: “We use pages_messaging to provide customer support.” A strong one says: “A support agent opens the Inbox page, selects a conversation from a customer who messaged the business's Facebook Page, types a reply, and clicks Send. The app uses pages_messaging to deliver that reply to the customer in Messenger.” The second version tells the reviewer exactly what to look for in the video.

I avoid marketing language, future plans, and internal names. I use the exact button labels that appear on screen, so the reviewer can match text to video.

Step 4: Record a screencast that proves each permission

The screencast is the evidence. A good one shows the complete flow from a logged-out state, without cuts that hide important steps. I covered the full process in how to record a Meta App Review screencast, but the essentials are:

  • Start from the app's login screen and show the Facebook Login or Facebook Login for Business flow.
  • Show the permission dialog so the reviewer sees what the user grants.
  • Demonstrate each permission in the same order as the submission, with an on-screen label naming it.
  • Show the result on Meta's side when relevant, such as a message arriving in Messenger or a reply appearing on an Instagram comment.
  • Use English UI or captions and a readable resolution.

Step 5: Run a pre-submission rejection audit

Before submitting, I go through every permission and ask: if I wanted to reject this, what reason would I use? Is the use case unclear? Is the permission missing from the video? Do the test credentials expire? Does the privacy policy mention this data? Each answer becomes a fix.

I also ask someone who did not build the feature to watch the screencast without sound and explain what each permission does. If they cannot, a reviewer probably cannot either. This short audit has saved more review cycles than any other step, and it is the best protection against the vague “unable to verify use case” rejection.

Meta App Review submission checklist

This is the checklist I paste into the project before every submission:

  • Each requested permission maps to a visible feature, and unused permissions are removed.
  • Business Verification, privacy policy, data deletion, icon, and category are complete.
  • Use-case descriptions use real button labels and describe the user, action, and data.
  • The screencast starts logged out, shows the permission dialog, and labels each permission.
  • Reviewer credentials work from a private browser window and need no two-factor code.
  • Reviewer instructions are numbered, short, and tested by someone else.
  • The app version the reviewer can access matches the version in the video.

What to do after you submit

Do not change the review environment while the submission is pending. I freeze the reviewer account, keep the test data intact, and avoid deploying changes that touch the login or permission flows. If the review is approved, I switch the app to Live mode and verify each permission with a real account. If it is rejected, I follow a structured audit before resubmitting instead of rushing a second attempt.

Frequently asked questions

How long does Meta App Review take?

Review times vary with Meta's queue and the permissions requested. Plan for several days to a few weeks, and assume a rejection adds another full cycle. Preparing carefully is the most reliable way to shorten the total time.

Do I need Business Verification for App Review?

Not for every permission, but Advanced Access to many business permissions and the WhatsApp Business Platform require it. Complete Business Verification before submitting so it does not block approval.

Can I request permissions for features I will build later?

You should not. Reviewers reject permissions they cannot see in use. Submit them in a later review once the feature exists.

Should I record one screencast or one per permission?

Either works if each permission is clearly labeled. I prefer one video with chapters per permission, because it shows the shared login flow once and keeps the context clear.