Seasonal & event tracking playbooks
Written before each window, with findings added after. No forecasts presented as measurements.
Most event retail analysis is published after the fact and is useless for preparing. These are written beforehand, because the decisions that determine whether your event data is usable are all made before the window opens.
Current playbooks
Each covers what changes in that window, the collection design it requires, and the measurement mistakes that recur.
Black Friday 2026 price tracking playbook
Written before the event, not after. What to set up now, and what nobody can tell you yet.
October to November 2026India festive season 2026 tracking playbook
A window that runs for weeks, not days, and where pincode-level collection stops being optional.
Approximately 18 February to 19 March 2027Ramadan 2027 GCC grocery tracking playbook
A window where the shopping day inverts, which breaks collection schedules designed for daytime retail.
Why these are playbooks and not reports
An event report published after the window is interesting and arrives too late to act on. Every decision that determines whether your event data is usable — when to start, what cadence, which fields, how to compute a baseline — is made before the window opens.
So these are written beforehand, and findings are added to each page after the window closes, dated, with the cadence and population stated. Nothing on these pages presents an unmeasured figure as a finding.