Data Validation

Data Validation

Data Validation

With Trackingplan, you can be automatically notified whenever your properties, events, and user acquisition data don’t conform to the values you have specified.

Data validation techniques serve as a proactive mechanism designed to intercept and rectify issues before errors compromise the integrity of your data.

Here are some of the data validation mechanisms that Trackingplan supports to ensure your data always arrives to your specifications and, in case they don’t notify you so you can fix it in record time.


Enums allow you to specify in advance the values you expect for a property to be notified every time it receives a value that does not conform to your list of predefined constants.

Just as Trackingplan automatically learns about the type and frequency constraints associated with each of your properties, its algorithm is also able to auto-infer enums based on your data.


Yet, to write Enums for a property manually, click on its type field and select Enum in the drop-down menu.


If this is the first time creating an Enum, select Create New Enum. Otherwise, you can reuse one of your existing ones, cloning it directly or editing it for this specific property.


In the next panel, you can name your new Enum and write the corresponding values. To help you with this, you can also autocomplete your Enum with the values that Trackingplan has observed in the last 30 days within that property.

Doing this will automatically show you all the values detected for this property in the last 30 days, but you can also check that all the values are correct and, in case they are not, delete them. Moreover, you can also ignore cases and diacritics to ensure the server will recognize any possible character or accent variations.

Once you are happy with it, click on Create New Enum. The new Enum will now appear in the drop-down menu. Select it and click on Use on this property.

All set! From now on, Trackingplan will be checking that all the values in this property match the specified Enum.

If it detects a value that is not within this list of predefined constants, Trackingplan will automatically send you a warning.

For both enums manually added or automatically inferred by Trackingplan, you'll always have the option to edit them by adding or removing values to your lists at any time.

RegEx (Regular expressions)

This feature allows you to specify a regular expression pattern (Regex) to which all the values seen for a property must conform.

The process of setting up Regex for a property is very similar to the one used for Enums.

Firstly, click on its type field and select Regex from the drop-down menu.


The following panel will appear. Click on Pick a Regular Expression. If this is the first time you create a regular expression, select Create New Regex. Otherwise, you can reuse one of your existing ones, cloning it directly or editing it for this specific property.


In the next panel, you can name your new regular expression (e.g.: language_regex) and write the corresponding pattern. You can also insert test values to confirm that your regular expression pattern will work as you expect. Once you are happy with it, click on Create New Regex.

Need help validating and testing your regex patterns? Check our regex tester tool to ensure your regular expressions are error-free.

Moreover, for Regexes, you can also ignore cases, diacritics, or both to prevent in advance any situation where the server would recognize it as an implementation issue.


The new Regex will now appear in the pick-up menu. Select it and click on Apply to this property.

From this point on, Trackingplan will be checking that all the values for these properties match the specified regular expression. If a value does not conform with the pattern you have specified, the dashboard will automatically show you a warning.


Function Validations

This feature allows you to set up any complex validation at track level and will warn you every time any of your properties don’t conform to the function provided to validate an event (e.g: cross-conditions like validating that all products logged in a cart carry a valid product_sku given the page section).

To set up custom validation functions, please contact and we will help.

Campaign Validations

Trackingplan also allows you to set up User Acquisition specification warnings to validate your campaigns based on your own requirements.

With it, Trackingplan will automatically inform you any time the attribution data collected in your campaigns doesn’t meet the custom rules you have defined so you can get it fixed before compromising the performance of your marketing investments.

Let’s see some examples:

  • If the campaign contains the keyword “blackfriday”, the medium attribute cannot be ‘press’. If this combination is detected, please send me a warning.

But not only campaigns are supported. In fact, you can also set up validations for any of your landings, referrals, pages, mediums, sources, and event attributions. Some examples can be:

  • All the landing pages should follow this specific format "/section/abc.
  • The event AddToCart should only originate on these 3 pages: a, b, and c. If this event is detected on a page that is not listed above, send me a warning.
Just ask which validation rules you would like to add and we will implement them for you.

← Previous

Discover ReleasesDiscover Releases

Next →

Daily DigestDaily Digest