Meta Ads · BYO Setup Guide

Set up your own
Meta Business app.

This guide walks you through creating a Meta Business app that VelaReach will use to connect your Facebook + Instagram ad accounts — on your own credentials, your own rate limits, your own branded consent screen. Takes about 10 minutes of clicking plus Meta’s business verification (1–3 business days).

~10 min setup Medium 1–3 days review
Use BYO if
  • · You’re hitting the shared VelaReach app’s rate limits (>1M API calls / day)
  • · Your legal team needs data isolation to a dedicated app
  • · You’re a large agency and want your own branded consent screen
  • · You already have an approved Meta app from another tool
Stick with shared app if
  • · You don’t already have a Meta Developer account
  • · You haven’t completed Meta Business Verification before
  • · You want to be connected in the next 60 seconds
  • · Your team is just getting started with VelaReach

Before you begin

1

Create a Meta Business app

Sign in to developers.facebook.com. In the top-right menu click My AppsCreate App. When Meta asks to choose an app type, select Business. Name it something recognisable like VelaReach-YourCompanyName. Attach it to your Business Manager.

https://developers.facebook.com/apps/creation/
Meta for Developers · My Apps
Create an app
Select an app type — this determines which APIs you can use.
● Business
For tools that connect to Marketing API, WhatsApp, Instagram Graph
○ Consumer
For apps that let users sign in with Facebook
Next

The "Business" app type unlocks the Marketing API that VelaReach uses.

Don’t have a Business Manager? Create one at business.facebook.com first — Meta requires one for Marketing API apps.
2

Add the Marketing API product

Inside the app dashboard’s left sidebar, click Add Products. Scroll down until you find Marketing API and click Set up. This unlocks the scopes VelaReach will request: ads_management, ads_read, business_management.

https://developers.facebook.com/apps/123456789012345/add/
VelaReach-Acme · App dashboard
Add a product
📈 Marketing API
Access Meta Ads data — campaigns, insights, ad accounts.
Set up
Facebook Login
Required for OAuth user consent

Marketing API is the product you want — not "Facebook Login for Business" or "Instagram Basic Display".

3

Whitelist the VelaReach redirect URL

This is the most common thing to get wrong, so copy carefully. In the left sidebar, find Facebook LoginSettings (you may need to add the Facebook Login product first if it isn’t already listed). Scroll to Valid OAuth Redirect URIs and paste this exact URL:

https://api.velareach.metaminds.store/api/v1/integrations/meta/callback
https://developers.facebook.com/apps/.../fb-login/settings/
Facebook Login · Settings
● Yes
● Yes
↑ This is the exact URL VelaReach redirects back to after consent.
Save Changes

The redirect URL must match character-for-character. No trailing slash.

90% of BYO failures happen here. If OAuth later returns “The redirect URI isn’t whitelisted”, come back and check the URL is character-identical. No trailing slash, no query params, HTTPS only.
4

Copy your App ID and App Secret

Click SettingsBasic in the left sidebar.

https://developers.facebook.com/apps/123456789012345/settings/basic/
Settings · Basic
↑ 15-digit number. Click to select, Ctrl+C.
Show ↑ Click Show, re-enter your password to reveal.
Save Changes

App ID is safe to copy anywhere. The App Secret is sensitive — never paste it in Slack or email.

🔒
Treat the App Secret like a password. VelaReach encrypts it with AES-256-GCM the moment you submit, and never writes it to logs.
5

Paste credentials into VelaReach

Back in VelaReach: SettingsIntegrations → click the Meta Ads card → ManageAdvanced tab → Set up BYO app. The 4-step wizard opens. Click past Intro and Guide, then on Step 3 paste the App ID and App Secret from the previous step.

Click Test & save. VelaReach makes a live call to Meta’s Graph API with your credentials and runs 5 validation checks inline.

6

Verify the live test passes

You should see green check marks next to:

  • · Credentials format — App ID and secret look well-formed
  • · Redirect URL whitelisted — matches Meta’s settings
  • · App exists on platform — Meta returned your app’s name and status

You’ll likely see one amber warning about scope_sufficient — that’s expected because Meta can’t confirm Advanced Access until after your first real user OAuth. Amber is fine; only red means a real problem (see Troubleshooting below).

Click Reconnect now → to run the OAuth flow through your new app. The consent screen will show your app name.

7

Optional — submit for App Review

Your app works in Development Mode for people listed as developers on the app. To use it for your whole team or clients, submit for review:

  • · Click App Review in the left sidebar
  • · Under Permissions and Features, request ads_management, ads_read, business_management
  • · Upload a 30–60 second screencast showing VelaReach’s OAuth flow
  • · Submit. Approval takes 1–3 business days.
You don’t have to submit for review to use BYO with your own team. Development Mode works for app admins out of the box.

After reconnecting, what changes?

✓ Preserved
  • · All historical spend, impressions, and ROAS data
  • · Your picker selection (which ad accounts are tracked)
  • · Automation rules and budget pacing configs
  • · Scheduled reports and Slack notifications
  • · Every tag, filter, and saved view
✦ Changed
  • · OAuth tokens revoked and re-minted via your app
  • · Card shows violet BYO app pill
  • · Consent screen on future reconnects displays your app name
  • · Audit log records who switched and when
  • · API calls count against your app’s rate limits

Troubleshooting

“Meta rejected the redirect URL”
You didn’t save the URL in Step 3, or you have a typo. Return to Facebook Login → Settings → Valid OAuth Redirect URIs and paste again using the Copy button. Meta is strict about trailing slashes and protocol (https, not http).
“Missing or invalid client id” from Graph API
The App ID you pasted isn’t recognised. Likely a stray space, or you copied the display name instead of the numeric ID, or the app was deleted. Open Settings → Basic in Meta, re-copy just the 15-digit number, and Test again.
OAuth works for me but not my team
Your app is in Development Mode, which restricts OAuth to app admins/developers/testers. Add each teammate’s Meta user ID under Roles, OR submit for App Review (Step 7) to open the app to anyone in your workspace.
“Ads management permission required but not granted”
Meta granted the OAuth token but stripped the ads_management scope. This happens when your app hasn’t passed Business Verification. Open Business Manager → Business Info and complete verification, then re-run Reconnect.
I want to revert to the shared VelaReach app
In the BYO wizard (or the Advanced tab of the Manage drawer), click Remove BYO. VelaReach wipes the encrypted credentials, flips back to the shared app, and revokes your app’s active tokens. Historical data stays. Click Reconnect once more to mint fresh tokens via the shared app.
💬
Stuck? Email us — we’ll hop on a 15-min screen share.
BYO is advanced setup and we don’t expect every customer to nail it the first try. Email support@velareach.com with your workspace name + exact error and we’ll pair with you.