View
 

Naming Conventions

Page history last edited by Tobin Poppenberg 8 months, 1 week ago

Overview

 

Learning Resources

Getting Set Up

Features by Screen

 

Affiliate Management <NEW!

 

Payment Processing System <NEW!

 

Wordpress Integration (PilotPress) <NEW!

 

Advanced Users

 

Email Best Practices

 

Postcards

 

Get Involved

 

Work With Us

 

Contact Us

What We're Working On

 

Done-For-You Campaigns

 

Other Cool Stuff


 

 

Getting Started: Naming Conventions

 


 

Naming Conventions

In order to keep your system well organized, we highly recommend using standardized naming conventions right from the start, for all your tags, groups, sequences, rules, trackers, tasks, task outcomes, emails, postcards, landing pages, and SmartForms.

 

For instance, if you're making tags for different lead sources where your contacts come from (which, in most cases, you'd set it up so that your SmartForm automatically tags all new incoming contacts with upon filling out), you would want to start each of those tags with: "Lead Src:" So, you might end up, for instance, with the following contact tags:

 

  • Contact Type: Prospect
  • Contact Type: Customer
  • Contact Type: Former Customer
  • Contact Type: Affiliate 

 

...instead of merely:

 

  • Prospect
  • Customer
  • Former Customer
  • Affiliate

 

Or if you're creating your e-mail newsletters, you'd want to name them like this:

 

Newsletter: July

Newsletter: August

Newsletter: September

 

...instead of:

 

July Newsletter

August Newsletter

September Newsletter

 

In the first way, they'll be easily identifiable, searchable, and useable by you and other members of your team because they will show up in collections and dropdown menus together, rather than all spread out (since items in collections and drop down menus are listed in alphabetical order). These example are about creating tags and messages, however, you can (and SHOULD) apply this kind of standardized naming conventions to everything you name throughout the system.

 

FAQs

 

Go to top

 

 

 

 

 

Comments (0)

You don't have permission to comment on this page.