HueLifeCMO Knowledge Base

Campaign Categories & Naming Conventions

Grounded in the 10 live campaigns exported 2026-06-10. Goal: every campaign sortable and filterable by year → program → type without opening it.

Principle: the name carries the structure; HubSpot fields carry the metadata.


What's wrong today (from the real export)

ProblemEvidence
4 different delimitersBook Launch (space), Leadership_Retreats (underscore), TSoI Recruitment - March 2025 (dash), BostonTSPCourse (none)
Year placement inconsistent…2026, …2025, March 2025, or missing entirely
Redundant words"Recruitment Campaign", "AMC Conference" (it's all campaigns)
Channel/source baked into nameGeneral Interest - Email Signature Clicks
Status never setAll 10 campaigns have blank status
Ownership gaps2 have no owner; 2 owned by Flower Krutina (Deactivated User)
Audience is freeform prose"Different leaders and facilitators who are interested in…" vs TFM graduates

The good news: your campaigns naturally fall into 4 types built around a handful of programs — so the taxonomy is small.


The naming convention

YYYY_PROGRAM_TYPE_Descriptor
FieldRequiredValuesExample
YYYYyesCohort/launch year, or EVG for evergreen/always-on2026
PROGRAMyesControlled program code (below)MTOP
TYPEyesRECRUIT / EVENT / LAUNCH / NURTURE / BRANDRECRUIT
DescriptoroptionalLocation, month, or edition — Title-Case, hyphen-joinedBoston

Rules: underscores _ separate fields; hyphens - join words inside a field. No channel in the name (channel lives on the asset). Drop filler words like "Campaign." One program per campaign.

PROGRAM codes (your actual programs)

CodeProgram
MTOPMastering the Technology of Participation
TSPToP Strategic Planning
TSOITSoI
TFMTFM
YOULEADYouLEAD
RETREATLeadership Retreats
AMCAMC Conference (external event)
HUELIFEOrg-wide / brand / cross-program

TYPE codes

CodeUse for
RECRUITCourse/cohort recruitment (the bulk of your campaigns)
EVENTConferences, in-person events, retreats, summits
LAUNCHBook/product/program launches
NURTUREAlways-on lifecycle journeys
BRANDGeneral awareness / thought leadership

Rename map for all 10 campaigns

Current name→ New name
MToP 2026 Recruitment Campaign2026_MTOP_RECRUIT
MToP 2025 Recruitment Campaign2025_MTOP_RECRUIT
TSoI Recruitment - March 20252025_TSOI_RECRUIT_Mar
BostonTSPCourse2025_TSP_RECRUIT_Boston
Leadership_Retreats2025_RETREAT_RECRUIT
YouLEAD 20262026_YOULEAD_EVENT
AMC Conference 20242024_AMC_EVENT
Book Launch2026_HUELIFE_LAUNCH_Book
Nurture - Course InterestEVG_HUELIFE_NURTURE_Course-Interest
General Interest - Email Signature ClicksEVG_HUELIFE_NURTURE_Email-Signature

Sorted, this groups 2025_MTOP next to 2026_MTOP, all RECRUIT campaigns together, and pushes evergreen (EVG_) to the bottom — exactly the at-a-glance order you want.


Don't put it in the name — put it in HubSpot fields

These already exist as campaign properties; you're just not using them. Filling them is half the cleanup:


Email naming rule (assets inside a campaign)

Emails inherit the campaign name, then add their order and purpose:

{CampaignName}_EM##_Descriptor[_vA]
PartMeaningExample
{CampaignName}The parent campaign's name, verbatim2026_MTOP_RECRUIT
EM##Send order in the campaign (zero-padded)EM01, EM07
DescriptorPurpose — Title-Case, hyphen-joinedInvite, Reminder, Last-Call
_vA / _vBOptional, A/B test variants only_vA

Examples (MToP recruitment has 7 emails):

2026_MTOP_RECRUIT_EM01_Invite
2026_MTOP_RECRUIT_EM02_Reminder
2026_MTOP_RECRUIT_EM07_Last-Call
2025_TSP_RECRUIT_Boston_EM01_Invite_vA

This makes every email self-identify its campaign, its place in the sequence, and its job — and emails sort in send order under their campaign.


Migration checklist

  1. Lock the PROGRAM + TYPE code lists above.
  2. Rename all 10 per the map (HubSpot keeps the same Campaign ID / UTM, so reporting history is preserved — names are cosmetic).
  3. Set status on all 10.
  4. Reassign the 4 ownerless/deactivated-owner campaigns to a live owner.
  5. Standardize the audience tag.
  6. Gate new campaigns: no campaign goes live without a conforming name + owner + status.

Renaming is safe — the Campaign UTM (44806480-YouLEAD%202026, etc.) is keyed to the Campaign ID, not the name, so existing tracking and analytics stay intact.