How annotations work
An annotation is a short note pinned to a date. Analytics and advertising platforms let you attach one to a chart so that anybody looking at the graph later sees a marker on the day something happened: the site migrated, the budget doubled, tracking broke, a television interview aired, a competitor’s shop opened down the road.
Mechanically it is trivial — a date, a line of text, sometimes a category. What makes it valuable is that it is written at the moment of the change, while the cause is still obvious. Nobody remembers in March why traffic bent in October, and reconstructing it from memory produces confident guesses rather than facts. The note captures the fact for free if it is written on the day.
Why annotations matter
Every unexplained movement in a chart eventually gets explained by whoever is telling the story, and people explain movements in whatever way suits them. A rise becomes proof that the work is paying off; a fall becomes an algorithm update. Annotations remove that argument, because the cause is recorded before anybody has a stake in it.
They matter most when several changes overlap. If the site was redesigned in the same fortnight the tracking was rebuilt and a campaign paused, a chart alone cannot separate them, but a dated set of notes can at least show what to rule out first. They are also the fastest defence against blaming a fall on something imaginary — an unexplained dip in a report invites invented causes, and an invented cause leads to a wasted month.
Common mistakes with annotations
The first is only annotating the things you did. Marketing changes are easy to remember; the events that move data hardest often belong to somebody else — a supplier out of stock, a price rise, a phone line down, a festival week when the whole country is away from its desk. A useful log records business events, not just campaign events.
The second is vagueness. “Made changes to the site” tells the next reader nothing. The third is keeping them in one person’s head or one person’s account: a note only helps if the people who read the monthly report can see it too. The fourth is confusing an annotation with an explanation. Two things happening on the same day is not proof that one caused the other, and a note should say what happened, not assert a result.
How to act on it
Make it a habit rather than a project. Write a note the same day for anything that could plausibly move a number: tracking edits, budget changes, price changes, site releases, stock problems, PR, staff absence, and predictable seasonal events such as Dashain, Tihar or an exam intake. Keep each one to a sentence with a date and, if the platform allows, a category.
Then use them. Before explaining a movement in a report, read the log for that period and the weeks before it; slow channels lag their causes. When nothing in the log explains the change, say so plainly instead of reaching for a convenient story.