Meta Access Verification: Passing the Tech Provider Test

Access verification is the second gate on the road to Meta App Review, and it asks a different question than the first. Business verification proved your company exists. Access verification tests whether that company is a genuine Tech Provider: a business whose software accesses Meta business assets and information belonging to other businesses. That describes every B2B tool that touches customers' Pages, Instagram accounts, or insights, which means every serious marketing platform files this form.

The form is four questions on a single screen. We filed it the morning our business verification cleared, and the Verified badge arrived within hours, against a quoted five days. Short forms reward preparation: the framing of each answer matters more than its length, and one question is an identity test wearing a survey's clothes.

When does the gate open, and what pressure is on it?

Two clocks touch this form. It stays locked until business verification clears; ours displayed exactly that message until the first gate passed. And the dashboard attaches a completion deadline with app restrictions behind it, months out in our case. Neither clock was our real driver: App Review cannot be submitted until access verification passes, so the practical deadline is your own launch plan. File it the day it unlocks.

One instruction at the top deserves a highlight: complete the form for your own business only. You are answering as the software vendor, never on behalf of a client.

Which business types do you select?

The multi-select offers Agency, Freelancer, Consultancy, SaaS Platform, and Other, and the guidance says to pick what best describes the part of your business providing Tech Provider services.

We selected SaaS Platform, alone, and the restraint was the point. Agency and Consultancy describe businesses that operate accounts on clients' behalf, a different data relationship than software the client operates with their own hands. The temptation is to tick more boxes for coverage; resist it, because a SaaS company that also claims Agency has recast its whole data story, and every later reviewer reads this filing. Select the boxes that are true, and only those.

How do you answer the Platform Data question?

The core question asks how your business will use Platform Data to enable a product or service on behalf of clients, and the form's own guidance sets the register: describe the service, how Platform Data enables it, and how clients use it, in short sentences without technical jargon.

Write it like a product description a non-engineer could repeat back. Ours said, in substance: clients connect their own Facebook Page and Instagram account to the platform, publish their own posts through it, and read their own engagement in dashboards; Platform Data is used only to show each client their own performance; no data is sold or shared. No endpoint names, no API vocabulary, no architecture.

Whatever you write here becomes part of a story reviewers cross-check later, against your data-handling answers, your privacy policy, and eventually your permission screencasts. Consistency across those filings is worth more than polish in any one of them.

What is the portfolios question really asking?

"Does your business manage multiple business portfolios?" reads like a survey demographic. It is an identity check. Managing client business portfolios, with partner access to their Business Manager accounts, is how agencies operate. OAuth-based software does something structurally different: each customer grants access from their own account, scoped by consent, and the vendor manages no portfolio except its own.

For a platform like ours the honest answer is No. Answering Yes triggers a request for the portfolio IDs of the businesses you manage, a list an OAuth product does not have, and files you under the agency model your other answers just disclaimed.

What does the website need to show?

The form wants a URL to a complete site showing the service you described and the business providing it. Two consistency rules make this easy to pass and easy to fail. The site should describe the same service your Platform Data answer described, in recognizably the same terms. And it should sit on the domain your business verification carries, so the whole chain of filings points at one identity.

How fast does it clear, and what unlocks?

Meta states a follow-up within five days. Ours went from Submitted to Verified within hours, the same day, with a status line confirming the business was verified as a Tech Provider. A clean filing on a just-verified business appears to move fast.

Clearing it removes the last platform-side gate before the submission itself: the App Review wizard's verification section shows green, and everything that remains, usage descriptions, screencasts, the reviewer test account, is work in your own hands. That remaining work is mapped in the complete App Review guide, and the gate before this one has its own field guide.

FAQ

What is access verification and who needs it?
Meta's test that your business is a genuine Tech Provider, required for any app accessing other businesses' Meta assets, and locked until business verification clears.

Should a SaaS company also tick Agency?
Only if it genuinely operates accounts for clients. Software the client operates is SaaS Platform, and extra boxes recast the data relationship.

How do you answer the portfolios question?
OAuth-based SaaS answers No. The question describes agency-style partner access to client Business Manager portfolios.

How long does it take?
Quoted five days; ours verified within hours of filing, the same day.