A fix-list you cannot act on is a to-do list. Ads Manager turns a finding into a change request against the live account — with a dry run first.
The report says a search term wasted £340. Now you open Google Ads in another tab, find the campaign, find the ad group, add the negative, and hope you put it at the right level.
Repeat for every finding, across every client. The analysis was the easy part; the transcription is where the errors and the hours go.
Position Eleven builds the operation for you and sends it to the Ads API — after showing you exactly what it will do.
A finding becomes a concrete change request — a budget adjustment, a negative keyword, a pause — with the resource it targets named.
Google validates the operation without applying it. You see whether it would succeed before anything is live.
Sent through the Ads API on the connection already authorised for reporting. Partial failure is surfaced rather than silently swallowed.
The dry-run path exists because the alternative is discovering a mistake in a client’s live account. Google validates the whole batch and reports what would have happened.
When one operation in a batch fails, the others still apply and the failure is reported — rather than an all-or-nothing that hides which part broke.
Changes go through the same authorised connection as reporting. There is no second OAuth flow and no separate token to manage.
Change requests are stored, so there is a trail of what was proposed and what was applied.
This writes to a live advertising account, which is genuinely consequential. Use the dry run. Position Eleven deliberately does not offer a one-click “apply everything” across a whole fix-list — batching a dozen unreviewed changes into someone’s live account is not a feature, it is an incident waiting to happen.
No. Nothing is applied without an explicit action. There is no autopilot.
Budgets, keywords, negatives and campaign state are the main ones. The transport is general, so the set grows without a rebuild.
Google’s error is surfaced rather than hidden behind a generic failure, so you can see exactly which operation was refused and why.
Validate first, then apply — on the connection you already authorised.
Get started