Stop fixing naming after the campaign is live.

Apply your convention

Your standard becomes part of the workflow.

Your organization defines the naming rules, the categories, their order, required values, and approved vocabularies. Naming reads that configured convention and puts it in front of the person creating the asset, so names come from the organization's standard, not from whoever happens to be working that day.

• One convention for the whole team, so the standard survives turnover, agencies, and busy quarters.
• New joiners follow the rules from day one, without memorizing a naming document.
• Governance you set once and update centrally, not a policy people quietly drift from.

Assemble + validate

You select the components. Naming validates the result against your standard.

Pick the values for each category, business unit, language, region, campaign, date, and the name is assembled from your convention as you go. You provide the inputs; Naming keeps them in the order and format your standard requires.

Before anything is created, Naming checks the assembled name and flags exactly which rule it breaks, so a mistake is caught here instead of surfacing later in your grouping, attribution, and reports.

• Errors are stopped at the source, before they multiply into hours of reporting cleanup.
• Fewer naming reviews and correction threads, so campaigns move from idea to launch faster.
• Confidence for every user that a name is right the moment it's saved.

Create or rename

New assets enter on standard, older ones are brought back to it.

Once you approve the name, Naming creates the real asset in Eloqua or Marketo, an email, landing page, form, program, or campaign, so nothing becomes a cleanup problem later.

Existing inconsistency doesn't have to be permanent either. Point Naming at an asset already in your platform and it prepares a compliant name and previews the rename. Creating is confirm-gated and a rename happens only when you submit it, never silently or on its own.

• Your instance stays clean as it grows, so cleanup never becomes a recurring project.
• Years of inconsistent assets can be brought in line without a manual rename marathon.
• Assets stay easy to find and group, so teams spend time on campaigns, not hunting.

Marketo only

UTM tagging & tracking exports

Every new asset ships with tracking that matches its name.

On Marketo, Naming tags each approved asset with UTM parameters drawn straight from its name, then hands your team a tracking and asset-creation export. Campaign tracking is set the moment the asset is made, not patched in afterward.

• Attribution your analytics team can trust, because source and campaign values line up with the asset name.
• No more hand-built tracking links, so campaigns launch faster and with fewer errors.
• A ready record of what was created and how it's tracked, for reporting and audits.

Eloqua only

Campaign-field & CDO write-back

The name and its reporting fields always tell the same story.

On Eloqua, Naming reads the approved name and writes its values back into campaign fields and custom data objects. Region, product, and campaign type are populated for you, so the structured data behind a campaign always matches the name on it.

• Dashboards and ROI reports built on fields that stay consistent, campaign after campaign.
• Less manual field entry for your team, and fewer mismatches to reconcile later.
• Cleaner segmentation and analysis, because the reporting attributes are always there.