In partnership with
Your conversion rate drops on Tuesday.
You open GA4, compare channels, check devices, and look at landing pages. Paid traffic looks different. Mobile conversions are down. You start forming theories.
Then someone mentions: “We updated the form on Monday.”
Someone else adds: “We also published a new GTM container.”
Now you have two useful starting points, and a question:
Why wasn’t that context available when you first opened the report?
This is one of the most overlooked parts of analytics: keeping a record of what changed.
Two days of free email tactics, starting Nov 12
GURU kicks off Nov 12. Join the 29,000+ marketers who showed up last year, 100% free and virtual.
GURU Conference, powered by Constant Contact, is back November 12–13. It's 100% virtual and 100% free, and it's packed with tactics you can use right away on newsletters, deliverability, design trends, AI, and what NOT to do with email.
What to expect:
Speakers including Molly Ringwald, Dan Levy, Amy Porterfield, Frank Vella + more
Sessions from world-class marketers at top brands
Networking every day
DJs, world-record breaking, and an alarming amount of rom-com fun!
Last year, 29,000+ marketers joined us. This year is even bigger, and spots are limited.
Your dashboard shows the outcome. You also need the context.
A change in performance could reflect customer behavior. It could also reflect a change in how you attract visitors, what they experience, or how you measure their actions.
For example:
A campaign launch changes your traffic mix.
A form update introduces friction.
A GTM release causes an event to fire twice.
A consent banner update changes how much activity you can measure.
A key event definition changes what your reports count as a conversion.
These situations can produce similar-looking movements in a dashboard, but they call for very different responses.
Without a change history, you spend time reconstructing the past before you can investigate the present.
Track improvements, too.
When conversions increase, everyone wants to know what worked.
Was it the new landing page? A different audience? A promotion? Or did a tracking change inflate the numbers?
If you cannot connect results with a reliable record of changes, you risk repeating something that never actually worked or overlooking something that did.
Make the record useful.
For each meaningful change, capture:
When it happened
What changed and where
Who made the change
Why it was made and what you expected to happen
Record it when the change happens. Two weeks later, “we updated something around then” is much less useful.
The goal is to make changes that could affect performance or measurement easy to find.
Start with “What changed?”
When I notice something unusual in the numbers, that’s the first question I want to answer. Having the history in GA Auditor’s Activity Timeline gives me somewhere to start, instead of trying to piece it together from old messages.
An example of the change history I check when something looks unusual in the numbers.
Of course, two things happening around the same time doesn’t mean one caused the other. But knowing what changed helps narrow down what to check next.
Try this with one of your own reports: pick a metric that moved over the past month. Can you find a record of the changes that might help explain it?
If you have to ask three people and search through Slack to find out, that’s a good reason to start keeping a shared change log.
Anil Batra
Try GAAuditor.com - it is free.
