Automation drafts · ClickPay

ClickPay

Jump to product, campaign, PO, or run a command ⌘K

● ops 14m ● ppc 2h ● api ok 3 approvals

Automations

Rules Runs Approvals

Drafts

Workflows

Tags

Audit log

Saved views

High confidence 1

Worth a look 1

Too thin to propose 1

⏎ open x dismiss c create staged

Automation Drafts

3 patterns found in 11 weeks of your manual changes · nothing here is running

Last 90 days

How this works

Review all

Drafts 3

Dismissed 8

Became rules 4

These are drafted from changes you made by hand, not from what the model thinks a good rule looks like. Each one is backtested against the period it was learned from, and the times it would have disagreed with you are listed rather than averaged away.

What it watches

Pause a campaign when cover drops under 14 days seen 7 times

first seen Jul 28

what I watched you do

Jul 28 You paused PB038 · Coil Spring · SP Exact the morning after cover hit 12 days.

Aug 2 Same move on PB224 · Putty · SP Broad at 11 days.

Aug 5 Two campaigns on PB106, both under 13 days.

Aug 9 PB224 again, this time after it went out of stock.

Aug 14 PB345 at 11 days — paused within four hours of the restock alert.

2 more, both the same shape

the rule that would be

when Days of cover < 14

and Campaign state is enabled

and Spend in the last 7 days > $50

then Pause the campaign

unless A replenishment PO lands within 10 days

at most 6 campaigns per run, once per campaign per week

if it had been on for 90 days

would have fired

matched what you did

you would have overridden

The three it would have got wrong: SW043 twice in May, where a PO was already at port — the unless clause above exists because of them. The third is PB211 on Jun 14, which you left running deliberately to hold rank through a stockout. Nothing in the data explains that one, so the rule would still get it wrong.

Drafted from your own actions. It starts staged and gated like any other rule — creating it sends nothing.

Dismiss

Edit first

Create it, staged

Negate a search term after 40 clicks with no sale seen 12 times

first seen Jul 11

what I watched you do

12× You added an exact negative after a term crossed roughly 40 clicks and zero orders.

median You acted at 44 clicks and $38 of spend.

range 31 to 68 clicks — you waited longer on branded terms.

never You have never negated a term carrying our own brand name.

the rule that would be

when Clicks ≥ 40 in the last 30 days

and Orders = 0

and Term does not contain measurite

then Add as an exact negative at the ad group

at most 20 per run

if it had been on for 90 days

would have fired

matched what you did

you would have overridden

All five overrides were terms that later converted — between 41 and 58 clicks, all on PB345 during its launch, when a term with no sales yet is not the same as a term with no sales. Raising the threshold to 60 clicks removes all five and loses about $310 of the savings.

The brand exclusion is not something you configured — it is inferred from 12 occasions where you could have negated a brand term and did not.

Dismiss

Edit first

Create it, staged

Raise the budget when a campaign caps before noon and ACoS is under target seen 5 times

not proposed — 5 occurrences, and you reversed 2 of them within a week

3 drafts · 2 proposed · 1 held back for want of evidence

a draft never runs; creating one makes a staged rule