Every time a tool asks you to "Continue with Facebook," you are making an access decision for your ad account. OAuth is the mechanism behind that button, and knowing how to use OAuth well is the difference between a connection you control and one you forget about. This guide covers how to connect a third-party ad tool to Meta without handing over your password, how to limit what the tool can touch, and how to cut access off when you need to.
Before you start, you need admin access to the Meta Business portfolio that owns your ad account, plus a tool with a Meta login connection. AdStellar is used in the examples below.
Step 1: Confirm Your Meta Access Level Before You Connect
OAuth can only pass along what your own user already holds. If your profile has partial access to an ad account, the tool will inherit that same partial access, and nothing in the connection flow can raise it. Fixing permissions first saves you a confusing round of reconnecting later.
Meta ties authorization to a person, not to a shared mailbox. That means you should connect with your own personal profile login, the one that actually holds roles in the Business portfolio. Do not create a fake profile to hold a connection, and do not log in with a login shared among several people. Meta's rules discourage fake profiles, and a shared login makes it impossible to tell who authorized what.
Run this quick check:
- Open Meta Business Settings for the portfolio that owns the ad account.
- Go to Accounts, then Ad accounts, and select the account you plan to connect.
- Confirm your name appears with the role you expect (full control or admin level for an account you will launch campaigns from).
- Repeat the check for the Facebook Page, and for the pixel or dataset and catalog if you run e-commerce ads.
The most common mistake here is connecting as a user with partial permissions, then wondering why the pixel, Page, or catalog never shows up in the tool. The tool is not broken. Your user simply cannot see that asset. Menu labels in Business Settings change from time to time, so if a path looks different, search the settings for "Ad accounts" or "People."
Step 2: Understand the OAuth Flow You Are About to Approve
OAuth 2.0 is an authorization standard, defined in RFC 6749. In plain terms: you approve an app on Meta's own login screen, and the app receives a token it can use on your behalf. It never receives your password.
That last point corrects the most common misconception. People assume that connecting an app means sharing credentials. It does not. Your password is typed only into Meta's page, and the app sees only the result of your approval.
The flow, in order
- Redirect. You click the login button in the tool and are sent to a Meta domain.
- Consent screen. Meta shows which permissions the app is requesting and lets you choose which assets to share.
- Authorization code. Once you approve, Meta sends a short-lived code back to the app.
- Token exchange. The app trades that code, behind the scenes, for an access token.
The terms worth knowing
A scope (Meta calls these permissions) is a named category of action the app may perform, such as reading ad performance or managing campaigns. An access token is the credential the app presents to Meta's API each time it acts for you. Bearer tokens are described in RFC 6750, and the name tells you the risk: whoever holds the token can use it, which is why tools store them carefully and why you can revoke them.
Tokens are not permanent. Meta documents long-lived tokens, and their lifetimes and refresh rules can change, so check Meta's developer documentation for the current behavior as of 2026. When a token expires or is invalidated, the fix is usually to reconnect.
One more distinction: OAuth is about authorization, meaning what the app may do. Logging in with Facebook also proves who you are, but that identity step sits alongside OAuth rather than being what OAuth itself provides.
If you are a developer building an integration rather than using one, the work looks different: you register an app with Meta, set redirect URIs, and implement the authorization code flow. This guide stays on the user side.
Step 3: Start the Connection From Your Ad Tool
In AdStellar, choose the Meta connection option and click the login button. Your browser redirects to a Meta page, and that redirect is the visible sign that OAuth is working as intended.
Before you type or click anything on that page, do a safety check on the address bar. The domain should be Meta's real one, facebook.com, with a valid secure connection. Be wary of lookalike spellings or a page that appears inside the tool's own interface. Just as important, you should never be asked to enter a Meta password into the ad tool itself. If a tool asks for that, stop. That is not OAuth.
A few practical details prevent the usual failures:
- Blocked pop-ups. Some tools open the Meta login in a pop-up window. If nothing appears, allow pop-ups for the tool's site and try again.
- Wrong browser profile. If your browser is already logged into a different Meta account, Meta will often skip the login and authorize that account instead. Check which profile name appears on the consent screen. If it is wrong, switch browser profiles or log out of Meta first.
- Wrong account for the client. Agencies juggling many logins are the most exposed to this mistake.
If you run an agency, set up a separate workspace per client. AdStellar supports unlimited workspaces, and keeping each client's authorization in its own workspace means one client's connection can be reviewed, replaced, or revoked without touching the others. It also prevents the awkward situation where a campaign for one brand is built against another brand's ad account.
Step 4: Review and Grant Only the Permissions You Need
The consent screen is where you actually exercise control, so read it line by line rather than clicking through. It lists what the app is asking to do and gives you a say over which assets it can reach.
For ad management, the requests typically map to Meta permissions such as ads_read (reading performance data) and ads_management (creating and editing campaigns). Meta renames and adds permissions over time, so verify the current scope names in Meta's developer documentation before relying on any list, including this one.
Match the access to the job:
- A tool that builds and launches campaigns needs write access. Without it, nothing can be created or edited.
- A tool used only for reporting or analysis needs read access and little else. If a reporting tool asks for more, that is worth questioning.
The second decision is which assets to share. Meta's consent flow commonly lets you choose specific ad accounts, Pages, and pixels rather than granting everything in the portfolio. Choose only the ones the tool should manage. If you have ten ad accounts and want to automate two, select two. You can widen access later, but you cannot undo something an over-permissioned token already did.
Troubleshooting: if an ad account, Page, or pixel is missing from the list, the cause is almost always your role, not the tool. Go back to Step 1, fix your access in Business Settings, then restart the connection so the consent screen reflects your updated permissions.
When you are satisfied, approve. Meta returns you to the tool, and the authorization code exchange from Step 2 happens without any further action from you.
Step 5: Verify the Connection and Run a Low-Risk Test
A completed redirect does not prove everything works. Verify read access and write access separately, starting with the cheap checks.
First, look at what the tool displays. You should see the correct ad account, the right Page, and the pixel you expect. Performance data such as spend, results, and recent activity should be pulling in from Meta. If the account is right but the numbers are empty, wait a few minutes and refresh before assuming a fault.
Next, test read access by importing an existing Meta campaign. If the campaign appears with its structure and metrics intact, the tool can read your account properly.
Then test write access with something small and safe:
- Create a single simple campaign with a minimal budget, or build it and leave it paused.
- Launch it from the tool.
- Open Meta Ads Manager and confirm the campaign appears under the correct ad account, with the settings you chose.
- Delete or keep it paused once confirmed.
Checking in Ads Manager matters because it is Meta's own record. It confirms the tool wrote to the account you intended, which is especially important if you manage several.
If something fails, look at the error before touching the campaign. An expired token, an authorization error, or a message saying the session is no longer valid usually means the connection needs refreshing, not that your campaign settings are wrong. Reconnect through the same flow, and recheck that your Meta role has not changed since you first connected.
Step 6: Set Up Ongoing Security Habits and Know How to Revoke Access
A connection is not a one-time decision. The same token that makes automation possible stays active until it expires or you remove it, so build a few habits around it.
Know the revoke path
You can remove an app at any time. Look in Meta Business Settings under the integrations area, and in your personal Facebook account settings under Business Integrations (or similarly named app and website settings). Menu names change, so verify the current labels as of 2026. Removing the app there invalidates its access, and the tool will need a fresh connection to work again.
Habits worth keeping
- Reconnect when people leave. Because authorization is tied to a specific user, a connection made by someone who has left the company can break, or linger, depending on their account status. Have a current admin reconnect, then remove the old authorization.
- Turn on two-factor authentication. The connecting Meta profile is the root of the whole chain. Protect it with two-factor authentication so a stolen password alone is not enough.
- Audit connected apps on a schedule. Review the list of authorized apps periodically and remove anything you no longer use. Old trial tools and former agency integrations are the usual leftovers.
- Keep the connecting role tight. Do not give the connecting user more Business Settings power than it needs.
Treat revocation as routine, not as an emergency measure. Revoking and reconnecting costs a minute, and it is the cleanest answer to the question "who can still touch this account?"
Step 7: Apply the Same OAuth Pattern to Other Tools in Your Stack
Once you have done this for an ad tool, you can recognize the pattern everywhere. Attribution platforms, analytics tools, and reporting dashboards use the same redirect, consent screen, and token structure. For example, connecting Cometly alongside your ad account lets conversion data flow back to your campaign tool, and each of those links is its own OAuth authorization you can review and revoke separately.
Use this checklist on any OAuth request before you approve it:
- Who is the app? Confirm the app name matches the vendor you meant to connect.
- Which scopes? Check that the permissions fit the tool's purpose. Write access for a reporting tool is a red flag.
- Which assets? Select only the accounts, Pages, and pixels required.
- How do I revoke it? Know where to remove it before you grant it.
Be cautious with any tool that offers a weaker alternative. If a service asks you to paste a password, or to copy an API key or token into a form, understand what you are trading away. A pasted credential usually carries broader, less trackable access, and it is harder to scope or cleanly revoke than an OAuth grant. Prefer the OAuth option whenever it is available.
Your Connection Is Live: Review It Quarterly and Put It to Work
With live data flowing in and a successful test launch confirmed in Ads Manager, you now have a secure, revocable link between your Meta account and your ad tool. Put a recurring reminder on the calendar for a quarterly access review: check who holds admin roles, which apps are authorized, and whether any connection belongs to someone who has moved on.
From here, the connection is a foundation rather than the goal. Use it to build campaigns from your past performance, launch variations in bulk, and let monitoring run while you focus on strategy. Learn more about our services



