Audit log: who did what, when and from where
When a client asks “who changed this?”, the audit log answers in seconds. It records every meaningful action in the workspace with its author, time and origin.
What it does
The log covers change proposals, approvals and rejections, executions and undos, campaign and ad creations, connection checks and disconnections, policy and limit changes, Tag Manager publications and rollbacks, GA4 setup steps, team changes, API keys and more. Actions by the AI analyst, MCP clients, agents and automations are marked with their origin.
Entries cannot be edited by application roles, and data is isolated per workspace. The log is a chronological feed; each entry expands to technical details shown without secrets.
Why it helps
- Full accountability for clients and management.
- Faster incident investigation.
- Evidence of process for audits and reviews.
How to set it up
- Open “Audit log” in the menu.
- Scroll the chronology or refresh it to see the latest events.
- Expand an entry to see its details.
Good to know
- Secrets and tokens are never written to the log.
- The log is part of the workspace data and follows its access rules.



Try it on your own accounts
Create a workspace, connect Google or Meta in a couple of clicks and see your accounts clearly. Changes follow your approvals or the policy you configure.
Create your workspace