A pause between a proposed change and the live account.
In an ad account, a saved change is usually live at once. Plireo is built so that a change is first written down exactly, checked, and approved by a person with the right to approve it.
A review, a history and an approval are not the same control.
What Google Ads provides, according to its own documentation, and what it leaves to the advertiser's organisation.
| What it is | What it does not do | |
|---|---|---|
| Ad review by the platform | A policy check on ads and assets | It does not ask anyone in your organisation whether the change should be made |
| Change history | A list of changes made during the past two years, with the user for changes made in the interface | It records after the fact. Through the API, change events cover the past 30 days, and not every change has an entry |
| Multi-party approval | A second administrator approves inviting a user, changing an access level or removing a user | The documentation lists these three user actions, not budgets, keywords or ads |
Sources at the foot of the page, read on 12 October 2026. Platform features change; check the linked pages.
What a change goes through.
Prepares the change
An exact before-and-after, not an intention.
Checks it by rule
Live state re-read, duplicates, limits. A failed check blocks; a doubt becomes a warning.
Validates without applying
The platform says whether it would accept the change. Nothing is applied.
Approves that exact change
With a written reason if a warning is open. Edit the change and the approval no longer applies.
Writes the record
Who prepared, what was checked, who approved and why: added, never rewritten.
Once approved, a change is applied by you in the ad platform. Execution from Plireo, with its safety controls, is in development.
A model does not decide whether a change may be proposed.
Budget cap
A single budget change is limited to 30 %. A larger move is made in steps, each one approved.
No cutting what converts
A negative keyword that would exclude queries which converted in the last 30 days, or the campaign's own keywords, is blocked, and they are named.
Evidence before a pause
A keyword pause is checked against 30 days of evidence. Without it the change carries a warning, and approving it needs a written reason, recorded as an override.
Supported, or refused
A change is prepared only for a campaign type and an action Plireo declares it handles. Anything else is refused, with the reason.
Three roles, enforced by the server.
The rule is in the database, not in the screen: a request made outside the interface is refused the same way.
| Reader | Operator | Approver | |
|---|---|---|---|
| Read accounts, analyses and the record | Yes | Yes | Yes |
| Ask questions | Yes | Yes | Yes |
| Prepare a change | No | Yes | Yes |
| Approve a change | No | No | Yes |
By default an approver may approve a change they prepared themselves. Plireo does not claim a four-eyes rule it does not enforce. A separate administrator role and access limited to selected advertisers are planned.
What an approver sees before saying yes.
- 1The exact changeItem by item, before and after. Nothing is summarised away.
- 2The checks and their resultIncluding the dry run by the platform, marked as having applied nothing.
- 3The open warningApproving past a warning requires a written reason, kept in the record.
- 4Where it standsPrepared, checked, validated, awaiting approval, and execution shown as not activated.
Where this stands today
- Prepared changesExact changes, validated by Google without being appliedIn progress
- ApprovalsApproval bound to the exact change, with a written reason when a warning is openIn progress
- Audit recordAppend-only record of what was prepared, checked and approved in PlireoIn progress
- RolesReader, operator and approver, enforced by the serverIn progress
- Administrator roleA separate administration rolePlanned
- Access by advertiserAccess limited to selected advertisers of an organisationPlanned
- Execution by PlireoApplying approved changes, with safety controlsIn progress
- Verification after executionReading the live account again after a change is appliedIn progress
- Settling an unconfirmed changeWhen the platform does not confirm a change sent by Plireo, establishing what really happened before anything else is sentPlanned
- Multi-organisationSeveral organisations with strict separationPlanned
Go further
Be among the first to use Plireo.
Plireo is in pre-launch. Request early access to be told when it opens, or apply to take part in private testing. Access opens gradually, so a request does not mean immediate access.
Paid plans open once the Google Ads, Meta, GA4 and GTM integrations are operationally validated.
Request early access