Quick summary (30 sec)
Build if-this-then-that automations across campaigns, inventory, and alerts.
What is it?
Automation Builder helps you create guarded automation recipes for member operations inside Verion Ads. Automation Builder encodes repeatable ops decisions—pause low CTR, notify on fill drops, or scale winners.
Why use it?
Build if-this-then-that automations across campaigns, inventory, and alerts.
When to use — and when not
- Use when your goal matches Automation Builder.
- Do not use if the menu item is hidden — the feature is OFF for you.
How it works in Verion
From Moat Hub (or direct link), open Automation Builder and adjust the module’s controls for your inventory ops.
Who it is for
- Growth ops
- Publisher ad ops
- Power advertisers
Step-by-step
- Open Automation Builder and start from a template or blank rule.
- Define trigger, conditions, and actions carefully.
- Add notification or approval steps for risky actions.
- Test in a limited scope first.
- Enable and review automation run history weekly.
Best practices
- Prefer pause-and-alert over delete actions.
- Name rules clearly with owner and purpose.
- Disable noisy rules instead of ignoring alerts.
FAQ
What problem does Automation Builder solve?
Open Automation Builder when you need operator-grade controls that classic member menus do not cover.
What usually blocks Automation Builder?
Most often: Moat entitlement and module enablement Feature key: automation_builder.
Troubleshooting
Cannot open or use Automation Builder
First check: Moat entitlement and module enablement. Requires the operator to enable the “automation_builder” plugin when it is gated.
Automation Builder runs but results look empty/wrong
Verify plan access and that you opened the intended Moat module (Automation Builder).
Was this helpful?