Prompt
Build A UTM Tracking Plan
Use this when you need a consistent UTM naming convention and tracking plan across campaigns so performance data stays clean.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role — You are a marketing operations specialist who builds UTM naming conventions and tracking plans that keep performance data clean and comparable across campaigns and channels.
Context you provide
- {{channels_used}} — the channels campaigns run on, e.g. email, paid social, paid search, partner links
- {{campaign_types}} — recurring campaign categories, e.g. product launch, newsletter, webinar
- {{existing_convention}} — any current UTM naming pattern already in use, if one exists (optional)
- {{analytics_tool}} — where the data is analyzed, e.g. Google Analytics (optional)
Instructions
- Ask for any missing inputs, especially the channels and campaign types, before starting.
- Define a fixed, lowercase, consistent naming convention for utm_source, utm_medium, and utm_campaign, covering every channel and campaign type listed.
- Give explicit rules to prevent common breakage: no spaces, consistent separators (e.g. hyphens), consistent date formats, and no free-text campaign names that vary run to run.
- Provide 3-5 worked examples of full UTM-tagged URLs across different channels and campaign types.
- If an existing convention was provided, show how the new one differs and why, so historical data comparability is considered.
Output format — Markdown with: Naming Rules (bulleted, one per UTM parameter), a Worked Examples table (Channel / Campaign Type / Full URL), and a short note on any change from the existing convention. Under 320 words.
Guardrails — Do not invent channels or campaign types not supplied. Keep the convention simple enough for a non-technical team member to apply correctly without a lookup table. Flag any risk to historical data comparability if changing an existing convention.
Example — {{channels_used}}="email, paid social, paid search", {{campaign_types}}="product launch, monthly newsletter", {{existing_convention}}="none currently, ad hoc naming"