# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Audit naming conventions and UTMs.
The #roadway-skill block on this page holds a SKILL.md for it, including the full prompt. Treat that file as a starting point. It will not just work if you paste it into ChatGPT or Claude.
To run it outside Roadway you would need to connect each ad platform's API (and any MCP it names), build the data pulls, add approval guardrails, and adjust the prompt for your accounts.
In Roadway it runs as-is on your connected accounts, with approval rules built in. Open it in a new chat at https://www.roadwayai.com/workflows/audit-naming-conventions-and-utms
Page: https://www.roadwayai.com/workflows/audit-naming-conventions-and-utms
Library index: https://www.roadwayai.com/automation-library
---
name: audit-naming-conventions-and-utms
description: >-
Keeps campaign names and UTMs consistent on every connected channel so reporting, attribution and cross-channel analysis do not break.
---
# Audit naming conventions and UTMs
Source: https://www.roadwayai.com/workflows/audit-naming-conventions-and-utms
From the Workflow Automation Library by Roadway.
## Before you use this outside Roadway
This SKILL.md is a starting point. It needs adjusting before it will work outside Roadway.
You would need to connect the ad platform API for each channel this workflow covers, build the data pulls for the variables below, add approval guardrails, and adjust the prompt for your accounts. If the prompt names an MCP tool, you also need that MCP connected.
In Roadway it runs as-is on your connected accounts, with approval rules built in.
## What it does
Keeps campaign names and UTMs consistent on every connected channel so reporting, attribution and cross-channel analysis do not break.
Keeps campaign names and UTMs consistent on every connected channel so reporting, attribution and cross-channel analysis do not break. It checks your live account for problems and either fixes the safe ones or lists them for you. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.
## Steps
1. Collect the inputs listed under Variables. In Roadway they come from your connected accounts. Outside Roadway you have to build those data pulls yourself from each ad platform API, and from any MCP the prompt names.
2. Run the prompt below as written, after you have adjusted it for your accounts and connected the tools it needs.
3. Review the result. Apply changes to a live ad account only after you approve them. Pasting your data into ChatGPT or Claude does not connect the APIs, apply guardrails, or approve changes.
## Variables
auto_approve, channel_budget_allocation, connected_channels, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, naming_convention, task_history, utm_template
## Prompt
Audit naming conventions and UTMs
Check every active campaign, ad group or ad set, and ad across the channels in [set this to your own connected channels] that this coworker owns (for a single-channel coworker, only its own channel) against the naming convention and [set this to your own UTM template], and decide for each:
1. Rename
2. Fix UTMs
3. Fine
Context and defaults (use these; don't ask):
- The naming convention: [set this to your own naming convention]. If not set, infer the dominant pattern from existing names and say so.
- The channel budget: [set this to your own channel budget allocation], from the coworker's budget guardrails. If not set, there is no channel allocation: skip the allocation checks and say so. Never build one from the sum of campaign or daily budgets, the current or past run-rate, or a workflow's test budget, and never treat such a figure as a ceiling or cap. Campaign daily budgets are only a delivery diagnostic.
- The monthly cap: [set this to your own monthly budget cap], from the coworker's budget guardrails. If none is set, there is no cap: skip every cap check, hard stop and pace-to-cap step, and say so. Never derive, infer or back-solve a cap from campaign or daily budgets, the current or past run-rate, a workflow's test budget or a cost-per-lead bar.
- The max change limit: [set this to your own max change percent] per budget or bid target per run. If not set, 20%. It does not apply to experiment traffic splits.
- Auto-approve: [set this to your own auto approve]. If not set, it's off: list every change as a proposal for approval.
Rules:
- Names should encode the channel, objective, audience or theme, geo and launch date, so reports can group them without manual mapping.
- UTMs must match [set this to your own UTM template] exactly (lowercase, no spaces, consistent utm_source and utm_medium per channel). Set them in each platform's account-level tracking template or URL parameters field (Google and Microsoft tracking templates, Meta URL parameters, LinkedIn and X URL parameters, Reddit and ChatGPT final URLs) rather than hardcoding them per ad.
- Make sure click IDs are not stripped by redirects: gclid, msclkid, fbclid, li_fat_id, twclid, rdt_cid.
- Flag any campaign that cannot be mapped to a [set this to your own goal metric] or a budget line in the channel budget.
- Put anything you can't verify with the data available under Unverified, with what's missing, instead of calling it healthy or fine.
- Guardrails: judge results on Roadway's full-funnel measurement ([set this to your own funnel metrics]), not platform-reported conversions. Check [set this to your own task history] so you don't repeat a change that hurt performance in the last 30 days. Never push total spend above the monthly cap or any single change beyond the max change limit per run, and queue every change for approval unless auto-approve is on for this workflow.
Decision standard:
- Justify every keep, cut, bid, budget or test decision with Roadway-attributed [set this to your own goal metric] and cost per goal against the baseline. Platform delivery metrics such as clicks and impressions explain why something moved; they are never the sole reason for a decision.
- Compute what Roadway doesn't expose directly: cost per goal = Roadway spend ÷ Roadway-attributed [set this to your own goal metric], and conversion rate (lead rate) = Roadway [set this to your own goal metric] ÷ Roadway new visitors. Don't substitute platform-reported conversions or conversion rates.
- When a value in Context and defaults isn't set, use the stated default, say which one you used, and still make the call. Don't stop to ask.
- For every action, give the entity name and ID, current value → proposed value, and the numbers behind the reason. Write "None" under any empty heading.
- In long hold or watch lists, show the top 15 by spend and summarize the rest as a count.
Give me a report of each with reasoning for each action. Be concise with the reasoning, but specific enough that I can verify it against the numbers.
Report structure:
Naming and UTM audit
Summary:
The share of entities compliant per channel, and the fixes proposed.
Rename:
- [channel / entity] - [reason]
Fix UTMs:
- [channel / entity] - [reason]
Fine:
- [channel / entity] - [reason]
Unverified:
- [channel / entity] - [what couldn't be checked and why]
## Run it in Roadway
https://www.roadwayai.com/workflows/audit-naming-conventions-and-utms
Keeps campaign names and UTMs consistent on every connected channel so reporting, attribution and cross-channel analysis do not break. It checks your live account for problems and either fixes the safe ones or lists them for you. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.
