Meta Ads
Manage Meta ad accounts, campaigns, performance reporting, and Conversions API workflows across Facebook and Instagram through OAuth-backed Marketing API access.
| Connection | OAuth |
| Used By | AI Ad Pilot — Required for setup readiness |
Setup Prerequisites
Most customers need a Meta Business user with access to the ad account and Pixel. Teams that bring their own Meta app should also prepare the app-level prerequisites.
- Meta Business portfolio with access to the target ad account, Page or Instagram assets used by the ads, Pixel ID, and dataset.
- Connected Meta user or System User with permission to manage the selected ad account and Pixel.
- Active ad account with billing enabled and no unresolved account restrictions.
- Meta app ID and app secret if using a customer-owned OAuth app.
- Marketing API product added to the Meta app.
- App Review or Business verification completed for the advanced permissions used outside your own business assets.
- Pixel installed on the landing site and server-side CAPI path prepared. Pixel ID plus CAPI verification are required before Meta spend approval. See AdPilot CAPI setup.
OAuth Setup
- Go to your drone’s Settings > Integrations.
- Click Connect next to Meta Ads.
- Sign in with the Meta user that can access the target Business portfolio, ad account, and Pixel.
- Approve the requested Marketing API permissions.
- Select the Business, ad account, and Pixel if AdPilot shows an account picker.
- Confirm the provider card shows
Connected. - Run AdPilot conversion verification before approving Meta spend.
If your organization uses System Users, confirm the System User still has the correct ad account and Pixel asset assignments before reconnecting.
Permission Scopes
| Permission | Why AdPilot needs it |
|---|---|
ads_read | Read campaigns, ad sets, ads, delivery state, insights, and spend. |
ads_management | Create, update, pause, and reactivate campaigns only after customer approval or spend-reducing safety logic. |
business_management | Read Business assets such as ad accounts, Pixels, datasets, and asset assignments needed for setup verification. |
pages_show_list / pages_read_engagement | Required only when the campaign flow needs Page or organic-post assets for creative review. |
public_profile | Basic login identity required by Meta Login. |
AdPilot treats Meta write permissions as capability, not consent. Launches, budget increases, bid changes, and reactivation still require spend approval.
Re-Auth Handling
Reconnect Meta Ads when the connected user is removed from the Business portfolio, System User assets change, App Review permissions change, the token is revoked, or the selected ad account or Pixel is no longer visible.
Meta does not expose a customer-facing fixed re-auth cadence in AdPilot. Reconnect immediately when the dashboard shows Auth expired, Reconnect required, Missing scope, or Pixel unavailable, and re-run CAPI verification if Pixel or dataset access changed. Follow Meta Ads OAuth re-auth.
Limitations And Known Constraints
- AdPilot cannot manage ad accounts, Pixels, datasets, Pages, or Instagram assets that are not assigned to the connected user or System User.
- Meta App Review and Business verification can block production use of advanced Marketing API permissions.
- Pixel-only tracking is not sufficient for AdPilot Meta launch readiness; server-side CAPI verification is required.
- Provider policy review can reject ads after submission.
- Audience, special category, and targeting restrictions remain enforced by Meta.
- Reconnecting Meta Ads does not revive rejected, expired, or stale AdPilot approvals.
Troubleshooting
- If the ad account is missing, confirm Business portfolio assignment and ad account role for the connected user or System User.
- If Pixel verification fails, use AdPilot CAPI setup.
- If Meta reports a missing permission, reconnect and confirm the Meta app has the required App Review access.
- If ads are rejected, fix creative, targeting, landing page, or disclosure issues before requesting a revised approval.
- For campaign, budget, tracking, or auth blockers, use AdPilot troubleshooting.