Naming Conventions and Portfolios

A campaign name should help the seller manage the account before they ever open the campaign.

When an account has only a few campaigns, naming feels unimportant. A seller may create campaigns called "Auto Test," "Dog Shirts," "Exact 1," "Halloween," or "Campaign 3" and still remember what each one means. The problem appears later, when the account has dozens or hundreds of campaigns, several product groups, different match types, seasonal tests, second-chance structures, winner campaigns, defensive campaigns, and old experiments that were never cleaned up.

At that point, weak naming becomes an operational problem. The seller cannot quickly tell what the campaign contains, why it exists, what marketplace it belongs to, whether it is discovery or scaling, whether it is seasonal, whether it contains one ASIN or many, or whether it should be reviewed, paused, protected, or ignored.

A campaign name is not decoration. It is a control layer.

Good naming allows the seller to search, filter, compare, audit, pause, and manage campaigns without opening each one manually. It also protects the account from future confusion. A seller may understand a campaign perfectly on the day it is launched, but six months later the name needs to explain the structure clearly enough that the next decision is still obvious.

If the campaign name does not reveal the campaign's job, the account will become harder to control as it grows.

There is no single naming convention every seller must use. The exact format can vary. What matters is consistency. A naming system should be simple enough to use every time and clear enough to make the campaign readable from the main dashboard.

A strong campaign name usually includes the most important management fields: marketplace, ad layer, targeting method or match type, campaign role, product type or product group, ASIN or theme when relevant, timing or season when relevant, and launch date or batch.

Table 6.6. Campaign Naming Framework