How to Configure a Standalone Campaign Name Generator?

Sometimes, you don't need a full tracking URL, you simply need a standardized, consistent name to paste into Salesforce (SFDC) or Marketo.

This guide will show you how to configure a project specifically for this purpose. By using a Custom Parameter and a strict Convention, you can transform the platform into a pure "Campaign Name Generator," allowing you to build complex naming strings for your CRM records without worrying about web links or UTMs.

For example, you can enforce a structure like <Campaign Type>-<Platform>-<Send Date> to ensure every team member generates identical formats.

Step 1: Set Up a Dedicated Project

First, create a specific workspace for this task to keep it separate from your standard link-building workflows.

1. Navigate to the Projects Dashboard.
2. Click Create a New Project.

3. Enter a descriptive name, such as "SFDC Campaign Name Generator" or "Marketo Naming Tool."

4. Locate the UTM parameters section, uncheck Enable UTM parameters. Since we are only generating a name, we do not need standard tracking tags. 

5. Scroll down and click Show Advanced Settings.

6. Check the box for Force conventions. This is a great way to ensure your team follows your strategy closely. Enabling this will remove the "No Convention" option from the builder and disable any URL builders that don’t support conventions.
7. Click Save to create the project.

Step 2: Create the Custom Parameter

Next, define the "container" that will hold your generated campaign name.

1. Open your new project.

2. Navigate to Parameters > Custom.

3. Click Create New Custom Parameter.

4. Name this parameter exactly what you want the output to represent, such as "SFDC Campaign Name."
5. Click Save.

Step 3: Build the Naming Convention

To strictly enforce your naming structure, you must build it from the ground up using Fields, Formats, and finally the Convention itself.

A. Create the Fields (The Building Blocks) 

First, define the individual components that will make up your naming string.

1. Navigate to Tools > Conventions > Fields and click Create a New Field.
2. Create a separate field for every part of your name (e.g., Campaign Type, Platform, Send Date).
3. For each field, define the Type:
   • Option: Creates a dropdown menu for multiple options.
   • Date: Adds a date picker with a specific format (e.g., YYYY_MM_DD).
   • Constant: Hardcodes a value that never changes.
   • Text: Create a simple text input field for custom values. 

4. Campaign Type Field: Set Type to Option and add values like productlaunch, retargeting, etc.

5. Platform Field: Set Type to Option and add values like facebook, linkedin, etc.

6. Send Date Field: Set Type to Date and select the date format from the dropdown.
7. Save each field before proceeding.

For a deeper dive into field types and settings, read our guide on Creating and Managing Fields.

B. Define the Format (The Structure) 

Next, arrange your fields into a reusable pattern.

1. Navigate to Tools > Conventions > Parameter Formats and click Create a New Format.

2. Give it a name (e.g., "SFDC Name Format") and choose a Separator (like a dash - or underscore _) to divide the fields and click Next.

3. Drag and drop your Campaign Type, Platform, and Send Date fields from Available Fields to Configured Fields in the exact order they should appear.
4. Click Save.

You can learn more about how to build and arrange parameter formats in our Manage Parameter Formats article.

C. Assemble the Convention (The Rule Set) 

Finally, link your format to the custom parameter to enforce the rule.

1. Navigate to Tools > Conventions > Conventions and click Create a New Convention.

2. Enter a name for your convention (e.g., "SFDC Naming Logic").

3. Locate the Custom Parameter you created in Step 2.
4. Set the parameter to Enforce Format and select the Format you built in Part B.
5. Click Save to finish the setup.

For a complete guide on building convention field logic, refer to our help documentation on How to Create and Manage Conventions.

Step 4: Optimize Project Navigation

To make this easy for your team, you should change the default project navigation to open directly to the naming tool, bypassing the standard URL builder entirely.

1. Go to Settings within your project navigation.
2. Click Show Advanced Settings.

3. Scroll down and locate the Default Project Navigation field.
4. Select Custom Parameters from the dropdown menu.
5. Click Save.

Now, whenever a user enters this project, they will land immediately on the screen used to build the name.

Step 5: Generate Your Campaign Name

With the setup complete, generating a compliant name is fast and enforced by your project settings.

1. Open the project (you will land directly on the Custom Parameters tab).
2. Click on Add a new value to create a new entry for your custom parameter (e.g., SFDC Campaign Name).

3. On the creation screen, notice that your default convention (e.g., SFDC Naming Logic) is automatically loaded since Force conventions is True.
4. Select the appropriate values for Campaign Type, Platform, and Send Date from their respective dropdown menus.
5. As you select your options, notice that the Parameter Value field is automatically filled with your correctly formatted string.
6. Click Save to finish.

You have successfully configured a tool that generates perfectly formatted campaign names for Salesforce or Marketo, completely independent of URL building. Your team can now produce consistent data for your CRM with just a few clicks.

Best Practices

To get the most out of your naming generator, keep these tips in mind:

• Use Dropdowns over Free Text: When building your convention, use dropdown menus whenever possible. This prevents typos and ensures 100% consistency in your data.
• Define Delimiters Clearly: Ensure your convention uses clear delimiters (like underscores _ or dashes -) between fields so the name is easy to read in your CRM.
• Keep it Separate: Do not mix this naming workflow with projects used for tracking URLs. Keeping them separate prevents user confusion and accidental data errors.