Marketing change report: how to show what changed in a period and why

What is a marketing change report?

A marketing change report is the “what we changed” half of a review: a dated list of the edits made to campaigns, budgets, creatives, the website, tracking and the CRM during one period. The performance report says what moved; the change report says what could have moved it.

Most teams already have the raw material. Google Ads keeps a change history, GA4 keeps a property change history, and your developers ship releases with dates. What is missing is one place where those changes sit together, in the same period as the metrics, written so a client or a manager can read them.

The report is a summary of a marketing change log: the log is the running record, the report is the slice of it for a given week, month or incident.

• Agencies use it as the “work done and why” page of the monthly client report.
• In-house teams use it in weekly performance reviews and after any sudden drop or spike.
• Analysts use it to rule changes in or out before blaming seasonality or tracking.

What should a marketing change report include?

A useful marketing change report answers five questions for the period: how many changes, of what kind, where, by whom, and which ones matter. Build it in this order.

1. Period and headline count. The exact dates (with time zone) and the total number of changes, so the reader knows the scale.
2. Split by kind. Investment (budgets, bids), campaigns (structure, bidding strategy, targeting), creatives and audiences, tracking and site, product/CRM/other, and account incidents (disapprovals, payment holds, outages).
3. Split by platform or source. Google Ads, Meta Ads, website, tracking, CRM, and changes logged by hand.
4. Highlights. Three to five changes that most likely affect results, each with the expected effect in one line.
5. Detail. One row per change: date, owner, platform, item, before → after, reason.

Example of the detail table (illustrative values, not real data):

The reason column is what turns a log into a report. Without it, the reader sees activity; with it, they see decisions.

Where do the changes for the report come from?

Pull each platform's own history first, then add what no platform records. The table shows what each source gives you and its limits, as documented by Google.

In Google Ads, the Change history page has “By user”, “By campaign” and “Performance” tabs, and the “Tool” filter separates edits made in the interface from those made by automated rules, the API or Google Ads Editor. That split matters in a report, because “we changed it” and “a rule or a tool changed it” lead to different conversations.

For Meta, use the account's activity history, as explained in our Meta Ads activity history guide.

How do I build a marketing change report step by step?

Use the same period as the performance report, collect changes from every source into one list, remove the noise and write the highlights last.

1. Fix the period. Same start and end dates as the metrics you will show, in the account time zone.
2. Collect. Google Ads change history, Meta activity history, GA4 property change history and annotations, the release notes from the website team, CRM workflow edits and any offline events (price changes, stock-outs, promotions).
3. Normalise. One row per change with the same columns: date, owner, platform, item, before → after, reason.
4. Collapse noise. A bulk edit of 300 keywords is one line (“paused 300 low-quality keywords in Generic”), not 300.
5. Group by kind and platform and count each group.
6. Write three to five highlights with the expected effect: “budget +47% on Brand, expect more brand clicks at similar CPC”.
7. Place it next to the metrics so each highlight can be read against the chart for the same days.

If your changes are already on one timeline, most of this is done for you. In Changeline, the Report button on a project builds a two-page change report for the last 7, 14 or 30 days or two dates you choose: the count, the split by group and by platform, editable highlights and the detail with dates and before/after values, saved as PDF from the browser.

How do I use the report to find what caused a change in results?

Put every change from the days before the shift on one timeline, rule out tracking first, then test one hypothesis at a time. The change report is the input for that check, so build it before you start guessing.

1. Mark the day the metric moved and list every change from the 7–14 days before it, across all platforms, including automated ones.
2. Rule out tracking. Look for tag, consent, conversion action or GA4 admin changes first. If conversions fell but sales in the CRM did not, it is a measurement problem, not a performance one.
3. Separate your edits from automation. Use the “Tool” filter in Google Ads to see what rules, scripts or recommendations changed.
4. Check outside events: site releases, price changes, stock, holidays, competitor promotions.
5. Test one hypothesis at a time, starting with the change closest in time and largest in scope, and look for the same pattern in the affected campaigns only.

Example: conversions drop 30% from 10 September. The report shows a purchase tag moved on 9 September and a budget increase on 3 September. The tag change is one day before the drop and touches every conversion, so it is checked first. CRM orders are flat, which confirms a tracking cause. This is an illustrative case, not client data.

Google Ads edits can be imported into Changeline automatically through a read-only connection; site, tracking and CRM changes are logged by the team. For a fuller method, see why conversions drop and how to find the cause and how to measure the impact of a change.

What mistakes make a change report useless?

Most change reports fail because they list activity without context. These are the common problems and the fix for each.

• Noise. Hundreds of keyword-level rows hide the five changes that matter. Collapse bulk edits and lead with highlights.
• Missing dates or time zone. “Early September” cannot be matched to a chart. Use exact dates in the account time zone.
• No before and after. “Budget changed” says nothing; “$150 → $220” does.
• No reason. Without the why, the client cannot judge the decision and you cannot judge it later.
• One platform only. A report built only from Google Ads misses the site release that caused the drop.
• Waiting too long. The Google Ads API only returns 30 days of change events and most interface changes can only be undone within 30 days, so collect while the details are fresh.

How often should you send a change report, and to whom?

Send it on the same rhythm as the performance review it explains: weekly for the internal team, monthly for clients and managers, and ad hoc after any incident.

• Weekly, internal: the full detail, so the team knows what was touched and avoids overlapping tests.
• Monthly, client or manager: count, groups and highlights on the first page, detail as an appendix.
• After an incident: only the changes from the days before the shift, with the hypothesis being tested.
• Quarterly or yearly: compare the same weeks year over year to see which changes you repeat every season.

To keep the source list tidy between reports, start from a marketing change log template. When the report has to explain a bad month, the guide on how to explain a conversion drop to a client shows how to present it.