Naming Conventions

The Campaign Suite creates campaigns and ad groups, which are named according to the default naming conventions explained below. Optionally, these can be changed for each template individually. This article explains how this can be done, but why deltamethod highly recommends not to change them.

Names of campaigns are created using the prefix of the template’s first table combined with the ID of the table value for which the campaign is created. In the simple example of a category table with the entries (sneakers, shoes and boots), which have the IDs (0001,0002 and 0003) respectively, and the table prefix “Cat”, these three campaigns will be created:

[Cat_0001]{ep}: sneakers
[Cat_0001]{b}: sneakers
[Cat_0002]{ep}: shoes
[Cat_0002]{b}: shoes
[Cat_0003]{ep}: boots
[Cat_0003]{b}: boots.

The content of the curly bracket {} informs the user about the match type, with “e” indicating “exact”, “p” indicating “phrase” and “b” indicating “broad”. This token informs the user about which keywords of which match types this campaign contains. However, this token only exists in campaign names, if the second or fifth campaign structure is chosen. The reason for this is that only for these campaign structures, different campaigns are generated for different match types. In the example above, the campaign “[Cat_0001]{ep}: sneakers” contains all the ad groups that consist of exact and phrase keywords for sneakers.

Generally, campaign names are built in the following form:

The names of ad groups are composed in a similar way, the difference being that ad groups contain the names of the main table as well as the support tables.

When combining the category table used in the previous example with a brand table (adidas, nike and puma) and a color table (red, blue and green), the ad groups created will look as follows:

[Cat_0001|B_0001|color_0001]{ep}: sneakers adidas red
[Cat_0002|B_0003|color_0002]{ep}: shoes puma blue
[Cat_0003|B_0001|color_0003]{ep}: boots adidas green.

Generally, the names of ad groups are created in the following form:
[PrefixOfMaintable_IdOfTableentry|PrefixOfSupporttable_IdOfTableentry|...]{FirstLetterOfMatchtype(s)}:name1 name2 name3.

WARNING: deltamethod highly recommends not to change these names as this would alter the generated structure. A change would cause problems with analytical features or subsequent changes in this template’s table set. Furthermore, punk negatives cannot be set anymore if you don’t follow a consistent naming convention throughout all templates. Please only apply changes if you know all the consequences.

Step 1 – Access the naming convention

To access the naming structure of a template click on “Settings” > “Define structure” to open the window where a custom naming convention can be implemented.
Define structure

Step 2 – Define a custom naming convention

The screenshot below shows the window, which is available from inside every template. By clicking the radio button “Custom”, fields for the different entities that need to be named appear. In most cases, these already include the actual default naming rules used by the Campaign Suite. To change these rules, change the entries of the fields. Leaving a field empty will result in the corresponding campaigns and ad groups not being created.
Define a custom naming convention

Note: Be aware that a change only applies to the campaigns and ad groups created by this very template. Other templates will not be affected by the current template’s custom naming rules.

To save the changes check the box after verifying all changes being made are correct and click on “Save changes”.

Refer to campaign structures to learn more about how campaigns and ad groups are created by the Campaign Suite.