Event key
Process + account + object. The same error on the same URL is always the same task, never a new notification.
WORKSHOP · ECOMMERCE.PL EVENT 6.0The Q4 handbook.
The Q4 handbook.
48 pages of specifics.
Q4 is thirteen weeks and several peaks, not one Friday. 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.
Starter pack: five controls to begin the quarter with
The order is deliberate: from the one that costs you every hour to the one that costs you every day.
- 01
Broken landing page
every 6–12 hBudget flows to an address that does not work. The only one of the five that costs money hourly, not daily.
HTTP != 200 · redirect > 3 · load time > 5 s (only URLs with spend in the last 7 days)
- 02
Zero conversions on live budget
every 2–4 hThe most expensive silence in e-commerce. Usually the tag, the checkout, the GA4 import or a switched primary conversion.
24 h spend > 70% of the 14-day daily median · conversions = 0 (baseline median ≥ 3 conversions per day)
- 03
Campaign paused by accident
every 4 hCatches the cause, not the symptom. Zero impressions shows up tomorrow — here you know within four hours, and you know who.
status change in the last 24 h · campaign with revenue history
- 04
Budget pacing
dailyBudget is not something you check on the invoice. Above target ROAS the same condition produces a “scale” task instead of a “slow down” alert.
spend to date / planned spend > 120%, or impression share lost to budget
- 05
Best seller disapproved in Merchant Center
dailyA list of 400 disapproved products is not a task. Three best sellers is a task.
product in the top 20% of 30-day revenue · destination status != approved
Minimum sample — without it a percentage threshold lies
“Down 25%” means nothing until you say on how much data. These are the values worth starting from.
| Metric | Change threshold | Minimum sample |
|---|---|---|
| CTR | −25% vs 28 days | 5,000 impressions |
| Conversion rate | −25 to −30% | 300 clicks |
| ROAS | −20 to −25% | 30 conversions |
| CPA | +25% vs target | 7-day spend > 2 × target CPA |
| Spend without sales | 0 conversions | 7-day spend > max(PLN 500; 1.5 × target CPA; 3% of account spend) |
Three things without which you will mute any alerting system
Quiet period
Three days by default. The next run appends to the existing task instead of creating another one.
Persistence counter
A problem returning for the seventh day in a row raises its own priority. Quiet does not mean forgotten.
Rollout order across the quarter
- todayConnect the account and read the initial audit. Do not change any thresholds yet.
- this weekSwitch on processes 01–03. The defaults are a good starting point.
- after a week of dataSwitch on processes 04–05 and calibrate thresholds to your account volume.
- before every peakTighten the frequency of processes 01–03 and agree who picks up tasks at the weekend.
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.
WORKSHOP HOST
Tomasz Kowalski
Sembot
Got a question about any of these thresholds, or want to run these processes on your account? Write to me — I answer personally.
START WITH A SINGLE PROCESS
Your first completed task.
On your own data.
Connect an account. Pick a process.
Check the first result.