Skip to main content
Uses Automations and Portfolio. Last updated 9 Oct 2026.

Overview

Changing budgets and bids by hand does not scale past a few ad accounts. Operators who run hundreds set up a system that acts on its own, then spend their attention on the exceptions. In Epsilo that system lives in Automations, and it has four parts.
Available on paid plans. See pricing.

The four parts

How it works

1

Set the split

Pick a distribution per ad account for the goal that matters most: efficiency, revenue, or an even share while products prove out. Lock the budgets you never want touched.
2

Schedule what you know

Add schedules for the known moments: pacing at midnight, a bid lift for peak hours, a target ROAS change for a promotion.
3

Script what you can't predict

Add scripts for conditions: pause a product that spends with no GMV, raise a winner’s budget when it beats target, cap a product whose ROAS falls under your floor.
4

Review before you trust

Use Apply now in Portfolio for changes you want to see first. Move a pattern into a script once you approve it every time.

Use it

Start from a template

In Automations, select New automation, then Start from a template. Templates cover common jobs, so you adjust a proven rule instead of writing one. See Recipes.

Pair every rule

A rule that only pushes one way drifts. Pair a bid increase with a bid decrease, and a budget increase with a cap or a distribution, so spend cannot run away.

Sale days without a second set

Do not keep one script set for normal days and another for sale days. Keep one baseline and add schedules on top for the sale window only. See Double day war room.

Watch the system, not every campaign

Read the Log tab in Automations each week. Epsilo tells you before you save a script that matches one you already have. An automation that keeps failing pauses itself; fix the cause, then select Resume.

Ask Botep

FAQ

Avoid scheduling two budget changes on the same object at the same time. They can override each other. Check the log to see which one ran last.
After repeated failures it cannot fix, an automation moves to Paused. Read the log for the reason, fix it, then select Resume.

Daily check

The fixes worth automating.

Recipes

Ready made automations.

Weekly and monthly review

Review what the system did.
Last modified on October 10, 2026