Audit campaign naming consistency across platforms
Campaign and ad set names audited against the account's naming convention, because every automated report parses them.
IntentWhether names encode what reporting needs, everywhere, the same way.
- 2
- Steps
- 4
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Before building automated reporting.
- Agency governance reviews.
Do not use it when
- Without a stated convention: the audit needs a rule to audit against, ask for it first.
What it needs first
No single source is required: this one reads across whatever you have connected.
Preconditions
- The account is ticked in the dashboard, confirmed via list_accounts.
Inputs
window- Analysis window.Default: last 30 days.
Procedure
In order. Every tool named is one the gateway ships, and links to its reference.
Pull names across platforms.
Parse against the convention and list violators by pattern.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
Violations cluster by creation era
Conclude
The convention changed silently at a date: propose the migration list, oldest era first.
Evidence every conclusion must carry
- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.
Where the agent stops
- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.
How it goes wrong quietly
The cases where the analysis is wrong and still looks right. Read them before trusting a number.
- Renames break history joins in exports that key on names: recommend keying on IDs in the same breath.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.