Own your alert rules, not the vendor defaults

Default thresholds are calibrated for a vendor's median customer, and you are not the median customer. Three defaults are worth overriding before you use any tool in anger.

The three

The break-even default

Almost every tool ships with a return threshold that is really a statement about margin. If your contribution margin is different from the assumed one, every signal it produces is calibrated wrong, in a direction you will not notice because the number looks plausible.

Compute yours, write it down, and put it in the tool. Which costs to include is a genuine decision, not a formula, and it is covered in the true ROAS guide.

The window default

Attribution and lookback windows encode an assumption about how long people take to buy. A brand selling a considered purchase and a brand selling an impulse purchase should not use the same one, and the default fits neither well.

Your own repeat and consideration intervals are visible in your order data. Use them.

The sensitivity default

Alert sensitivity encodes how often the vendor thinks you want to be interrupted. The right setting depends on how much budget you can realistically move in a week, which for most brands is less than the tooling assumes.

If you cannot act on a signal within the period it describes, the alert is not should be off. The broader case is in why real-time attribution alerts mislead.

Write the rules down outside the tool

Whatever you configure, record it in your own decision log: the threshold, the definition behind it, the date, and who agreed it. Two reasons. Tools change their defaults between versions, sometimes silently. And when you switch tools, the reasoning is the part worth carrying over, not the settings screen.

The habit is described in keeping the attribution record in your own workspace.

Where this product sits

The one-time read has no alerting layer and no automated budget action, so there are no alert defaults to override. What the read returns is what each channel caused next to what last-click gave it, with a data-health score rather than a confidence interval, from a Google Analytics export, and the thresholds are yours to set outside it.

The general rule

Any setting a vendor chose for you is a setting that encodes their assumptions about your business. Most are harmless. The three above are not, and they take an afternoon to fix.

Related answers

• Alert fatigue and what it does to a marketing team
• What a real-time alert is actually detecting
• Why real-time attribution alerts mislead
• Continuous monitoring without handing over your stack