Campaign Naming Standards
This page provides a recommended convention for naming campaigns in BaseQR. A consistent pattern makes campaigns easy to find, reduces duplicates, and aligns reports with analytics (for example, GA4 via utm_campaign). This is guidance, not a requirement.
Objectives
• Improve search and discovery in the Campaigns list.
• Enable clean rollups and comparisons in reports.
• Keep utm_campaign values aligned with campaign names.
Recommended pattern
Use lowercase, hyphen-separated values with a predictable order:
yyyy_qN_initiative[-channel][-region][-lang]
• yyyy_qN — Four-digit year and quarter (for example, 2025_q2).
• initiative — Short, descriptive slug (for example, eventseries, product_launch, grand_opening).
• channel (optional) — High-level channel or placement (for example, retail, print, dooh, email, social, web).
• region (optional) — Geographic scope (for example, us, ca, uk, eu, apac, emea).
• lang (optional) — Language code (for example, en, es, fr).
Examples
• 2025_q2_eventseries-retail-us-en
• 2025_q3_product_launch-print
• 2025_q4_holiday_email-us
• Evergreen alternative (no quarter): evergreen_store_signage-retail-us
Do’s and don’ts
Do
• Use lowercase and hyphens only (a–z, 0–9, -).
• Keep names concise (aim for ≤ 60 characters).
• Mirror the exact value in utm_campaign for clean reconciliation.
• Reuse the same initiative slug across channels to compare performance (for example, 2025_q2_eventseries-retail, 2025_q2_eventseries-dooh).
Don’t
• Avoid spaces, emojis, or punctuation other than hyphens.
• Avoid vague names (for example, new_campaign, test1).
• Avoid mid-flight renames; they create confusion during reviews and exports.
Using descriptions for context
Add operational detail to the campaign description so collaborators have the full picture:
• Goals and KPIs (scan target; GA4 conversion events).
• Locations and placements (for example, retail endcaps, shipping inserts, event signage).
• Audience/regions and UTM plan (summarize source/medium/campaign conventions).
Alignment with UTMs
• Set utm_campaign to the exact campaign name.
• Keep utm_source and utm_medium stable across codes to compare placements and channels.
• If you must change UTMs mid-campaign, keep utm_campaign unchanged.
Bulk operations
• Apply the naming standard before bulk creation to prevent duplicates.
• Use the Bulk Import Template (link placeholder) to create many codes under the correctly named campaign.
Quick checklist
• Name follows yyyy_qN_initiative[-channel][-region][-lang].
• Lowercase, hyphen-separated, ≤ 60 chars.
• Description includes goals, placements, audience/regions, and UTM plan.
• utm_campaign matches the campaign name exactly.