v15 Segmentation vs. Multi-Suite Tagging [SiteCatalyst]

- Adam Greco

With the arrival of SiteCatalyst v15, one of the most intriguing questions is whether or not clients should take advantage of segmentation and replace the historic usage of multi-suite tagging. This is an interesting question so I thought I’d share some of the things to think about…

Multi-Suite Tagging Review

As a quick refresher, if you have multiple websites, it has traditionally been common to send data to more than one SiteCatalyst data set (known as report suites). The benefits of this multi-suite tagging were as follows:

  1. You could have different suites for each data set (i.e. see Spain data separately from Italy data)
  2. If you sent data to many sub-suites and one global (master) report suite, you could see de-duplicated unique visitors from all suites in the global report suite
  3. If you wanted to, you could see Pathing data across multiple sites in the global report suite to see how people navigate from one website to another
  4. You could create one dashboard and easily see the same dashboard for different data sets in SiteCatalyst or in Excel
  5. You want to see metrics at a sub-site level, but also roll them up to see company totals in the global report suite

As you can see, there are quite a few benefits of multi-suite tagging and most large websites tend to do this as a best practice. Of course, where there is value, there is usually a cost! Since you are storing twice as much data in SiteCatalyst, our friends at Omniture (Adobe) have always charged extra for doing this, but normally these “secondary server calls” are charged at a dramatically reduced rate.

...

-------------

Read the full post at Web Analytics Demystified.