Naming Conventions Monitoring

Naming Conventions Monitoring

Naming Conventions Monitoring

💡

Trackingplan helps you ensure consistency and accuracy in the naming conventions used across your events, campaigns, mediums, sources, and properties by detecting and highlighting discrepancies, such as duplicate or improperly formatted names, that may compromise data quality, attribution, or analytics implementations.

image

For it, Trackingplan enables you to create customized naming convention rules for your UTMs and analytics implementations, allowing you to seamlessly validate that your campaigns and analytics data consistently adhere to your established naming standards.

image

Edit Rules

☝🏻

To make things easier, Trackingplan includes a set of preconfigured rules that you can easily activate or deactivate based on your preferences.

These rules are thoughtfully designed to address the most common use cases and align with best practices recommended by major providers, such as Google Analytics 4 (GA4).

Despite their pre-configured nature, these rules are fully customizable, allowing you to adjust them to fit your team's needs and ensure your data and campaign tracking aligns with your goals.

To customize a rule, simply click on the “Edit” button next to the rule you wish to modify.

image

This will open a modal where you can review the rule's default configuration and adjust its parameters to better suit your specific needs. For example, you can refine the rule to apply only to a particular provider, such as GA4, or exclude certain events where you know the rule might not be applicable.

image
☝🏻

Additionally, you’ll be able to see in real time which elements are impacted by any of our rules as you edit or create them. For instance, in the scenario above, we can see that out of 80 events that meet these parameters, 3 are non-compliant with this rule.

Create New Rules

💡

Trackingplan also offers you the possibility to create your own custom rules from scratch, allowing you to define unique rules for your campaigns, mediums, sources, events, and properties. This ensures each element of your tracking setup has its own tailored rules, providing you with full control over your naming conventions and tracking parameters.

To do so, simply click on the “Create naming rule”.

image

Next, give your rule a title and select the dimension where you'd like to apply it (campaigns, events, mediums, etc.).

Trackingplan allows you to create these rules using Regular Expression (Regex) patterns to which all the values seen must conform, ensuring strict and consistent data validation.

image
🫰🏻

For additional support, we’ve created this Regex Tester Tool to help you test and validate regular expressions with ease. Moreover, if you're not familiar with Regex, our support team will be happy to guide you through the process, assisting you in creating and refining your custom rules to fit your specific requirements.

image

Identifying Issues

Once you’ve set up naming convention rules, Trackingplan makes it easy to detect violations throughout your panel. Any element—whether it's an event name, campaign, medium, etc.—that breaches the rules will be highlighted, providing you with instant visibility into where corrections are needed.

💡

Think of it as a “spellchecker” for your data, visually pinpointing which elements are not meeting the required standards.

image
☝🏻

However, we understand that pinpointing errors in a panel with 2,000+ campaigns can be overwhelming. That’s why Trackingplan offers you the option to filter only by affected elements, giving you the total number of errors that fail to meet any of your active rules. To refine this even further, you can also apply filters on specific rules, isolating only the warnings related to that rule to tackle specific issues systematically.

image

Finally, by hovering over the highlighted area, you’ll see a detailed explanation of the rule that hasn’t been met. This gives you a clear understanding of the problem and its context, making it easier to take corrective action.

image

From there, you can always ignore a naming convention for a specific element if it’s an exception or edit the rule to adjust its parameters.

Use Cases

Let’s explore some practical use cases with some real-world examples:

Create Rules for Event and Property Naming Conventions

Ensure event names are always in lowercase

💡

Setting up a rule to alert you whenever an event contains uppercase letters or other non-compliant values helps maintain consistency in your tracking.

image

Additionally, when creating or editing rules for event naming conventions, you can limit the scope of the rule to apply only to specific destinations. For example, you can set a rule to apply exclusively to Google Ads (destination = Google Ads).

🫰🏻

Need help testing and validating your Regex? Use our Regex Tester Tool to fine-tune your expressions with ease.

In your Events tab, you’ll find detailed insights about errors in your event naming conventions. Yet, if you’ve also configured naming convention rules for properties, these will be visible by expanding any of your events.

image

To view errors specifically related to property naming conventions, you can also head over to your Properties tab. There, you’ll find all relevant issues organized for quick review and resolution.

Create Rules for UTM Naming Conventions

Maintaining proper UTM naming conventions is essential for preventing attribution errors that could disrupt the accuracy of your marketing performance metrics. That’s why having precise and consistent UTM naming conventions is crucial for reliable attribution.

Enforce Numeric Values for the UTM Source affiliate

💡

Setting up a rule to trigger an alert if the source is set to affiliate, but campaign name contains letters or any other non-numeric values.

image
🫰🏻

Consistent and valid UTM parameters reduce attribution errors, helping you accurately calculate the return on ad spend (ROAS), and determine the true cost per acquisition (CPA). For more help, our UTM Builder Tool can guide you in creating structured and error-free UTM parameters.