OAuth is an open authorization standard that lets one app act on your behalf inside another service without ever seeing your password. Every time you click "Connect Meta account" in an ad tool, OAuth is the mechanism deciding what that tool can and cannot do inside your ad account. It is not a login system, and it is not a way of handing over your credentials. It is a way of handing over a narrow, revocable slice of access.
If you buy media, run an agency, or manage an e-commerce ad budget, you approve these connections constantly. Understanding what what is OAuth really means in practice lets you read a permission screen with confidence, spot a request that goes too far, and clean up old access before it becomes a problem.
Delegated Access Without Sharing Passwords
OAuth is a framework for delegated authorization. You, the owner of an account, allow a third-party app to do specific things in that account for a limited time, and you can take that permission back whenever you like. The app never receives your password. It receives a token, which is a different kind of credential with different properties.
The classic analogy is the valet key. It starts the car and lets the attendant park it, but it does not open the trunk or the glovebox. Map that to advertising: an ad tool might be allowed to read performance data and create ads, but not change the payment method on the account. The scope of the key is the whole point.
Before OAuth became standard, apps simply asked for your username and password and logged in as you. That meant the app had full access to everything, could change your password, and could not be cut off without you changing your own credentials, which broke every other integration too. There was no way to say "read only" or "this one app, not that one."
A few terms will recur throughout this article:
- Authorization: deciding what an app is permitted to do. This is what OAuth handles.
- Resource owner: you, the person who owns the account and can grant access.
- Client app: the third-party tool asking for access, such as an ad platform.
- Access token: the credential the app presents to prove it has been granted access.
- Scope: a specific permission attached to that token, such as reading ads or managing them.
The key distinction to hold onto: a password proves who you are and unlocks everything. A token proves only that you approved a particular app for particular actions.
The Four Players and the Authorization Code Flow, Step by Step
Every OAuth connection involves four roles. You are the resource owner. The ad tool is the client. The authorization server is the system that authenticates you and records your consent; for Meta, that is Facebook Login. The resource server holds the data and performs the actions, which in your case is the Meta Marketing API where your campaigns, audiences, and reporting live. If you are still getting oriented with the platform itself, our guide on what Facebook Ads Manager is covers the interface these permissions ultimately unlock.
The most common arrangement for web apps is the authorization code flow. Here is what happens when you connect an ad account:
- You click Connect or Continue with Facebook inside the ad tool.
- Your browser is redirected to Meta's own consent screen, which lists the app and the permissions it is requesting.
- You approve (or decline). If you approve, Meta redirects you back to the app.
- That redirect carries a short-lived authorization code, not the access itself.
- The app's server sends the code directly to Meta, along with its own client credentials, and receives an access token in return.
Why the extra step? The browser is a leaky environment. URLs end up in history, logs, and referrer headers. By sending only a one-time code through the browser and doing the token exchange server to server, the token itself never appears in a URL. The code is also short-lived and useless without the app's own secret, so intercepting it gets an attacker very little.
Versions and flow types
OAuth 2.0, specified in IETF RFC 6749 (2012), is the version in use today, and bearer token usage is described in RFC 6750. The standard defines several flow types, and choosing the right one matters for security. The authorization code flow suits server-side apps because the secret stays on the back end. Older shortcuts that returned tokens directly in the browser are now discouraged. As a marketer you will not choose the flow, but you benefit when a vendor uses the right one, and you can tell you are in it when you see that redirect to Meta's own consent page.
Scopes and Tokens: What You Are Actually Approving
Scopes are the individual permissions an app asks for, and they are the part of the consent screen worth reading. In the Meta advertising world, commonly seen examples include ads_read for viewing ad and performance data, ads_management for creating and editing ads, and business_management for working with business assets. As of November 2026 these names are the ones typically referenced in Meta's developer documentation, but Meta revises its permissions, so check the current docs if you need exact details.
Consider a worked example. Suppose a creative-analysis tool asks to read your ads and pull reporting. The consent screen lists permission to view ad performance, plus permission to manage ads and business assets. Reading and reporting justify the first. If the tool only produces reports and never launches anything, the management permission is broader than the job requires. That is a reason to ask the vendor why, or to look for a tool whose requests match its function. A launch tool, by contrast, legitimately needs management access, because creating campaigns requires it. Reporting-focused tools, like a Facebook ad analytics tool, should in principle need far less than a launcher does.
How tokens behave
Access tokens are deliberately short-lived, so a stolen one has a limited window of use. To keep a connection working without making you re-approve constantly, systems issue either refresh tokens, which can be exchanged for new access tokens, or longer-lived tokens. Meta uses its own token model, and lifetimes have changed over time, so verify the current figures in Meta's documentation rather than relying on a number you read elsewhere.
The important property is that a token is not a password. It carries only the scopes you approved, it can be revoked on its own, and revoking it does not require you to change your credentials or disturb any other app.
OAuth vs. Passwords, API Keys, and SSO
These mechanisms get lumped together, but they differ in three ways: who holds the secret, how access is limited, and how it is cut off.
- Shared password: the app or person holds your actual credentials. Access is all or nothing. Revoking means changing the password, which locks out everyone using it.
- API key: a static secret tied to an account or project. Scoping varies by provider, and the key is typically shared across whoever holds it. Revoking means rotating the key and updating every system that uses it.
- OAuth: the app holds a token issued after your consent. Access is limited by scope and tied to a specific user and app. Revoking removes one app's grant without touching anything else.
- SSO: a single identity provider signs you into many services. It is about proving who you are once, not about limiting what an app can do.
The common confusion is between authorization and authentication. OAuth answers "what may this app do?" OpenID Connect is an identity layer built on top of OAuth 2.0 that answers "who is this user?" When you use "Sign in with Google" or "Continue with Facebook," the service often uses both: OpenID Connect to confirm your identity and OAuth to grant any additional access. That overlap is why people call OAuth a login protocol, though on its own it is not one.
The agency case makes the difference concrete. If a team shares one login to a client's ad account, you cannot tell who did what, you cannot remove one person without affecting the rest, and a departing freelancer still knows the password. With per-user OAuth grants, each person or tool has its own revocable connection, so access can be removed individually and nothing else breaks. This is also why understanding what a media buyer does day to day helps you decide who truly needs access to which accounts.
What OAuth Looks Like When You Connect an Ad Account
In practice, connecting an ad account to a platform such as AdStellar follows the code flow described earlier. You choose to connect Meta, land on Meta's consent screen, and review the requested permissions. You then select which ad accounts and Pages the tool may use. Only the assets you select are made available, which is a second layer of limitation beyond scopes.
Once the grant is in place, the platform can use its token to call the Marketing API. That is what makes real-time performance data possible without CSV exports, and it is what allows a tool to import your existing campaigns and analyze past performance. The same permission that lets it read history lets it create and launch new campaigns, which is why the management scope appears on the screen. This delegated access is the foundation of Facebook ad automation, and it is also what lets an AI media buyer act inside your account on your behalf.
For agencies, the structure matters. Connecting each client's ad account into its own workspace keeps permissions separated by client. When a contract ends, you remove that client's connection and the grant for that account is gone, with no effect on the other clients you manage.
One more point: connections are per tool. An attribution integration such as Cometly has its own authorization connection to Meta and to your store, with its own scopes and its own consent screen. Approving one tool does not approve another, so review each tool's permission list separately and keep a note of what each one can do. The same applies to tracking setups like the Meta Pixel, which is configured separately from your ad tool's API access.
Staying Safe: Mistakes to Avoid and How to Revoke Access
Most OAuth risk comes from habits rather than from the standard itself. The mistakes worth avoiding:
- Approving every scope without reading. The consent screen is the only moment you can say no to a permission.
- Leaving old connections active. Ex-vendor, ex-freelancer, and abandoned trial tools often keep valid grants long after the work ends.
- Connecting through a personal profile with admin rights across many businesses. A token inherits the reach of the person who approved it, so a broad profile creates a broad grant.
An audit you can do this week
As of November 2026, you can review connected apps in your Facebook account settings under Business Integrations, and in Meta Business Suite or Business Settings under the integrations or connected apps areas. Menu names and paths move around, so search the settings for "Business Integrations" if the layout has changed. For each entry, ask whether you still use the tool, whether the vendor still works with you, and whether its permissions match its job. Remove anything that fails those checks. If you are weighing what to keep, our rundown of software to manage your Meta ad campaigns can help you consolidate to fewer, better-vetted connections.
Revoking a grant invalidates that app's token, so the app loses access immediately. Changing your password alone may not cut off every integration, because tokens are separate credentials and may remain valid depending on how the provider handles them. Remove the app explicitly rather than assuming a password change did it.
Finally, watch where the consent screen appears. It should load on Meta's own domain, reached by redirect from the app. A lookalike page that asks for your password in a pop-up, or sits on an unfamiliar address, is a phishing red flag. Close it and navigate to the app directly.
Delegation You Can Take Back: What to Do Next
OAuth is controlled, revocable delegation, not password sharing. The app gets a limited token for specific actions, you keep your credentials, and you can end the arrangement whenever you choose. That only protects you if you use the controls.
This week, open your connected apps in Facebook and Meta Business settings and remove every tool or vendor you no longer use. Before connecting any new ad tool, read the permission list and confirm that each scope matches what the tool actually does for you.



