Why naming conventions matter

A team wants to compare video ads across three markets. It sounds like a straightforward reporting task.

One market uses “Video” in its campaign names. Another uses “VID.” The third includes the format in some names and leaves it out of others.

Before anyone can compare performance, someone has to decide which ads belong in the report.

That work rarely appears on a reporting dashboard. Yet it affects everything the dashboard shows: which ads are included, how they are grouped, and whether the comparison is useful.

Omnitor’s taxonomy and naming tools help teams organise campaign data consistently and identify issues that need attention. They give creative and performance reporting a clearer foundation.

The structure behind a useful report

Most reporting questions depend on being able to group ads correctly.

How did a product perform across markets? Which creative formats had a higher click-through rate? What did the team spend on a particular campaign theme?

To answer those questions, the relevant information needs to be present and recognisable.

A naming convention defines how that information should appear in a campaign, ad group, or ad name. A taxonomy defines the fields and values the team uses to describe its work.

For example, a team might use fields for market, product, format, and creative concept. Each field needs a shared meaning. If “format” refers to image or video, everyone should use it that way.

Without that agreement, two people can create names that look reasonable but describe the work differently. A report may then separate ads that belong together or combine ads that should be reviewed separately.

Small inconsistencies become reporting problems

Naming issues are often ordinary mistakes.

Someone copies a previous campaign name and misses a field. A new team member uses a different abbreviation. A local market introduces a value that has not been added to the shared dictionary.

Each issue may seem minor in isolation. Across hundreds or thousands of ads, those differences become harder to track.

The effect is not always obvious. A report can look complete while leaving out ads with missing or unrecognised values. A category can appear to have little spend because the same activity has been recorded under several names.

That makes it difficult to know whether a result reflects campaign performance or the way the data was organised.

The problem often surfaces during a review: someone notices a missing campaign, questions a total, or asks why an ad appears in the wrong group. The discussion pauses while the team checks the underlying data.

How Omnitor helps teams find the issues

Omnitor checks campaign naming against the defined taxonomy and surfaces mismatches for review.

The issues view identifies problems such as:

• Missing mandatory fields: information required by the naming convention has not been included.

• Unknown fields: a field appears in a name but is not recognised in the taxonomy dictionary.

• Invalid values: a field contains a value that does not match the expected structure or accepted values.

The issue details help teams understand what needs attention. They can see the affected ads, platform, name level, field, and a description of the problem.

That context matters. “There is a naming error” leaves someone with another search to do. Knowing which field is missing, where it is missing, and which ads are affected makes the review more direct.

Teams can correct names in the source ad platform, then re-import the data or wait for the next sync. Where a new field or value is intentional, the team can review whether its shared taxonomy needs to change.

Separate errors from intentional changes

A taxonomy needs consistency, but campaigns evolve.

A team may enter a new market, introduce a product line, or start testing a new creative approach. The existing structure may need to accommodate that work.

When an unfamiliar value appears, the first question should be whether it is a mistake or a legitimate addition.

If it is a mistake, the campaign naming needs correction. If it is intentional, the team needs to agree on how to represent it consistently.

That distinction prevents people from forcing new activity into an old category simply to make a validation issue disappear.

Omnitor makes the mismatch visible. The team brings the context needed to resolve it.

A practical example: comparing formats across markets

Suppose a team wants to review image and video ads for a product launch in the Netherlands, Germany, and France.

Its agreed format values are IMAGE and VIDEO. During setup, some ads use VID, while others omit the format entirely.

Depending on how the report is built, filtering for VIDEO could miss part of the campaign. Comparing the remaining ads might give the team an incomplete view.

A useful review would follow four steps.

1. Check the relevant naming issues.
Identify ads with missing or invalid format values and confirm that they belong to the campaign being reviewed.

2. Verify the intended values.
Look at the affected creatives and campaign context. Confirm which ads are videos and which are images.

3. Correct and refresh the data.
Update the names in the source platform, then bring the corrected information back into Omnitor through re-import or sync.

4. Review the comparison again.
Check that the report now includes the intended ads and that the market and format groupings make sense.

The corrected structure supports a more complete comparison. The team still needs to consider differences in spend, audience, placement, and campaign objective when interpreting the results.

Give the convention a clear owner

A naming convention is easier to maintain when someone is responsible for it.

That does not mean every campaign name needs central approval. It means the team knows where the agreed structure lives, who can clarify it, and how changes are handled.

A practical starting point is to agree on:

• Which fields are required for reporting.

• Which values are accepted for those fields.

• How teams should request a new field or value.

• Who reviews recurring naming issues.

Keep the structure focused on information the team actually uses. Every required field adds work during campaign setup and needs to be maintained.

A long convention with unclear definitions can create as much confusion as a short one with missing information. The aim is a structure people understand and can apply consistently.

Use naming health to guide the review

A naming-health summary gives teams a quick view of how much campaign data passes validation and where warnings or errors remain.

It is a useful starting point for deciding what to review. A missing market field, for example, deserves attention before a market comparison.

Passing validation does not guarantee that every detail is correct. An ad can contain an accepted market value that was