Salesforce Marketing Cloud Campaign Naming Best Practices

Why SFMC naming is different

Salesforce Marketing Cloud sits at the intersection of email, SMS, push, and journey data. Unlike display campaigns where a bad name just breaks a report, a bad SFMC name can corrupt journey analytics, break SQL queries in Analytics Builder, and make your Data Extensions unmanageable overnight.

The problem compounds quickly. SFMC doesn't have a native naming enforcer. You can name a campaign anything you like, and the platform will happily accept it. That means the discipline has to come from your team — which means it has to be documented, trained, and audited.

The recommended structure

A solid SFMC naming convention covers three layers: the campaign, the email send, and the journey. Each has slightly different needs.

Campaign level:

Brand_JourneyType_Audience_YYYYMMDD

Example:

Acme_Welcome_NewSubscribers_20260401
Acme_Winback_LapsedQ1_20260401

Email send level:

Brand_JourneyName_EmailType_VersionLetter_YYYYMMDD

Example:

Acme_Welcome_Nurture_v1_20260401
Acme_Welcome_Nurture_v2_20260415

Journey name:

Brand_JourneyPurpose_Audience_StartDate

Example:

Acme_PostPurchase_AllBuyers_20260401

The segments that matter most

Brand — always first. This matters more than it sounds. If your SFMC instance serves multiple brands or business units, omitting this creates immediate reporting chaos. Even single-brand teams should include it as a future-proofing measure.

JourneyType or Purpose — Welcome, Winback, PostPurchase, Promotional, Transactional. Keep this vocabulary controlled. Don't let "Onboarding" and "Welcome" coexist for the same workflow.

Audience segment — be specific but consistent. NewSubscribers, LapsedQ1, HighValueDonors. Avoid vague labels like All or List1. The audience name should appear in your Data Extension name too, making cross-referencing straightforward.

Date — always YYYYMMDD. This makes campaigns sortable in both the SFMC interface and downstream SQL queries. Avoid April2026, Apr26, or any format that requires human interpretation.

Version letter — for A/B tests and email iterations, append _vA, _vB, or _v1, _v2. This is critical for SFMC A/B tests where both variants need names that make the comparison obvious in reporting.

Common mistakes I see in the wild

Using spaces. SFMC's interface allows spaces, so people use them. The moment you try to query that send name via API or reference it in AMPscript, you're escaping strings. Use underscores.

Mixing naming styles mid-journey. A journey that starts as Acme_Welcome_v1 and ends as ACME welcome email - final tells me three different people built it. Consistency within a journey is non-negotiable.

Skipping the date on evergreen campaigns. "But it runs forever — why does it need a date?" Because when you clone it in two years and forget to update the journey name, you'll have two identically-named journeys and no way to tell which data belongs to which.

Using customer-facing language as internal identifiers. The subject line "Your exclusive offer is waiting" is not a campaign name. Your campaign name is internal. Keep them separate.

Enforcing the convention at scale

Document the convention in your internal wiki and link to it from every SFMC business unit. Add a campaign naming check to your launch checklist — ideally an automated one.

The most effective teams I've seen do three things:

1. Maintain a controlled vocabulary document for allowed values in each segment
2. Review all campaign names in a weekly ops sync before activation
3. Run a quarterly audit of existing assets and rename anything non-compliant

Automation makes this sustainable. Manually checking 40 email sends before each campaign launch isn't realistic.

---

Want to automate your SFMC naming audits? AdOps Auditor checks your campaign names against your SFMC convention in seconds — paste a list, get a compliance score and plain-English fix suggestions instantly.