Enforce naming conventions: compute program name based on tag values + other info

Enforce naming conventions: compute program name based on tag values + other info

Enforcing Program naming guidelines in large orgs is always painful.

It would be great if the admins could set automated rules that would automatically define the name of a program, as a combination of infos, using :

  • The program type (Event, default, email or engagement)
  • The program channel, using rules such as (if channel = gated content, then add "GTC" to the name, else if... Choice-like approach might be appropriate)
  • All the program tags (again with if then else or choices)
  • Program dates (for the ones that are in the calendar) and/or program creation date, with the possibility to output it in YYYYMMDD format
  • Some free-entry fields

-Greg

8 Comments
Grégoire_Miche2
Level 10

Ideally, if the program is sync with a campaign in SFDC, the SFDC campaign name would be updated if the program name changes.

Anonymous
Not applicable

Hi,

Where I have the most program with people following naming conventions is in the Design Studio and this is due to filtering. I have logged idea on what would go a long way to help that here -  

Grégoire_Miche2
Level 10

One of the reasons why this is important is because complying with the naming convention plays a full role in the ability to get a solid attribution reporting.

-Greg

Grégoire_Miche2
Level 10

also add info about the workspace. This would require that each workspace has a short name.

This is required so that programs can be easily sorted in RCE program opportunity analysis. See Best Practices for Troubleshooting RCE Program Opportunity Analysis Report Issues

-Greg

Dan_Stevens_
Level 10 - Champion Alumni

Similar to the well-publicized tool that Docusign uses with Eloqua: DocuSign | Eloqua Toolkit

Anonymous
Not applicable

It is unfortunate that this is the case. I wish Marketo would include program ID in its data rather than force us to rely on the program name to match up activities in the log.

Grégoire_Miche2
Level 10

Hi Matt,

Program ID's are not good enough: as you continuously add new programs to your instance, if you use program ID, you will have to go back to your smart campaigns and add the new IDs many times a day in a large org.

I would rather use program properties such as tags.See

-Greg

kh-lschutte
Community Manager
Status changed to: Open Ideas