You connect Google Ads to a Magento profit tool. The consent screen says the app can see, edit, create, and delete your Google Ads accounts and data.
That sentence is enough to stop a careful merchant. It sounds like the tool can pause campaigns, change budgets, or rewrite creatives.
For Magento net-profit apps the reality is narrower — and the scary wording is mostly Google’s, not the product’s.
There is only one Ads API scope
Google Ads API OAuth documents a single scope:
https://www.googleapis.com/auth/adwords
There is no public adwords.readonly (or similar) you can pick in Cloud Console. Every legitimate Ads integration — reporting tools, bid helpers, profit syncs — requests the same string. Google’s consent UI then shows the generic see / edit / create / delete copy for that scope.
So if a Magento P&L product asks for “edit” language, it is usually not inventing a broader permission. It is stuck with the only Ads API scope that exists.
What the scope allows vs what the app does
OAuth answers: *which API family can this token call?*
Your product answers: *which calls does the code actually make?*
Those are different layers. A token that *could* call mutate endpoints does not mean the SaaS *does*. For a spend-into-P&L workflow you typically need:
- Read campaign / account spend (and related metrics) into the store timezone P&L
- Optionally upload offline click conversion values (profit-shaped numbers) when the merchant turns that on
You do not need to create campaigns, edit budgets, pause ads, change targeting, or touch billing — and a serious Magento profit product should not do those things even though the consent copy sounds like it could.
If you want the bidding angle of profit uploads, see Profit-Based Google Ads Conversions for Magento and POAS vs ROAS. New to the API pieces (OAuth, developer token, customer id)? Start with Google Ads API Basics for Magento Merchants.
A second ceiling: the Ads user role
API access also inherits the Google Ads access level of the Google user who clicked Allow.
If that login is Read-only on the Ads account, write-style API calls fail even with the broad adwords scope. If it is Admin / Standard, the token is more powerful — which is why you should connect with a role that matches the job (spend sync + optional conversion upload), not an unused Super Admin on every MCC leaf.
How to read the consent screen without panic
When you review a Magento profit tool’s Google connect flow, check three things:
- Homepage / branding — does the OAuth app name match the product you are on (e.g. Verid on verid.io)?
- Stated use — privacy policy and product copy should say *read spend* and, if relevant, *optional conversion upload* — not “we manage your account”
- In-product controls — spend sync should be obvious; profit conversion upload should be off by default and clearly labeled
Then click Allow knowing the screen text is industry-wide, not a special power grab unique to that vendor.
What Verid does with Google Ads
Verid is Magento net-profit analytics. After OAuth it:
- Syncs daily campaign spend into the same P&L as Magento orders, COGS, shipping and fees
- Optionally uploads click conversions valued from Magento order gross profit (gclid / gbraid / wbraid) when you enable Google POAS conversions
It does not create, edit, pause, or manage campaigns, budgets, creatives, targeting, or billing.
Docs: Ads. Magento connect: Docs · Magento. Try the read-only sample dashboard at /demo.
Practical checklist before you connect
- Confirm you are on the real product domain (HTTPS, expected brand name on consent)
- Prefer a Google user with Ads access limited to the accounts you intend to sync
- Connect spend first; enable profit conversion upload only after COGS coverage looks honest
- After Allow, verify spend rows appear for recent dates — that is the read path working
- If conversion upload is on, confirm actions like “Verid Gross Profit” exist and stay secondary until you are ready to bid on them
- If Google shows an unverified-app interstitial, read what that warning means
Bottom line
The scary consent sentence is a Google Ads API labeling problem, not proof that a Magento profit tool will restructure your account.
Ask what the product *does* after Allow. For Verid, that answer is: pull spend into real net profit — and optionally feed profit values back into Google — not edit your campaigns.