PushRPMPushRPM

Plugin workflow

PushRPM Autopilot Modes Explained

Understand PushRPM's autopilot modes — manual, assisted, autopilot safe, and autopilot growth — and choose how much PushRPM applies on its own.

Main intent

Help publishers pick the right level of automation and understand the safety guardrails behind auto-apply.

Short answer

Autopilot sets how much PushRPM does for you: manual surfaces recommendations only, assisted nudges you to review, autopilot safe auto-applies only low-risk high-confidence changes, and autopilot growth adds guarded experiments. Higher modes require a higher plan.

What autopilot controls

Autopilot decides whether PushRPM only recommends changes or also applies them for you. Every mode keeps a full change ledger so you can see, pause, and roll back anything. Auto-apply never touches changes that increase ad density or use aggressive placements — those always stay manual.

Manual

PushRPM scans, detects leaks, and surfaces recommendations, but applies nothing automatically. You review and apply each change yourself. Best when you want full control or are still learning how your site responds.

Assisted

Same as manual for safety — nothing is auto-applied — but PushRPM actively prompts you when a high-value, low-risk action is ready, so review takes seconds. A good default for hands-on publishers.

Autopilot safe

PushRPM auto-applies only changes that clear strict hard rules: low risk, high confidence, applicable severity, and a large enough traffic sample. It will not increase density on an already-dense site, and it auto-rolls-back a change if guardrail metrics regress. This is the recommended automated mode for most monetized sites.

  • Only low-risk, high-confidence recommendations are applied.
  • A minimum traffic sample is required before any auto-apply.
  • Density increases and aggressive placements are never auto-applied.
  • Regression triggers an automatic rollback.

Autopilot growth

Everything in autopilot safe, plus guarded A/B experiments that test placement variants and promote winners automatically — still inside the same safety rails. Best for publishers who want PushRPM to keep pushing RPM with minimal hands-on time.

Plan ceilings and the safe default

Auto-apply modes are part of your plan entitlement. If you downgrade, PushRPM clamps a stored higher mode down to the highest your plan allows — so it never silently keeps auto-applying beyond what you pay for. On any uncertainty it fails safe to manual.

Implementation checklist

  • Open Optimization in the dashboard and find the autopilot control.
  • Start in assisted or autopilot safe while you build trust.
  • Confirm your plan supports the mode you want.
  • Review the change ledger after the first sweep.
  • Move to autopilot growth once safe mode is producing wins.

Common mistakes

  • Expecting density-increasing changes to auto-apply — they never do.
  • Jumping to autopilot growth before reviewing safe-mode results.
  • Assuming a downgrade keeps your old automation level — it is clamped down.

Example

A Growth-plan publisher runs autopilot safe for two weeks, sees consistent low-risk wins in the ledger with no rollbacks, then upgrades to autopilot growth to let PushRPM run guarded placement experiments.

FAQ

Can autopilot hurt my site?

Auto-apply is restricted to low-risk, high-confidence changes with a minimum traffic sample, and it auto-rolls-back on regression. Density and aggressive placements are never auto-applied.

Can I undo what autopilot did?

Yes. Every change is logged in the ledger and can be rolled back. Autopilot also rolls back on its own if guardrail metrics regress.

Which mode should I start with?

Assisted or autopilot safe. Move to autopilot growth once you have seen safe-mode wins you trust.

Related docs