Ensighten recommends that each company establish a common naming standard for their Conditions and Deployments.
The benefits of establishing a naming standard reduces confusion, identifies Conditions or Deployments quickly and easily for your various internal groups and teams. In addition, you can easily train new team members who will work on your account. Without common naming structures, it quickly becomes difficult to identify and locate your Conditions and Deployments.
There are a variety of Condition types you might create including URL, Geographic Region, Time, and Browser Data.
The most common type is a URL Condition.
A method for naming your Conditions includes using the website property name, usually in some abbreviated form followed by an underscore, dash, colon, or space with the name of the page or pages where the condition will apply. For example:
You can add additional Condition types to your URL Condition, such as Geographic Region or Timing Conditions and include them to the condition name as follows:
Your website is http://vacations.com
To set up a Condition that applies to the home page of the site. You can use the following example to name the Condition:
- vaca can represent your website name
- hm represents the page name, such as home page
Condition name: vaca_hm
If you decide to add timing to your condition to include actual dates, or some other reference to the timing, the Condition name can look like:
You can develop a common structure for everyone to follow when adding Conditions to your Manage account. Posting your naming structure internally gives your Manage users a reference to use as a best practice.
When configuring your Deployments using the Manage App wizard the third step requires giving your deployment a name. It is a best practice to add the Deployments Tag type and sub-Tag details to the front of the condition name as in the following examples.
- GA:EventTracking:vaca:forms - In this example, GA is an abbreviation for the Google Analytics tag, followed by the sub-tag detail Event Tracking, and the Condition on the vactions.com website forms.
- SiteCat-PageCode-Vaca-Global - SiteCatalyst page code tag firing on the entire vacation.com site.
- FL:Vaca:OrderConf - FloodLight tag on the vacation.com order confirmation page, AdWords_Vaca_OrderConf - Google AdWords tag on vacation.com order confirmation page.
- GA_Initialization_Vaca_Hm - Google Analytics initialization tag on the vacation.com home page.
- GA:BaseCode:Vaca:Global - Google Analytics base code tag firing on entire vacations.com site.
Include abbreviations you will use for Tags and web sites. Add comments to your deployments of the configuration process, which you can choose to use to describe what you are deploying.