Campaign Naming Conventions

Tyler Jordan
October 29, 2019

Campaign naming seems like an unimportant, mundane concept, but it’s not.  In order to maintain clean reports and properly run messaging tests at scale, you need to be able to segment out different pieces of your performance in easy and repeatable ways.  We also need a campaign name that makes it easy to filter in the Google Ads engine.

So campaign naming is going to have 2 primary purposes

  1. To allow for proper and effective reporting

  2. To allow for quick analysis at a glance within the network (Google or Bing)

To be able to do this you want to be able to identify a number of different high level items at a quick glance.  The important stuff for reporting and analytics are going to be what the network is and whether you’re targeting in search, display or video.  For quick glance analysis those will be important too, but you will also want clarity on brand vs non-brand vs competitor, you will want to narrow down on product or service categories and sometimes sub-categories, as well as geo and match type.

The elements we include in our campaign naming convention are as follows:

  • Network (Google or Bing)

  • Medium (Search, display, video, native, etc.)

  • Brand vs Non-Brand vs Competitor for search or Prospecting vs Retargeting for display/video

  • Category

  • Sub-category (if necessary)

  • Geo

  • Alpha/Beta/Gamma/Delta/GDN/YT


Here are some example campaign names for a shoe retailer:

  • Google_Search_NB_Sneakers_UK_Beta

    • This would be a non-brand search campaign running on Google focused on sneakers in the UK targeting broad match modified terms

    • All of these elements could be easily broken down and segmented in reporting and with a quick filter they could be viewed in the network’s interface

  • Google_Display_Prospecting_CustomIntent_US_GDN

    • This would be a Google Display campaigns focused on new user prospecting using custom intent as the targeting category in the US

Using this campaign naming formula you can get a lot of information squeezed into a small amount of text, and if you standardize things properly you can bubble up insights to higher levels both in reporting and in the UI.