Campaign Naming Convention

A campaign naming convention is the structured rule for labelling campaigns in Amazon Advertising so the account is filterable, reportable, and legible. It is the single non-glamorous discipline that determines whether a 200-campaign account is operationally tractable or operationally chaotic.

A naming convention costs nothing to implement and has compounding returns. An account without one accumulates dead campaigns, mislabelled tests, and untrackable spend with no way to filter them out short of clicking through every campaign individually.

The canonical pattern

[Format] - [Brand] - [SKU/Theme] - [Targeting] - [Match Type] - [Role]

Example: SP - Amalyze - WB-500ML - Manual - Exact - Harvested

Decoded:

• SP — Sponsored Products (alternatives: SB, SD, SBV)
• Amalyze — Brand or sub-brand
• WB-500ML — SKU or SKU family identifier
• Manual — Targeting mode (Manual / Auto / Product)
• Exact — Match type (Broad / Phrase / Exact / n/a for product targeting)
• Harvested — Role (Harvested / Discovery / Branded / Conquest / Remarketing / Defense)

Why each segment matters

• Format lets you filter by ad format in the bulk reports. Every report comes pre-sliced by format if the names carry it.
• Brand matters for multi-brand sellers and for sub-brand campaigns within a single brand.
• SKU/Theme is the join key to the P&L. Without an SKU code in the campaign name, you cannot tie ad spend to product margin in any downstream report.
• Targeting + Match Type disambiguate the dozens of campaigns that share an SKU. WB-500ML - Manual - Exact is unmistakably different from WB-500ML - Auto.
• Role is the human-readable description of why the campaign exists. Harvested vs. Discovery vs. Branded is the operating instruction; without it, the next operator (or your future self in three months) has to reverse-engineer intent from the targeting.

Date-bound campaigns

Event campaigns get a date suffix appended:

SP - Amalyze - WB-500ML - Manual - Exact - PrimeDay2026
SB - Amalyze - WB-Family - Manual - Exact - BFCM2026

The date suffix forces the campaign to read as "this is a time-bound thing" — operators are more likely to remember to pause or archive it when the event ends.

A/B test naming

Side-by-side tests use a -vA / -vB suffix:

SP - Amalyze - WB-500ML - Manual - Exact - Harvested -vA
SP - Amalyze - WB-500ML - Manual - Exact - Harvested -vB

The losing variant gets paused and renamed -vA-paused-2026-04-12 for archival traceability.

Migration: imposing convention on a legacy account

A pre-existing account with inconsistent naming can be migrated in three passes:

1. Inventory. Export all campaign names; tag each with its inferred Format/Brand/SKU/Targeting/Role.
2. Rename in bulk via Bulk Operations. Amazon's bulk upload allows campaign name updates; convention can be imposed across hundreds of campaigns in one upload.
3. Lock the convention. Document it; tie new campaign creation to a template.

Common mistakes

• No convention at all. Default state of accounts set up in a hurry.
• Convention exists but isn't enforced. New operators don't know it; new campaigns drift from it; within 6 months it's gone.
• Convention too detailed. Eight segments with sub-segments makes names 90+ characters long and unreadable in the campaign manager.
• Convention too sparse. Three segments (SP - SKU - Exact) doesn't disambiguate enough; SKU + match type leaves multiple campaigns sharing the same name.
• Brand segment skipped on single-brand accounts. Reasonable today; painful when the company adds a second brand and has to retrofit thousands of campaign names.