Event key
Process + account + object. The same error on the same URL is always the same task, never a new notification.
Q4 is thirteen weeks and several peaks, not one Friday. And the controls you set up now keep working in January and April — Q4 is merely the reason to start. This is the material from the “Q4 without surprises” workshop: 40 controls, 9 checklists and 6 runbooks for the whole quarter. You can implement the thresholds by hand or switch them on in Sembot.
A catalogue of 40 controls, thresholds with minimum samples, a checklist for every month of the quarter and runbooks for emergencies. Polish language.
Five processes from the Sembot Collection, with their default thresholds. You can change every threshold and schedule on the process card.
Budget flows to an address that does not work. The page went down overnight — in the morning you have a task with the amount and the list of ads.
HTTP status outside 200, 201, 429 (0 = no connection) · active ads
The most expensive silence in e-commerce. Usually the tag, the checkout, the GA4 import or a switched primary conversion.
≥ 200 clicks and 0 conversions in the window · 3 days by default, worth shortening to 1 for Q4
Catches the cause, not the symptom. Zero impressions shows up after 2 days — a pause shows up the next morning.
pause / resume · new or removed campaign · budget change above 1%
Budget is not something you check on the invoice. The task shows ROAS next to the forecast — above target ROAS the call is “scale”, not “slow down”, and you make it.
month-end spend forecast outside the approved plan ± 10% · you enter the plan yourself
A warning is a list to review. A disapproval removes the product from Shopping and PMax — that is today’s task.
products with “disapproved” status (hard block on serving)
“Down 25%” means nothing until you say on how much data. Below are the default process thresholds in Sembot.
| Metric | Change threshold | Minimum sample |
|---|---|---|
| Conversion rate | −25% vs 30 days | 300 clicks |
| Account ROAS | −20% vs 30 days | 10 conversions |
| Zero conversions (tracking) | 0 conversions for 3 days | 200 clicks |
| Product without a purchase | ≥ PLN 100 in 7 days, 0 purchases | + 1 day for conversion lag |
Process + account + object. The same error on the same URL is always the same task, never a new notification.
While the task is open, the next run appends to it. After it is closed — three days of quiet.
The task counts how many checks in a row the problem has lasted. Quiet does not mean forgotten — after three days the process looks again.
An account spending PLN 5k a month and one spending PLN 500k cannot share thresholds. If you are rolling this out by hand, start from the values on the card and after the first week compare the number of alerts with the number of real problems.
CTO, Sembot · workshop “Q4 without surprises”
Software architect and site reliability engineer. The guide’s controls, checklists and runbooks are the tools engineering teams use to keep systems up at peak load, carried over to e-commerce. Got a question about any of these thresholds, or want to run these processes on your account? Write to me — I answer personally.
COO, Sembot · talk “10 marketing fuck-ups that can sink your Q4”
He walks through what most often breaks campaigns in the fourth quarter. The workshop picks up exactly where his talk ends: from the list of mistakes to the controls that catch them.
Connect an account. Pick a process.
Check the first result.