How to use
With Trackingplan, you can be automatically notified whenever your properties, events, and user acquisition data don’t conform to the values you have specified.
These are the 3 ways you can use to validate your data:
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.
To write Enums for a property, click on its type field and select Enum in the drop-down menu.
If this is the first time you create an Enum, select Create New Enum. Otherwise, you can reuse it, edit it, or clone it from another property and use it on this one.
In the next panel, you can name your new Enum and write the corresponding values. Yet, you can also autocomplete your Enum with the values that have been observed in the last 30 days in this 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. You can always add it to the Enum by editing it, or fix it in case it is an error.
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 a regular expression from another property.
In the next panel, you can name your new regular expression (e.g.: percent scrolled) 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.
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.
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 firstname.lastname@example.org and we will help.
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 email@example.com which validation rules you would like to add and we will implement them for you.