The Adobe / Omniture SiteCatalyst Analytics tool is one of the most robust and feature rich digital measurement tools in the market and, as such, the implementation can be one of the most challenging and complex as well, but it does not have to be. In the recent Forrester “Understanding Tag Management Tools and Technology” report, ease of use & ease of implementation were cited as the top reasons for selecting a tag management system.
Having used all the major tools in the market I can tell you first hand that for most Tag Management Tools that is a valid and critical request. Some tools require you to modify the tracking code for the vendor, use a rigid pre-built template, or even strip out all the html scripts and do some serious modifications such as inverting the code just to get the basic code to fire. And that’s not even talking about doing any of the more complex event based or interstitial tracking. I know what you are thinking…I’m now an “evil vendor” myself and have spent too much time drinking the Satellite Kool-Aid. But I’ve spent the last few year waist..er..neck deep in working with the other tools; I have a pretty good grasp on the features and limitations of other solutions, and how Satellite is different. So let’s look at what it takes to get the basic Adobe / Omniture SiteCatalyst tracking code in place using Satellite.
*Note: In a previous post, To Host or Not To Host, I talked about the hosting options that Satellite offers you. The steps outlined below do NOT change depending on the hosting option that you select. *
Satellite TMS SiteCatalyst Implementation Guide
Step 1: Copy the s_code from the Adobe Admin Console
Copy everything as it is, no need to change anything or invert the code.
Step 2: Add the tracking code to Satellite
Once you are logged into Satellite and viewing your web property, select the “Add a Tool” button. Choose SiteCatalyst from the Tool Type drop down and then you will enter in your production and staging report suite ID’s. Once that is filled out, select the “Create Tool” option.
Now that the entry for SiteCatalyst has been created you will see a set of options presented to you. Expand the General section and move down to the s_cod
e section and select Satellite Managed.
> *Note: Satellite provides you the option to self host the s_code.js file from Adobe/Omniture if you need to do this. If you are adding Satellite to an established and robust implementation you might choose to point Satellite to use your existing s_code file to start with instead of migrating everything at once.*
Once you select the “Open Editor” button you will see a modal window that you can paste in the the s_code that you copied in step 1. After you paste the code in, select “Save and Close”
There are lots of other options on the main configuration page and we will explore those more in future posts but the only thing you need to know about them today is all the other settings are optional. Satellite allows you to open the code editor to tweak any of the settings just like a traditional implementation, or you can use the options on the main screen to override any of the settings here. You get to choose what level of tinkering with the code that you are most comfortable with. We are not going to force you into using a template that you are not able to edit. It is your code and your site, manage it as you see fit.
## **Step 3: Place the Satellite embed code on your site**
Now that you have the s_code saved and configured in your web property you need to get the embed code placed on your staging & production web servers. This too is a simple process. From the main menu, select the “Embed” option and navigate to the hosting option that you are using.
For every hosting option there are four code snippets you will need to get from this screen. Staging & Production header & footer code. Why two different versions? Having two distinct code libraries offers you something no other TMS can provide. Peace of mind that when you are developing and testing rules in staging there is no accidental way that anything that is not approved and ready to go will end up in production and potentially impact not only your data quality, but site performance as well.
After you add the header and the footer code to your servers you are ready to test the code on your staging server. Once you are happy you can approve the code and publish the changes to your production site and SHAZZAM!….you have just implemented the base Adobe / Omniture SiteCatalyst code on your site with Satellite. Congratulations!
***Note:** Not counting the time is take you to deploy the embed code to your staging & production servers this whole process should take you less than ten minutes.*
If you have any questions or would like to see a demo of how Satellite can help you with your digital measurement initiatives or to schedule a demo to see all of the features, email me rudi(at)searchdiscovery.com.