Run more in-house, with the skills you have.
For teams where advertising is shared between a performance specialist, a marketing lead, a brand manager and sometimes finance. Plireo is being built so that each one has a defined part, and so that the reason for a change outlives the person who made it.
A team is not a list of people with the same password.
An example of how the three roles map onto a marketing department. The mapping is yours; the rule is enforced by the server.
| In the team | Role | Reads and asks | Prepares changes | Approves |
|---|---|---|---|---|
| Performance specialist | Operator | Yes | Yes | No |
| Marketing lead | Approver | Yes | Yes | Yes |
| Brand manager | Reader | Yes | No | No |
| Finance or management | Reader | Yes | No | No |
An approver may approve a change they prepared themselves: Plireo does not impose a four-eyes rule today. A separate administrator role, and access limited to some advertisers, are planned.
The day your specialist leaves, the account keeps its settings and loses its reasons.
Many in-house teams know the handover document that is never quite written. The new person inherits two hundred negative keywords, a bidding strategy, three paused campaigns, and no account of why.
The cautious reaction is to touch nothing, and the account stops improving. The confident reaction is to clean up, and something that was there for a good reason disappears.
Plireo is built so that the handover writes itself as the work is done: each decision taken in it is kept with who took it and why, and the business context is versioned, so a past choice can be read against what was known at the time.
The same facts for the specialist, the manager and the finance director.
One set of figures
Everyone reads the same computed figures, with the same date of reading. A meeting starts from the analysis, not from reconciling two exports.
Approval that leaves a trace
A budget increase is approved by the person accountable for it, on the exact amount, with a reason when a check raised a warning.
Context written once
Targets, margins and what must not be touched are written once and used by every analysis, instead of being re-explained in each brief.
Where this stands today
- RolesReader, operator and approver, enforced by the serverIn progress
- Administrator roleA separate administration rolePlanned
- Access by advertiserAccess limited to selected advertisers of an organisationPlanned
- 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
- Recommendations and decisionsChannel-level recommendations, each agreed, deferred, rejected or challengedIn progress
- Advertising MemoryHistory, decisions and business contextIn progress
- Execution by PlireoApplying approved changes, with safety controlsIn progress
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