Definition
A change log is a dated record of changes made to something the team relies on, kept so that the effect of each change can be traced later. In analytics it covers tags, consent settings, platform settings, site releases, campaign launches, outages and metric definitions; elsewhere it covers CRM fields and record ownership, the rules in a guideline, or the structure of a recurring report.
The word log matters. It is append-only history, not a description of how things are now. The current state lives in the specification, the guideline or the settings; the change log says when that state changed and why.
What an entry holds
The tutorial on keeping a measurement change log gives the full field list for analytics. Across uses, a useful entry carries:
- Date of the change going live, with the time zone where reports cross zones, and an end date for temporary changes and outages.
- What changed, in one or two plain sentences that make sense without the ticket.
- System or document changed, so readers check only what touches their work.
- Owner, the person who made the change and can be asked about it.
- Reason, because a change nobody can explain is likely to be undone by the next person.
- Expected and observed effect, in a measurement log: which figures should move, and later what actually moved.
- Link to the evidence: the container version, ticket, pull request or announcement.
In practice: logging as part of every release
A change log is only as good as its completeness, and the measurement tutorial's rule is that a change is not finished until it is logged. That is why the log appears as a line on release, container publish and campaign launch checklists, and why planned changes are logged before they go live, so people reading reports that week know what is coming.
Other teams use the same habit at a smaller scale. The tutorial on writing customer service tone guidelines gives the guidelines a version date and a change log recording each change, its reason and its date. The tutorial on building a monthly LinkedIn report saves the change log with each month's workbook, so the report's own history stays readable. In the CRM, the tutorial on auditing and documenting CRM fields records each retired field with its date, and the tutorial on reassigning CRM records when someone leaves logs the handover so a dip in follow-up in that territory can be traced to its cause.
A measurement log can also carry trading events such as price changes, as long as they are marked so that measurement changes can be filtered on their own. Style guides, reason lists and trackers usually keep their own logs beside the document they describe.
Change log and decision log
The two are easy to confuse because both are dated tables. A change log records what was changed in a system or document. A Decision LogA running record, one row per decision, of what changed and why, what was expected, who decided and when the result will be checked. records what the team decided, why, what it expected and when the result will be checked. One decision often produces several changes, and a change can be made with no decision behind it, such as a fix or a platform update. Teams that keep both link the rows, so a change can be traced back to the decision that asked for it.
A van hire firm checks the log before celebrating
Taittell Van Hire, an invented van rental firm, opens its morning dashboard to find online bookings recorded in analytics up from 46 to 93 overnight, while the booking system shows 48. Before anyone shares the news, the analyst opens the change log. One entry, made at 08:40 the previous day by the web developer, records a release that added a booking confirmation tag to the new checkout. The container already had a booking tag on the confirmation page, so every booking was now counted twice. The duplicate tag is paused by 11:00, the entry is updated with its observed effect, and the day's report notes the window instead of reporting a doubling.
Related terms and common confusions
Many log entries concern a Key EventA GA4 event marked as important to the business, the property's measure of success., the GA4 event marked as the property's measure of success, because changing what counts as one changes every conversion report. Tag changes often run through the Data LayerA structured object on a web page that passes values to a tag manager for tags to use., so a release that changes what the page passes to the tag manager is worth an entry even when no tag changed. Renaming campaigns or events under a new Naming ConventionAn agreed pattern for naming campaigns, ads, events and tracking parameters so that reports can group them reliably. breaks grouped reports unless the date of the switch is logged. And every BaselineAn estimate of what a metric would have done without a given change, campaign or promotion, against which the effect is measured. assumes that measurement stayed the same over the period it was built from, which only the log can confirm.
- A product changelog is the same thing. Public release notes for customers are a communication; the change log here is an internal record for explaining data and rules.
- Annotations inside the analytics tool are enough. The measurement tutorial treats marks in individual tools as copies; the log is the one source across systems.
- The log can be written up at month-end. Entries written later lose times, reasons and owners.
- Only big changes need entries. Small tag fixes and setting changes are often the ones that move figures unexpectedly.
- The log replaces the specification. It records when things changed; the tracking plan or guideline records what they became.
