# Prepare a campaign tracking plan with UTM conventions

**trustWF workflow pack** · Marketing

## Outcome
A naming convention, tagged-link inventory template, KPI dictionary, and pre-launch QA checklist.

## Who this is for
A digital marketer or small team setting up consistent campaign links and measurement

## What to provide
Required: campaign name, channels, content variants, destination URLs, analytics platform conventions, and reporting period. Optional: existing naming rules and conversion events. Never paste credentials or private analytics exports.

## Steps
1. Inspect existing naming rules and event definitions; preserve any established conventions.
2. Define allowed values for source, medium, campaign, content, and term fields where relevant.
3. Map each planned link to a destination and intended measurement without altering the destination.
4. Create a launch QA checklist and note analytics configuration that a human must confirm.

## Copy-ready instructions
STAGE 1 — 1. Gather the measurement rules
When to use: Use before naming links.
Prompt: Help me make a campaign tagging plan. Campaign and dates: [details]. Channels: [list]. Destination URLs: [paste approved URLs]. Creative or audience variants: [list]. Existing UTM or analytics naming rules: [paste or “unknown”]. Analytics platform and defined conversion events: [details or “unknown”]. First identify naming conflicts and missing configuration. Do not create new conversion events as if they already exist.
Expected return: An inventory of planned links and a list of existing rules to preserve or confirm.
User check: Confirm every destination is approved and remove private parameters, identifiers, and tokens.

STAGE 2 — 2. Set naming conventions
When to use: Use after confirming existing rules.
Prompt: Based on the confirmed rules, propose a consistent convention for utm_source, utm_medium, utm_campaign, and optional utm_content/utm_term. Use lowercase, stable separators, and a short controlled vocabulary. Provide examples using only the campaign and channel details supplied. Mark any proposed values as recommendations pending analytics-owner approval. Do not include names, email addresses, customer IDs, or sensitive targeting terms in URLs.
Expected return: A concise naming standard plus a link matrix with each approved destination and proposed tags.
User check: Check spelling, consistency, duplicate tags, URL encoding, and privacy risk.

STAGE 3 — 3. Prepare launch QA
When to use: Use after a human approves the naming standard.
Prompt: Create a pre-launch checklist for this link matrix: [paste approved matrix]. Include checks for destination loading, redirect behavior, tag preservation, correct channel/source values, analytics property, conversion-event availability, and a test visit where permitted. Separate checks the user can perform from those requiring an analytics administrator. Do not state that any tracking is working until observed.
Expected return: A link-by-link QA checklist and reporting table template.
User check: Have an analytics owner confirm events and reporting before launch; do not share tagged links until tested.

## Review before using
Do not invent analytics events or claim tracking is installed. Check that tags contain no personal data, secrets, or sensitive audience details; confirm redirects and platform-specific rules.

---
Use the result as a draft. Review it for accuracy, context and any required approvals.