Back to basics – SAINT classifications

[Jahangir147]

I’ve come across a few clients now that either aren’t using SAINT, are using it in a limited way, or are using it for campaigns only. Maybe people are confused by what it does, or daunted by it, or just don’t know what it can be used it for. It’s got uses that extend way beyond campaigns.

So, in this post, I’ll re-cap a bit about what SAINT actually is, and how it can be used, across a whole multitude of things.

And classifications can be used for millions of records. We recently uploaded a very large list of customer ID’s and segments per customer, which enables some fascinating insight into customer behaviour.

SAINT – the acronym.
To get this out the way, SAINT stands for SiteCatalyst Attribute Importing and Naming Tool. It’s a way to classify a SiteCatalyst variable into more meaningful terms, and enabling you to group them together in certain ways.

What’s a Classification?
Basically, when you “classify” a SiteCatalyst variable, you are extending tonga email list 26,869 contact leads the information available on that variable through additional meta-data.

Classifications are most frequently used on campaigns. When you run a campaign you track it through a campaign code – a unique code that you set to identify that specific campaign element, such as “eml123”. You add the tracking code to a link that’s driving traffic to your site.

Your s_code is most likely looking for any page query string to contain the parameter “cid”, and once it sees it, it’ll put the value “eml123” into the s.campaign variable.

It only needs to see it once…typically on the landing page. As long as it saw it and recorded it then you can see success events further down track, tied back to the campaign code.

Looking at your campaign reports, you’ll see one called “Tracking Code”, and in there, you’ll see all of the unique values that have been passed through the s.campaign variable.