All postsPaid media13 min read

ads_management vs ads_read: why many ad tools can read your campaigns but not change them

ads_read lets a tool report on Meta ad accounts; ads_management lets it change them. One app declined on July 28 and approved on November 2, 2026, what changed between, what the permission lets a tool do, and how to check your connection.

overads teamPublished Updated

TL;DR

  • ads_read lets an app pull ad reports for the Meta ad accounts it can reach; ads_management lets it read them and also create and manage campaigns. A tool used by other businesses needs each one approved separately in Meta App Review, after Business Verification.
  • Meta asks for an unapproved permission only from people with a role on the app. Everyone else connects without it, sees no error, and the gap shows only when the tool tries to change something.
  • Meta declined ads_management for overads on July 28, 2026 and approved it on November 2, 2026, once the reviewer could watch a live change. Meta and Google ad changes run after you approve them; X and Snapchat connect read-only, so overads proposes and a person applies.
  • A tool with ads_management can pause, resume, re-budget and launch ads through the API. It cannot do more than the connecting person's role allows, and in overads nothing runs until a person confirms it.
  • LinkedIn splits read (r_ads) from write (rw_ads). Google Ads and Snapchat each have one scope that allows both, so on those two the advertiser's lever is the role of the person who connects the tool.
Meta
Google Ads
LinkedIn
Snapchat
The four ad platforms whose read and write permissions this guide compares.

What changed: rewritten on November 3, 2026, after Meta approved ads_management for overads on November 2, 2026. The sections on the July 28 decline are kept as history, and three sections are new: what changed on November 2, what a tool with ads_management does and does not do, and how to tell whether your own connection holds it. Google's access levels are updated to its October 30, 2026 page.

What ads_read and ads_management allow

ads_read and ads_management are the two Meta permissions an outside app uses to work with ad accounts: ads_read covers reporting, and ads_management covers reporting plus changes. Meta's permissions reference defines both. ads_read gives an app the Ads Insights API, which returns report data for ad accounts the user owns or has been given access to. ads_management lets an app both read and manage those ad accounts.

ads_read and ads_management side by side, from Meta's permissions reference, read November 3, 2026
Questionads_readads_management
What it allowsPull ad report data through the Ads Insights API, and send web events from a server through Meta's server-side APIRead and manage the ad account
Allowed usage Meta listsCustom dashboards and data analytics; sending web eventsCreating campaigns, managing ads and fetching metrics; building ad management tools
Permissions it depends onNonepages_read_engagement and pages_show_list
Screencast Meta asks forThe login, a business reaching its ad data, and metrics such as impressions, spend and clicks on screenThe same three steps
Needed to serve other businessesAdvanced Access, through App ReviewAdvanced Access, through App Review

Two details in that table are easy to miss. ads_read is not purely passive: Meta's reference says it also lets advertisers send web events from their servers to Facebook, so a reporting permission can carry data in as well as out. And the screencast requirements for ads_management repeat the ones for ads_read word for word, all about showing performance data. Meta's App Review tutorial adds the general rule: recordings must show actions that require the permission requested, and a permission without a recording will not be approved. overads' two outcomes below suggest the general rule is the one that counts.

The same reference lists a third ads permission, ads_mcp_management, which lets an app reach Meta's ads Model Context Protocol server so AI agents can create and manage campaigns, read reports and manage catalogs, ad accounts and pixels for advertisers.

How Meta decides which apps get each permission

Meta lets an app use ads_read or ads_management for people outside its own team only with Advanced Access, which Meta grants one permission at a time through App Review, after Business Verification. Meta's access levels page sets out the split. Every Business app gets Standard Access automatically, but a permission with Standard Access can only be requested from people who have a role on the app, such as its admins, developers and testers. Advanced Access lets the app request the permission from anyone.

The App Review process page says Meta's reviewers test the app itself. If they cannot reach the app at all, the whole submission is rejected. If they can test the app but cannot test the feature that needs a permission, that permission is not approved. For a tool that will serve other businesses' ad accounts, Meta's pages describe this path:

  1. Build and test with Standard Access, which works for people with a role on the app.
  2. Complete Business Verification for the business that owns the app.
  3. Make at least one successful API call with each permission within 30 days before submitting.
  4. Record a screencast for each permission that shows the login and the actions that use it.
  5. Tell reviewers how to reach the app. Meta tests with its own test accounts and asks applicants not to share personal credentials.
  6. Submit, and wait for the decision. The tutorial says it should arrive within a week.
  7. Separately, move the Marketing API Access Tier from Limited to Full access, which needs at least 500 Marketing API calls in the last 15 days and an error rate under 15% across the last 500 calls.

The last step is about volume, not permission. Meta's Marketing API authorization page says Limited access is meant for development, not for apps serving live advertisers. The page also notes that Meta renamed the tiers: what it called Standard Access for this feature is now Limited access, and Advanced Access is now Full access, and the threshold for Full access came down from 1,500 calls to 500.

What happened when overads applied, in July 2026

Meta approved ads_read and business_management for overads and declined ads_management, in an App Review decision dated July 28, 2026. That one decision is why overads' Meta ad access was read-only from July to November 2026.

What the decline looked like in practice is the useful part:

  • The login did not fail. overads' Meta connection asks for both ads_read and ads_management. Because ads_management had only Standard Access, Meta asked for it only from people with a role on overads' Meta app. Every customer's connection came back holding ads_read alone, with no error.
  • The gap showed up later. A connection without ads_management can read every report. A change sent through it comes back refused: Meta's Graph API error guide lists codes 200 to 299 as permission errors, meaning a permission was never granted or has been removed.
  • Approval is per app and per permission. overads runs separate Meta apps for ads and for publishing. On the same date, Meta renewed pages_read_engagement for the ads app and declined it for the publishing app.

overads handled this by reading which permissions each connection actually holds from Meta, rather than trusting the list it asked for. A change the connection was not granted was refused before anything was sent, and the change controls stayed off in production. This article does not guess at the reviewers' reasons for the decline.

What changed on November 2, 2026

Meta approved ads_management, read_insights and pages_manage_engagement for overads on November 2, 2026, on a resubmission of the same app. The table lists the two decisions side by side.

Meta App Review outcomes for the overads ads app, July 28 and November 2, 2026
PermissionJuly 28, 2026November 2, 2026
ads_readApprovedHeld
business_managementApprovedHeld
ads_managementDeclinedApproved
read_insightsDeclinedApproved
pages_manage_engagementDeclinedApproved
threads_basic and threads_content_publishDeclinedDeclined again

Three things were different in the second submission. Each is a fact about what overads sent, not a claim about why Meta decided as it did:

  1. The reviewer could watch a live change. In July, ad changes were switched off everywhere in production by a single flag, so a reviewer who clicked Pause saw a refusal. For the resubmission, overads added a second switch that turns changes on for listed workspaces only, listed the reviewer's workspace, and left every other workspace as it was. The permission check still applied: a listed workspace can only change an account whose connection actually holds ads_management, which before approval meant only people with a role on the app.
  2. One screencast per change, not per permission. The July submission leaned on performance screens, which is what Meta's reference describes under ads_management. The November shot list was written around changes instead: a campaign paused and resumed, a daily budget changed, and the assistant's own pause proposal confirmed from a chat, each followed by the result in Meta Ads Manager. Meta does not say which of the three differences counted, so this is what changed, not why it worked.
  3. A reviewer login that never met the checkout. overads is paid from day one, so the reviewer's account was put on a plan in advance and its steps were written as direct links to each screen.

The approval changed the product the same day: the global flag was switched on in production and the reviewer's workspace was taken off the list. Meta and Google ad changes run after you approve them; X and Snapchat connect read-only, so overads proposes and a person applies. A connection made before November 2 still holds ads_read only, because Meta grants a permission at login; the next section says how that shows.

What a tool with ads_management can and cannot do

A tool with ads_management can change the ad accounts the connecting person can manage, within that person's own role. Meta's reference describes the permission as reading and managing the ad account, and Meta's task-based access table caps a token at what the person could do in Ads Manager. What a given tool does with the permission is the tool's choice. The table is overads' own list, read from its code on November 3, 2026.

What overads does with ads_management, from its code on development, read November 3, 2026
ActionDoes overads do it?Who decides
Pause or resume a campaign, ad set or adYesA person confirms each change, or a bulk change, first
Set or scale a daily or lifetime budgetYesA person confirms it
Edit an ad set's audience and locationsYesA person confirms it
Attach a new creative to an adYesA person confirms it
Launch a campaign and ad setYes, created pausedA person confirms it and activates it in Ads Manager
Create a custom or lookalike audienceYesA person confirms it
Run an automation rule that changes adsYesThe workspace rule for ad changes is set to ask by default, so the rule stages a proposal; an owner or admin can set it to act within limits
Create an ad account, or change billingNoNot built
Change ads on Google, X or SnapchatNoThose connections are read-only, so overads proposes and a person applies

Every one of those changes passes the same gates in order: the workspace's own switch, a check that the entity belongs to the workspace, the ad account's acceptance of Meta's Business Tools Terms, the connection's actual ads_management grant, and a person's confirmation. Each successful change is written to an audit log with who confirmed it. The default workspace rule for ad changes is ask, which means a routine, a workflow or an automation rule can stage a change but not apply it; an owner or admin can raise that to act within limits, or lower it to never, in the workspace rules.

How to tell whether your connection has ads_management

A Meta connection holds the permissions Meta granted at the moment of login, so a connection made before an approval keeps its older, thinner set. Three checks show which set a connection holds:

  1. Ask Meta, not the tool's request list. overads reads each connection's granted permissions back from Meta's token-debug endpoint and caches the answer per connection. It never keeps a table of what App Review approved, because such a table is stale the moment a decision changes.
  2. Read the notice on the change control. When a change control is unavailable, overads says which of three things failed, in three different sentences: Meta has not granted ads_management on this connection (with a Reconnect Meta link), ad changes are not enabled for this workspace, or overads could not confirm what it may do. The first is Meta's decision, the second is overads' own switch, and the third means the lookup never answered.
  3. Reconnect to pick up a new permission. Reconnecting Meta from the integrations page asks Meta for the permission again, and the same debug read then shows it. Reports keep working either way, because they need only ads_read.
Ask Meta, not the tool's request listoverads reads each connection's granted permissions back from Meta's token-debug endpoint.
Read the notice on the change controloverads says which of three things failed, in three different sentences.
Reconnect to pick up a new permissionReconnecting Meta from the integrations page asks Meta for the permission again.
Three checks that show which permissions a Meta connection holds.

On Facebook's side, the business integrations settings list every connected tool and what it can do, with a Remove button; a removed tool can no longer manage your ads but may keep information it already had.

How Google, LinkedIn and Snapchat separate reading from changing ads

Google Ads, LinkedIn and Snapchat each draw the line between reading and changing ads in a different place. LinkedIn draws it in the permission, as Meta does. Google draws it in the developer's approved use. Snapchat leaves it to the role of the person who connects the tool.

Where four ad platforms separate reading ads from changing them, from each platform's developer docs, read October 5 and November 3, 2026
PlatformRead-only permissionPermission that can change adsWhat the developer needs firstRead-only role for the person connecting
Metaads_readads_managementApp Review for each permission, after Business VerificationPartial access with View performance
Google AdsNone: one scope, adwords, covers bothThe same adwords scopeAn API access level on the Google Cloud project; at Standard access, a Reporting permissible use limits the tool to read-only callsRead-only access level
LinkedInr_ads and r_ads_reportingrw_adsApproval for the Advertising API, which comes with bothViewer (allowed r_ads only)
SnapchatNone: one scope, snapchat-marketing-api, covers bothThe same scopeAn Organization Admin creates the OAuth app in Snap Business ManagerReports role

Google Ads. Google's OAuth guide for the Google Ads API names a single scope for the API, and Google's list of OAuth scopes describes it as access to "see, edit, create, and delete" Google Ads accounts and data. So a reporting tool and a bidding tool ask for the same consent. The read-only limit Google offers sits with the developer. Its access levels page, updated October 30, 2026, says developer tokens were retired on September 9, 2026 and access is now set per Google Cloud project, at four levels: Test (test accounts only), Explorer (2,880 operations a day on production accounts, with account creation, user management, planning and billing services withheld), Basic (15,000 operations a day, after brand verification) and Standard (unlimited, after a manual audit that typically takes 10 business days). Its permissible-use section applies to Standard access only, and its Reporting use limits a project to read-only calls.

2,880
Operations a day at Explorer access
On production accounts
15,000
Operations a day at Basic access
After brand verification
10 business days
Typical time for the manual audit for Standard access
Standard access is unlimited
Google Ads API access levels, from Google's access levels page, updated October 30, 2026.

LinkedIn. LinkedIn's Marketing API key concepts define rw_ads as managing and reading a member's ad accounts, limited to members with a billing admin, account manager, campaign manager or creative manager role. r_ads reads ad accounts and also works for the Viewer role. LinkedIn's access page lists both among the permissions that come with approval for the Advertising API.

Snapchat. Snapchat's Marketing API authentication page says its one scope lets an app read and write, and that the access token reflects the user's own permissions. Its roles page defines a Reports role with read-only access to an ad account.

On every platform, the person's role caps what any tool can do through them. Meta's task-based access table gives View performance the right to view ads and access reports, but not to create or edit ads. Google's account access levels let a Read-only user view campaigns and run performance reports, while only Standard and Admin users can edit campaigns.

Is read-only ad access safer?

Read-only ad access is safer in one specific way: a tool that cannot write cannot pause a campaign, launch an ad or raise a budget, whether through a bug, a bad suggestion or a leaked token. How firmly that holds depends on who enforces it:

  • Enforced by the platform. On Meta, a token without ads_management cannot change ads. On LinkedIn, a token without rw_ads cannot either.
  • Enforced by the tool's code. On Google Ads and Snapchat, a reporting tool usually holds a scope that allows changes. Unless its project is limited to Reporting, its read-only status is a choice in its code.
  • Enforced by your own role. On all four platforms, connecting a tool from a read-only role limits it to reading, whatever scope it holds.
Enforced by the platform
On Meta, a token without ads_management cannot change ads
On LinkedIn, a token without rw_ads cannot either
Enforced by the tool's code
On Google Ads and Snapchat, a reporting tool usually holds a scope that allows changes
Unless its project is limited to Reporting, its read-only status is a choice in its code
Enforced by your own role
On all four platforms, connecting a tool from a read-only role limits it to reading
Whatever scope it holds
Who enforces a tool's read-only ad access.

Read-only access has costs too. A tool that cannot write cannot act at night or at the moment a campaign goes wrong; a person has to make every change in the platform's own ad manager, and the tool sees the result on its next sync. For changes that should happen without a third-party tool at all, the platforms' own rules run inside the platform: automated rules in Meta Ads Manager can notify you or act, for example by pausing an ad or raising a budget, and Google Ads automated rules can change ad status, budgets and bids. A tool with write access and a confirmation step sits between the two: it can act, but only after a person says yes. Our guide to human in the loop AI for marketing covers which changes are worth leaving to a person, and the agency client onboarding checklist covers how to ask a client for access from the right role.

What to ask any ad tool before connecting it

Five questions show what an ad tool can do in your accounts before you connect it:

  1. Which permissions or scopes does it request? On Meta, ads_management means it can change ads. On Google Ads and Snapchat every tool's scope allows changes, so ask what its code actually calls.
  2. Which of those has the platform approved? A Meta permission without Advanced Access works only for people on the developer's own team, and the tool's login will not tell you which ones you were granted.
  3. Does a change need a person to confirm it? Ask whether the tool shows the exact change first and keeps a record of who approved what.
  4. Does it work from a read-only role? If the tool only reports, ask whether it runs when connected from Meta's View performance access, Google's Read-only level, LinkedIn's Viewer role or Snapchat's Reports role.
  5. How do you remove it? On Facebook, the business integrations settings list every connected tool with a Remove button. In a Google Account, the linked apps page has a Remove access button.

If you are choosing between tools that write to ad accounts, our guides to Madgicx alternatives and Birch alternatives say which ones act on ads and which only read. Meta, TikTok and Amazon also let an AI agent change campaigns through their own MCP servers; our comparison of the Meta ads MCP server with Google's and TikTok's says which official servers can write.

Where overads fits

overads fits a team that wants to read Meta, Google, X and Snapchat ads in one place and keep every change behind a person's yes. overads reads those platforms and proposes changes, each linked to the campaign it refers to. Meta and Google ad changes run after you approve them; X and Snapchat connect read-only, so overads proposes and a person applies. The platforms overads connects differ in depth: Meta, Google and X sync every campaign, ad set and ad; Snapchat shows spend totals only. The LinkedIn ad connection is built, and no data flows from it yet. The same split is stated on the about page.

The read-only limit on X and Snapchat is overads' own. Its Google connection uses Google's only Ads scope, which Google describes as "see, edit, create, and delete", and its Snapchat connection uses Snapchat's single read-and-write scope, but overads' code calls only their read endpoints. Its X Ads connection, live since October 23, 2026, works the same way. overads workflows and the workflow templates follow the workspace rule for ad changes: by default they stage a change for a person to confirm, and on X and Snapchat that person applies it in the platform.

The overads workflows home: a box to describe a job in plain English, with connected accounts beside it
overads workflows follow the workspace rule for ad changes: by default they stage a change for a person to confirm.

overads does not fit a team that wants software to apply ad changes on its own across every platform. On Meta and Google it changes ads only after a person confirms, or within limits an owner or admin has set; on X and Snapchat it cannot pause, edit or launch an ad or change a budget at all. For that, the platforms' own automated rules run without a third-party tool. Our comparison of cross-platform ad management tools sets out what else is available. Reading a competitor's ads is a separate question from reading your own: our guide to whether you can see a competitor's ad spend covers what each ad library publishes.

Frequently asked questions

Does an app need App Review to manage only its owner's ad account?

No. Meta's Marketing API authorization page says standard access to ads_read and ads_management is enough for an app that manages only your own ad account. Advanced access is needed to manage other people's ad accounts.

I connected Meta to overads before November 2, 2026. Do I need to reconnect?

Yes, if you want overads to change ads. A connection made before the approval holds ads_read only, so every ad change control shows a notice that ads_management is not granted and a Reconnect Meta link. Reconnecting asks Meta for the permission again. Reading reports does not need it.

Can a Google Ads tool at Explorer or Basic access change campaigns?

Google's access-level page restricts Explorer projects from account creation, user management, planning and billing services, not from campaign changes, and its read-only Reporting use applies only to Standard access. So at Explorer or Basic access, only the user's role or the tool's own code keeps a tool read-only.

How long does Google take to review Standard access for the Google Ads API?

Google's access-level page, updated October 30, 2026, gives a typical review time of 10 business days for Standard access, which involves a manual audit. It says Google may upgrade a project to Explorer or Basic access automatically after the application.

Sources

  1. Permissions Reference for Meta Technologies APIs. Meta for Developers. Accessed Nov 3, 2026.
  2. Access Levels. Meta for Developers. Accessed Nov 3, 2026.
  3. Marketing API: Authorization. Meta for Developers. Accessed Nov 3, 2026.
  4. App Review process. Meta for Developers. Accessed Nov 3, 2026.
  5. App Review tutorial. Meta for Developers. Accessed Oct 5, 2026.
  6. Graph API: Handling errors. Meta for Developers. Accessed Oct 5, 2026.
  7. Business portfolio assets and their task-based access settings. Meta Business Help Centre. Accessed Oct 5, 2026.
  8. How do I edit the privacy and settings for my business integrations or remove them from Facebook?. Facebook Help Centre. Accessed Oct 5, 2026.
  9. About automated rules in Meta Ads Manager. Meta Business Help Centre. Accessed Oct 5, 2026.
  10. OAuth 2.0 internals for Google Ads API. Google for Developers. Accessed Oct 5, 2026.
  11. OAuth 2.0 Scopes for Google APIs. Google for Developers. Accessed Oct 5, 2026.
  12. Access levels and permissible use. Google Ads API, Oct 30, 2026. Accessed Nov 3, 2026.
  13. About access levels in your Google Ads account. Google Ads Help. Accessed Oct 5, 2026.
  14. Manage links between your Google Account and apps from other developers. Google Account Help. Accessed Oct 5, 2026.
  15. Set up automated rules. Google Ads Help. Accessed Oct 5, 2026.
  16. LinkedIn Marketing API: Key Concepts. Microsoft Learn. Accessed Oct 5, 2026.
  17. LinkedIn Marketing API: Increasing Access. Microsoft Learn. Accessed Oct 5, 2026.
  18. Marketing API: Authentication. Snap for Developers. Accessed Oct 5, 2026.
  19. Marketing API: Roles. Snap for Developers. Accessed Oct 5, 2026.

Drafted with AI assistance, then checked against primary sources and the product itself by the overads team.

Read Meta, Google, X and Snapchat ads in one place

overads Ads manager reads your ad accounts in one view. Meta and Google ad changes run after you approve them; X and Snapchat connect read-only, so overads proposes and a person applies.

Get started