Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Coffee Break: Join us on Wednesday, April 5th at 10am PT to chat with Ben Gaines, Director of Product Management for Adobe Analytics. Ben will be online to answer your Analytics and Adobe Summit questions.

Automatic, rule-based SAINT classifications based on specific criteria




SiteCatalyst should offer the ability to automatically classify "key" values that match a specified set of criteria. For example, if the key contains "12345," the campaign is automatically set to "Winter 2010 Campaign." This should also allow the use of wildcards (e.g., "12*45") and/or regular expressions.



Level 5


The ability to classify using a wildcard would help us significantly. Since we have consistent naming conventions for our campaign tracking paramters, this feature will allow us to efficiently classify our campaigns.


Level 1


I have found that Omniture often suggests filling eVars and sProps with concatenated data.  An example would be, if I were Honda, I may pass the following into a single prop: acura:2010:suv:mdx  While this will get you good info about MDX, what if you also wanted to get at info for just SUVs, or just for Acura?  You would have to export a file, create a saint file, then upload a saint file.  But what if your data set changes more frequency than car models do.  you are now left in a situation where you have to constantly manage this.


Instead there should be a mapping feature.  This mapping feature should allow a user to declare a delimiter (ok if application dictates this but nice to be customizable) and then define the structure of your data.  Using the above example, the structure is {Make}:{Year}:{Class}:{Model}


At a minimum the application should then map each item to a SAINT classification.  However it would be even more powerful if the user then had the ability to map different combinations of values into SAINT classifications.  Ex.  Maybe Honda wants to see a summary by {Make}:{Year} or {Make}:{Class}.


Once the configuration is done, the application would then take care of moving the data into the SAINT.


The process should also have a way to flag data issues.  Ex.  The above example has 3 colons.  Any time a record has more or less, it should NOT push to SAINT and be flagged as bad data.  Maybe the push to SAINT would be a manual process and at the time of the push, you can select an option to download data errors.  Note that data errors should only be downloaded if they are completely unclassified.


Here is the process I envision:

1)      Create the SAINT classifications for the desired sProp/eVar. 

2)      Define structure for data that will be populated in the sProp/eVar. 

3)      Using the defined structure, map the data into the defined SAINT classifications.

4)      Push data and download data issues to be manually classified and uploaded.


This feature would be a huge help for us as we would be able to repurpose a number of different sProps as we would not need different props for each combination of data.


Level 4


In our current workflow, this could free up an immense amount of time. Another strong "yes" to get this implemented please.


Level 3


We also spend a good deal of time with classifications - so a real strong 'yes please' to get this implemented.


The larger the data to upload becomes, the longer it seems to take. However there is no easy way to see the status of the processing, which leads to overwrites and even more delay.


Level 1


SAINT classifications should echo similar logic you would use to create segments, or within the Marketing Channel logic. We have to routinely update our classification manually (as much as weekly)  ...


For example, we can create a marketing channel "Email" using logic on the tracking code:

1.) Campaign Contains "Email_*"

2.) Referring Domain Contains "mail." OR "webmail."


The ability to have SAINT codes be "smart" in the same way would save hours of manual labor.


Level 1




This is a great idea. Most advanced digital marketing teams have created a logical structure to their tracking codes and this would make it so much easier to classify


Level 4


Another person who would like to use a wildcard.  Thank goodness, I can use excel formulas to do this, but it is a big nuissance.


Level 3


This has been "under review" for a year and a half now.  Is there still some chance it will happen and/or will it only happen in SiteCatalyst 15?