Skip to content
Use cases · Change control

Know what changes in your ad accounts, who approved it, and why.

In an ad account, one click can move a budget or pause a campaign, and it is live at once. Plireo is being built to put a clear step between the idea and the account: the change is written out, checked, and approved before anything happens.

Before and after

A history tells you what happened. An approval decides whether it should.

The platform's change historyAn approval in Plireo
WhenAfter the change is liveBefore the change is applied
What it showsWhat was changed, and by which user when it was done in the interfaceThe exact before and after, the checks that ran, and who approved
The reasonNot recordedKept with the decision
How far backGoogle Ads: two years in the interface, 30 days through the APIRetention periods will be set out in the terms before launch

Statements about Google Ads come from its documentation, linked at the foot of the page and read on 12 October 2026. Plireo's record covers what is done in Plireo, not changes made directly in the platform.

The path of a change

From an idea to an approved change, in five steps.

You
Plireo
Approver
1YouIn progress

Ask or accept a recommendation

For example: raise the budget of a campaign limited by it.

2PlireoIn progress

Writes the change

The exact before and after, for one campaign.

3PlireoIn progress

Checks it

Current state of the account, limits, duplicates. A failed check blocks the change.

4ApproverIn progress

Approves or refuses

Only a person with the approver role, with a written reason if a warning is open.

5PlireoIn progress

Records everything

Who prepared, what was checked, who approved and why. The record cannot be edited.

Once approved, a change is applied by you in the ad platform. Execution from Plireo, with its safety controls, is in development.

Operate · Optimise · Control

Control that helps you act, rather than slowing you down.

Fewer mistakes in daily management

A change is prepared for one campaign and re-reads its current state: a budget that moved in the meantime is caught before approval.

Optimisations you can defend

Each change comes from an analysis with its sources. The reasoning travels with the request, so the approver sees why, not only what.

A clear answer months later

“Who paused this, and on what basis?” is a line in a record, not a search through emails.

What it covers

Four types of change on Search campaigns, to begin with.

Plireo prepares four types of change on Google Ads Search campaigns: a campaign's daily budget, a negative keyword, pausing a keyword, and a new ad created paused. Each type has its own checks, and a new type is added only with its own.

No change is prepared on Meta, and changes made directly in an ad platform are not imported into Plireo's record.

Where this stands today

The capabilities behind this use case.

  • 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
  • Execution by PlireoApplying approved changes, with safety controlsIn progress
  • Verification after executionReading the live account again after a change is appliedIn progress

Every capability and its status →

Early access

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