What is a bulk report edit?
A bulk report edit is one change applied across many reports at once, like swapping a retired metric, changing a date range or adding a new campaign type.
Ad platforms and analytics tools retire and rename things all the time, and every report that uses them has to follow. Your own standards change too: a new attribution model, a new date view, a new naming convention.
Here are some common reasons why you might need to bulk-edit your reports:
| Change | Example |
|---|---|
| A platform renames or retires a metric | GA4 now calls conversions key events |
| An attribution setting goes away | Meta stopped returning 7-day view and 28-day view attribution from January 12, 2026 |
| A whole data source stops | Universal Analytics stopped processing data on July 1, 2023 |
| Your attribution model changes | Last click to data-driven |
| The date view changes | Year to date to quarter to date |
| A new campaign type needs adding | Performance Max added to paid dashboards |
| A new look or naming convention | New brand theme, new report names |
The editing work itself isn't difficult at all, but it's just tedious, time-consuming, and frankly, frustrating to edit dozens of reports. Here's how one PPC lead at a UK agency agency described it:
"We had about 50 social reports and when I wanted to change the attribution model, it took me half a day to manually change everything."
Bulk edits are different from the monthly report update. For that, see automated client reporting.
How do agencies use AI agents to bulk edit reports in Whatagraph?
Agencies use an agent to find every report a change affects, make the change, and check each one went through. A human specialist checks the change and approves it before the agent edits across all reports. Here's how two teams do it.
An Irish ad-ops team: a new date range on every report
This team wanted every report in their space to show quarter to date instead of year to date. Doing it by hand meant opening each report and changing each widget.
They asked the agent to make the change. They tested it on one report, then on a second, and then applied it to every report in the space.
"I applied the first test on the first report, checked that one, made sure that it is correctly what I was looking for, did it again on a second test, and then I applied that change on every single report I have on my space, and that was successfully done."
An in-house marketing team: 38 reports with the wrong setting
This team's online shop reports showed sessions by day, when they needed them by month. The setting sat inside one widget on each report, across many markets.
Whatagraph's bulk-edit agent, Sweep, searched every report and found all 38 that used the day setting. It named the exact widget on each one and proposed changing it to month. Before changing anything, it took a snapshot so every report could be restored.
Manual vs. agent bulk edits
The safest combination agencies we talked to implement is a combination of both. Here's how the workflow typically looks like.
- The specialist prompts an agent to find affected reports for a change they want to make.
- The agent finds them, the specialist reviews, and asks it to apply the change to one report first.
- The agent does that, the specialist reviews, and once they're satisfied, asks the agent to apply the change across all affected reports.
Here are more details of how the work compares completely manual, templated, and with agents:
| By hand | Templates | AI agent + specialist | |
|---|---|---|---|
| Finding affected reports | Open each one and look | Only helps with new reports | Sweep lists every report and widget |
| Time for 50 reports | Hours, often half a day | No help for reports already built | One pass, plus your check |
| Risk of missing one | High | High for older reports | Low, because every hit is listed |
| Undo | Change it back by hand | Change it back by hand | Restore from a snapshot |
| Who checks | Whoever did the edit | Whoever did the edit | A person reviews the list and the first report |
For a wider look at the options, see our roundup of automated reporting tools.
How to bulk edit reports with an AI agent
The safe way to run a bulk edit is list, check, test, then apply. Here's how to set it up with Whatagraph IQ Agent: Sweep.
1. Describe the change in plain words. Say what to find, what to change it to, and which reports. For example: every widget in the client folder that uses 7-day view attribution.
2. Ask for the list first. Sweep lists every report and widget the change affects, and changes nothing yet.
3. Check the list. Take out any report that should stay as it is. You can't lock specific reports away from an agent in the settings today, so name the ones to skip in the brief.
4. Apply it to one report and check it. Open it and compare it with what you expected.
5. Apply it to the rest. Sweep makes the change and checks that each edit went through.
6. Keep the snapshots until you're sure. If a client spots something off next week, you can roll that report back.
Paste this brief, or describe the change to IQ Agent in your own words:
Find every report in [client folder or list] that uses [metric, setting or source].
For each one, list the report, the tab and the widget. Don't change anything yet.
Tell me which metric or setting you'd use instead: [metric A] was retired and replaced with [metric B]. If you're not sure which replacement fits a widget, ask. Don't guess.
Skip these reports: [report names].
After I confirm the list, take a snapshot, then make the change on [first report] only.
After I confirm that report, make the change on the rest. Then list any widget you couldn't change and why.
To be completely on the safe side, the brief asks for a change report before the agent touches reports: what was retired, what replaces it, and where.
Bulk-edits go even faster with Whatagraph's linked reports, where you have one "master" report and a collection of reports tied to it. The agent only needs to edit the master report once, and changes are automatically applied to all the reports tied to it. This saves time and tokens as the agent wouldn't need to edit every individual report.
What are the benefits of bulk editing reports with an AI agent?
✅ Hours back on every platform change. Half a day of clicking becomes a list to check and a change to approve.
✅ No report missed. Sweep lists every widget the change affects, including the old reports nobody opens.
✅ The same metric everywhere. Every client report uses the same definition after the change.
✅ A list before anything changes. You see exactly what will change, and where, before you approve it.
✅ An undo for every report. Snapshots let you restore a report if something looks wrong later.
✅ Faster reaction to platform changes. When a platform retires a metric, you can fix every report the same week, not when a client asks.
Best practices for bulk report edits
A few habits keep bulk edits safe:
- Ask for the list before any change. Read it before you approve anything.
- Check one report first. Then apply the change to the rest.
- Keep "needs approval" on for report and widget edits until you trust the agent with that kind of change.
- Snapshot before every bulk edit. Keep the snapshots until the next reporting cycle has gone out.
- Write the change down. Note what changed, why and which reports. The next person to touch those reports will need it.
- React to platform changes early. When a platform announces a retired metric, fix your reports before the date, not after a client spots a gap.
- Keep bulk edits with the people who own the reports. Agree who's allowed to run them, and name the reports to skip in every brief.
For the tools that help run a reporting operation at this scale, see our guide to client reporting tools.
What common mistakes to avoid in bulk report edits?
1. Changing everything at once
A change that looks right in your head can look wrong in a real report. Apply it to one report, check it, then apply it to the rest.
2. Letting the agent pick the replacement
When a metric is retired, the right replacement isn't always obvious. Tell the agent which metric replaces which, and ask it to stop and ask when it isn't sure.
3. Forgetting reports outside the folder
Old reports, one-off client dashboards and reports in other folders use the same metric too. Ask the agent to search every folder you're responsible for, not only the obvious one.
4. Skipping the snapshot
Without a snapshot, undoing a bulk edit means fixing each report by hand. Take one every time.
5. Letting anyone run bulk edits
In a big team, an accidental bulk edit is the fear agencies raise most. Keep edits on "needs approval", agree who runs them, and name any report that should stay as it is in the brief.
6. Mixing a bulk edit with a client request
A change for one client doesn't belong in a change for all of them. Run them separately, so a client-specific tweak doesn't end up everywhere.
