Troubleshooting
Best practices
Get the most signal from first-party data without over-reading noise.
Log changes as you make them
Attribution is only as good as your growth memory. A change logged on the day it ships gives the cleanest before-and-after.
Read for consistency, not spikes
Trust a signal that shows up across queries and pages over a single dramatic day. One spike is noise more often than not.
Respect the confidence label
A modeled or partial reading is a hint, not a verdict. Let more history accumulate before betting on it.
Don't over-read
First-party data is honest but finite. When it cannot answer, it says so - take that at face value rather than forcing a story.