A Stricter Approach
Once you compose a pattern, Tracking First initiates a sequence to discover how that pattern should be classified. If you already know how it should be done, how do you make sure that users don’t end up coloring outside the lines you’ve drawn? Is there any way to apply pattern rules and constraints? Yes — codes can be composed to meet your organization’s unique naming conventions and taxonomy.
Delegation and Control
These questions echo the biggest concern that we’ve heard from Analytics Administrators when we dangle the prospect of delegating the task of code creation back to individual marketers: how can I relinquish control of the classification tables without compromising the integrity of the reports?
Auto-Classification Off Switch
Our answer is to offer Pattern Rules and Constraints, available for any pattern you create. By unchecking the default Auto-Population tool, you will be shown a Constraints dialog, where you can lay down the rules for how that pattern will behave in the Classification stage.
For instance, you can determine which classification fields will be shown, and how they will be populated–choose from single values or drop-downs. If strict rules are applied, users with access to this pattern will only be able to advance in the process once they complete the table as you’ve designed it.
Through proper management of patterns, user groups, and permissions, you can ensure that all of the data flowing from Tracking First into your analytics vendor complies with the reporting strategy you’ve put into place.