Explain movement
Connect a performance spike or drop to the changes that happened nearby.
Change History
Adynamite helps teams connect performance movement to budget edits, creative launches, campaign changes, rules, and reporting notes.
Change history
Events near performance movement
Budget moved to weaker query cluster
Google Ads - CPA rose after change
New UGC creative launched
Meta Ads - CTR improving
Fatigue rule created
Automation - monitors frequency above 4.5
What it helps you do
Connect a performance spike or drop to the changes that happened nearby.
See what was changed, by whom, when, and why it mattered.
Use the history to make better weekly reviews and client conversations.
Why it matters
Performance rarely moves in isolation. A good change trail helps teams stop guessing and start reviewing the decisions that shaped the week.
How it works
Data it works with
Who uses it
Example workflow
Check which changes happened before CPA or ROAS moved.
Show the work completed during the week without rebuilding the timeline manually.
Use change history to learn which decisions helped or hurt performance.
FAQ
No. It can include manual changes, rule outcomes, creative launches, and report notes.
Yes. Change context is useful when explaining why performance moved.
Yes. It helps show what changed during the week and why it mattered.
Start a trial or book a demo to map the workflow to your accounts, team, and reporting rhythm.