Marketing change log: what it is and how to keep one

Why does a marketing team need a change log?

Most metric shifts have a cause inside the team: a budget cut, a new landing page, a tag that fires twice, a consent banner update or a new form field in the CRM. The problem is that those changes live in different places.

• Google Ads keeps its own change history, for people with access to that account.
• Meta Ads keeps an activity history, with its own format and filters.
• GTM keeps versions, your CMS keeps revisions, your CRM may keep an audit log.
• The reason behind each change usually lives only in someone's head or in a chat thread.

A change log puts the what, when, who and why of every channel in one place. It is the first thing to open when a client asks why conversions fell, and the fastest way for a new team member to learn an account's history.

What should you log?

Log anything that can move a number you report on. Skip changes that can't.

External events belong in the log too: a competitor sale, a holiday, a platform outage, press coverage. They explain shifts no one on the team caused.

Which fields does a good change log entry need?

Four fields are required, four are optional. Keeping the required set small is what keeps people logging.

1. Date (and time, if two changes can happen on the same day).
2. Title: short and specific. “PMax budget +20%”, not “Budget update”.
3. Channel or tag: Google Ads, Meta Ads, Website, Tracking, CRM, Product, Other.
4. Owner: who made the change.
5. Why: the reason, in one sentence. This is the field platform histories never have.
6. Expected impact: what should happen, and when you will check.
7. Link: to the ticket, the GTM version, the ad or the page.
8. Result: filled in later, when you know.

A ready-to-copy version is in our free marketing change log template.

How do you use a change log to explain a metric shift?

1. Find the date the metric moved. Use daily data, not weekly averages.
2. Open the log for the 1 to 14 days before it. Paid media changes can act the same day; SEO and CRM changes take longer.
3. Shortlist changes that touch the metric's path. A conversion drop points to landing pages, tracking, destinations and forms first.
4. Check tracking before performance. A metric that fell to zero overnight is usually a tag, not a campaign.
5. Confirm with the platform's own history and segment the data to test the theory.
6. Write the result back into the log, so the next person learns from it.

We cover the client conversation itself in how to explain a conversion drop to a client.

Isn’t the native history in each platform enough?

Native histories are useful for the details of one platform, and you should keep using them. They fall short as a team record for four reasons:

• They are siloed. Each shows only its own changes, so you can't see a landing page release next to a budget change.
• They lack the why. They record that something changed, not the reason or the expected result.
• They have limits. Google Ads change history covers the past 2 years; Meta does not publish a fixed retention period for its activity history.
• Access is per platform. A client or a new analyst often can't see them at all.

GA4 annotations help, but they are capped at 1,000 per property and at 150 characters of description, and they only live inside that one property.

Spreadsheet or dedicated tool?

A spreadsheet is a fine way to start, and our template works in Google Sheets or Excel. Teams usually move to a dedicated tool when:

• they manage several clients and need one log per client with the right people in each;
• they want to see changes on a real time axis, next to each other, instead of scrolling rows;
• clients should read the log without being able to edit it;
• they need an edit history they can trust.

Changeline is built for exactly that: one to-scale timeline per client, tags per channel, owner/editor/viewer roles and a full edit history. Automatic import from Google Ads and Meta Ads is coming soon.

How do you get a team to actually keep the log?

• Log at the moment of change, not at the end of the week. It takes seconds when the context is fresh.
• Keep required fields to four. Every extra required field lowers compliance.
• Make it part of the checklist for launches, GTM publishes and budget changes.
• Use it in every review. A log people read gets updated; a log no one reads dies.
• Backfill the last 30 days on day one, so the log is useful immediately.