Guide5 min read

Understanding your baseline

What does it mean when TagWatch says purchases are below baseline? You find the baseline of every event under the site’s Monitors › Events, and in Analytics once a site is picked.

What the baseline is

The baseline is TagWatch’s answer to one question: how many events do we normally get on a day like today? It is learnt from the last four weeks, on its own, in the background.

Think of a shop manager who knows they sell about 80 pairs of shoes on a Tuesday. If they sold 20 by closing time, something is wrong. That is the baseline.

An example: the purchase event

Over the last four Tuesdays a shop had 120, 135, 118 and 127 purchases, so about 125 is normal for a Tuesday. This Tuesday the Tag Manager container was unpublished at 10:00 and only 18 purchases arrived. TagWatch compares 18 with 125, sees a drop of 86%, and alerts the next morning, long before a monthly report would.

The threshold

Not every dip is worth an alert. A rainy day or a bank holiday is not an emergency. The threshold says how far a count must fall before you hear about it. The default is 80%: alert only when the count drops more than 80% below normal. A day that empties out completely is caught anyway, whatever the threshold.

Start with 80%. Lower it for an event whose count barely moves from week to week, where a smaller dip already means something.

Monday is compared with Monday

Most sites have a weekly rhythm. A B2B site gets its demo requests on Tuesday and Wednesday and almost none on Saturday; a fashion shop is busiest at the weekend. So TagWatch only compares like with like: this Monday with the last four Mondays. A quiet Sunday never sets off an alert because Friday was busy. There is nothing to configure.

The first four weeks

  • Week 1. Collecting data. A count that drops to zero is caught after the first days.
  • Weeks 2 and 3. Provisional baseline. Zero counts are caught; drop alerts stay paused.
  • Week 4 and on. Normal baseline. Drop alerts are on, and one Baseline ready email says so.

Just added a monitor and no alerts yet? That is how it should be.

When an alert arrives

  1. Is the tag still live? The incident says what changed. Check it on the page itself.
  2. Are the campaigns still running? A budget that ran out or a paused campaign means fewer visits and fewer events.
  3. Is the site up? A checkout that errors takes purchases to zero at once.
  4. Is there a business reason? A holiday, a product out of stock, a promotion that ended. Then resolve the incident yourself.

Common questions

Black Friday? TagWatch alerts on drops, not on spikes. In the weeks after, the baseline can sit a little high while those days are still in its four week window.

An event that fires once a week? Too few to judge. Drop alerts stay paused below an average of 10 a day; a tag monitor fits better.

Just launched? Add the monitor now. It never alerts without enough history.

The baseline looks high after a promotion? The window rolls, so it settles on its own within four weeks.

Worth remembering

Like for like
Each weekday against the same weekday of the last four weeks.
Start at 80%
It catches real breakage and lets ordinary bad days pass.
Four weeks to learn
Zero counts are caught within days; drop alerts wait for a full baseline.
Drops only
A count above normal never sends an alert.
Try it on your own site
First month 50% off on a monthly plan.