You open Ads in a Magento profit tool, click Connect Meta, and nothing useful happens. Or the developer console shows Business verification — not approved. Someone says “put Conversions API on it.” Someone else wants a Magento module.
Stop. Those are three different jobs.
Three Meta screens, three meanings
| What you see | What it actually is | What it is not |
|---|---|---|
| App Review / permissions | Meta deciding whether ads_read (and friends) can leave Development | Your thank-you page |
| Business verification — not approved | Meta does not yet accept the company behind the app | A dead Purchase pixel |
| Access verification (tech provider) | Extra step to touch other businesses’ objects | Required to compute yesterday’s net |
Google has a cousin of this: the unverified app warning. Same shape — the vendor is in a queue. Different paperwork.
What Magento still owes you without Meta OAuth
Yesterday’s net is Magento orders minus COGS, merchant shipping, fees, refunds and whatever ad spend you already have (Google OAuth, CSV, manual).
That number does not wait on Facebook’s legal team. Statistics are not GA sessions either. If cash is soft, start with yesterday’s net plus one leak, not with CAPI.
SKU contribution stays revenue − COGS. Do not invent Meta fees on the line to “make Ads Manager match.”
What “Connect Meta” is for
A Magento P&L needs Meta for one thing first: daily spend onto the store-timezone calendar. That is pulling Meta spend into net.
The OAuth scopes a profit tool should ask for are read-shaped (ads_read, sometimes business_management to list the ad accounts you already admin). It should not need to publish ads or replace Ads Manager.
Campaign POAS that joins pixel clicks to Magento contribution is Beta. It needs a storefront Purchase, not a verified Business Manager badge. Marketplace / M2E orders never get a Purchase.
Why the founder’s ad account still syncs
If the app admin connects their Meta ad account, Development / unpublished apps often still pull spend. That is why a TagCraft-style shop can look “live” while a second merchant’s Connect button dies.
Treat that as test-user physics, not proof that clients are unblocked. Same pattern as Google test users vs the whole internet.
What not to do while Meta is red
- Do not install a Magento tracking module or Conversions API to “fix verification.”
- Do not paste a second pixel. One Settings snippet is the storefront path.
- Do not pause Magento sync. Orders are the P&L.
- Do not tell the merchant their Business Manager is broken because *your* company check failed.
Resubmit company documents that match the legal name, https://verid.io (or your real domain), Privacy and Terms. Read the rejection reason first. Access-rights verification stays grey until the company row is approved. Then publish the app if it is still unpublished.
A merchant checklist this week
- Magento REST green; yesterday exists in DailyProfit.
- Google spend on the same dates if you buy Search.
- Meta: if Connect works, confirm spend rows — then POAS vs ROAS.
- If Connect fails, enter Meta spend manually for a week. Do not sit dark because a portal is red.
- Pixel: storefront Purchase only. No CAPI required.
Where Verid fits
Verid reads Magento via REST and optional Google / Meta spend into one DailyProfit. Meta OAuth is ads_read + business_management — docs. The pixel stays one snippet.
Business verification is Meta’s gate for other people’s ad accounts. It is not yesterday’s net.
Try the demo, or start a trial. If Meta ROAS is green and the bank is not, start with green Magento, red bank.