Ad naming conventions for SaaS campaigns

Why do ad names matter for reporting?

Ad names are the only label that travels with spend from every platform into your reports. When they follow one pattern, a script can split each name into channel, region, product and stage. When they do not, every pivot table needs hand cleaning, and automated rules that act on names misfire.

SaaS accounts drift quickly. New channels, regions, product lines, funnel stages, audience lists and creative tests each add a dimension. Without a standard, a campaign called US_Ent_Retarget_Q2 may in fact target UK enterprise accounts, and nobody can tell from the report.

What does a good convention look like?

A good convention is a fixed order of fields, one delimiter, a short glossary of allowed values, and nothing else. This pattern covers most B2B SaaS programs: channel, geo, product, stage, audience and launch month, in that order, in lowercase and joined by underscores.

• channel: linkedin, googlesearch, googledisplay, meta, capterra.

• geo: ISO country codes or your sales regions, such as us, uk, emea.

• product: a short code per product or use case, such as crm or platform.

• stage: aware, consider, convert or expand.

• audience: abm1 for a named account list, rtg for retargeting, lal for lookalikes, broad.

• yyyymm: the launch month, so relaunched campaigns stay comparable.

Example: linkedin_us_crm_consider_abm1_202607. Ad sets and ads add their own fields after the campaign part, such as the creative variant.

Which rules prevent most errors?

Four rules prevent most naming errors, and each is easy to check by script.

1. One delimiter. Underscores between fields, hyphens only inside a value, never both in the same role.

2. Lowercase, no spaces. Google Analytics treats UTM values as case sensitive, so utm_source=google and utm_source=Google are two sources, and missing values show as "(not set)".^[1]

3. A glossary. One shared list of allowed codes, so plg cannot mean product-led growth in one region and platform in another.

4. A date field. Without it you cannot tell a relaunch from the original run.

Keep the number of fields small. Granular detail such as headline or image belongs at ad level or in utm_content, not in the campaign name.

How do names connect to analytics?

Names connect to analytics through UTM parameters, so the campaign name should be the utm_campaign value. Google recommends always setting utm_source, utm_medium and utm_campaign.^[1]

• Medium decides the channel. GA4 assigns its default channels from source and medium, for example Paid Search or Paid Social when the medium matches values such as cpc, ppc or paid followed by any text. Traffic that matches no rule is reported as Unassigned.^[2]

• Cost joins need exact matches. GA4's campaign data import adds cost, clicks and impressions from other platforms and joins on source and medium; "Facebook" and "facebook" do not match.^[3]

• Pass names automatically where you can. LinkedIn's API supports dynamic tracking parameters that insert the campaign name, campaign ID or campaign group into landing page URLs.^[4] Google Ads ValueTrack passes the campaign ID rather than its name, so join ID to name in your data.^[5]

The same fields then map to CRM campaign records, so closed-loop reporting can join spend to pipeline.

How do you enforce the convention?

Enforce it in the tools people use to launch campaigns, not in a document nobody opens.

• A name builder. A sheet or small form with dropdowns for each field that outputs the exact name and the matching UTM string.

• A launch checklist step. The name and UTMs are checked before a campaign goes live.

• A nightly check. A script reads active campaigns through each platform's API, tests names against the pattern and posts a list of exceptions to your team channel. Fix them within a day.

• A lookup table for history. Map old names to the new fields in your reporting layer instead of trying to rename everything.

Automated campaign taxonomy mapping covers how to apply the mapping as data arrives.

What mistakes undo a convention?

Most conventions fail through slow drift rather than one big error.

• Too many fields. Twelve fields in one name means nobody fills them in correctly. Keep the ones you filter on weekly.

• Vague codes. Any code that two people read differently will split your reports.

• Mixed sources. Campaigns built by hand and by bulk upload with a different delimiter break every parser.

• No owner. Someone in marketing operations approves new codes and retires old ones.

Where should you start this week?

Start small and fix the campaigns that carry the most spend:

1. List your top spending campaigns across platforms and write down what each name means.

2. Agree on the fields and the glossary with everyone who launches campaigns.

3. Rename the active campaigns and set the matching UTMs.

4. Add the nightly check and the lookup table for older names.

With names in place, a unified marketing dashboard can compare channels on the same terms. Our marketing analytics and attribution service sets up conventions, tracking and reporting together, as part of our digital marketing work.