What is automated changes attributed to "system"?
Both Google Ads' Change History and Meta's equivalent change log can show edits attributed to a generic "system" or "Google Ads" actor instead of a named team member. This happens because automated bidding, auto-apply recommendations, and other platform-side automation make their own micro-adjustments to bids, budgets, or targeting on your behalf, and those changes get logged the same way a human edit would. Anyone auditing the log to reconstruct "what did we change vs what happened on its own" needs to know this distinction exists, or they'll misattribute automated moves as deliberate decisions, or the reverse.
Ad platforms log changes to give advertisers an audit trail: what changed, when, and who did it. But "who" isn't always a person. Google Ads' Change History records automated bid adjustments made by Smart Bidding strategies, and separately logs changes applied automatically when an advertiser has auto-apply turned on for certain recommendations, both under a system-level actor rather than a named user. Meta's account-level change log behaves similarly for automated actions taken by its delivery and optimization systems.
This matters most during a post-mortem or a handover. If an agency, a founder, or a new team member is trying to reconstruct why a budget or targeting setting looks different than expected, scanning a change log that mixes human edits and system edits under similarly generic labels can lead to two mirrored mistakes: crediting a deliberate strategic call to "the algorithm just did it," or, worse, assuming an automated adjustment was a team decision and building a narrative or a fix around a choice nobody actually made. Knowing that "system"-attributed entries exist as a normal, documented category (not a bug or a mystery) is the first step to reading the log correctly.