The Adobe / Omni­ture Site­Cat­a­lyst Analyt­ics tool is one of the most robust and feature rich digital measure­ment tools in the market and, as such, the imple­men­ta­tion can be one of the most chal­leng­ing and complex as well, but it does not have to be.  In the recent Forrester “Under­stand­ing Tag Manage­ment Tools and Tech­nol­ogy” report, ease of use & ease of imple­men­ta­tion were cited as the top reasons for select­ing a tag manage­ment system.

Screen Shot 2012-12-19 at 7.53.13 PM

Having used all the major tools in the market I can tell you first hand that for most Tag Manage­ment Tools that is a valid and crit­i­cal request.  Some tools require you to modify the track­ing code for the vendor, use a rigid pre-built template, or even strip out all the html scripts and do some serious modi­fi­ca­tions such as invert­ing 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 inter­sti­tial track­ing. I know what you are thinking…I’m now an “evil vendor” myself and have spent too much time drink­ing the Satel­lite 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 limi­ta­tions of other solu­tions, and how Satel­lite is differ­ent.  So let’s look at what it takes to get the basic Adobe / Omni­ture Site­Cat­a­lyst track­ing code in place using Satel­lite.

Note: In a previ­ous post, To Host or Not To Host,  I talked about the hosting options that Satel­lite offers you.  The steps outlined below do NOT change depend­ing on the hosting option that you select.

Satellite TMS SiteCatalyst Implementation Guide

Step 1:  Copy the s_code from the Adobe Admin Console

Screen Shot 2012-12-21 at 10.44.46 AM

Copy every­thing as it is, no need to change anything or invert the code.

Step 2:  Add the tracking code to Satellite

Screen Shot 2012-12-21 at 10.45.26 AM

Once you are logged into Satel­lite and viewing your web prop­erty, select the “Add a Tool” button.   Choose Site­Cat­a­lyst from the Tool Type drop down and then you will enter in your produc­tion and staging report suite ID’s.  Once that is filled out, select the “Create Tool” option.

Screen Shot 2012-12-21 at 10.46.03 AM

Now that the entry for Site­Cat­a­lyst has been created you will see a set of options presented to you.  Expand the General section and move down to the s_code section and select Satel­lite Managed.

Note:  Satel­lite provides you the option to self host the scode.js file from Adobe/Omniture if you need to do this.   If you are adding Satel­lite to an estab­lished and robust imple­men­ta­tion you might choose to point Satel­lite to use your exist­ing scode file to start with instead of migrat­ing every­thing at once.

Screen Shot 2012-12-21 at 10.47.16 AM

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”

Screen Shot 2012-12-21 at 10.49.31 AM

There are lots of other options on the main config­u­ra­tion 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. Satel­lite allows you to open the code editor to tweak any of the settings just like a tradi­tional imple­men­ta­tion, or you can use the options on the main screen to over­ride any of the settings here. You get to choose what level of tinker­ing with the code that you are most comfort­able 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 config­ured in your web prop­erty you need to get the embed code placed on your staging & produc­tion web servers.  This too is a simple process. From the main menu, select the “Embed” option and navi­gate to the hosting option that you are using.

Screen Shot 2013-01-01 at 11.04.02 AM

For every hosting option there are four code snip­pets you will need to get from this screen. Staging & Produc­tion header & footer code.  Why two differ­ent versions?  Having two distinct code libraries offers you some­thing no other TMS can provide.  Peace of mind that when you are devel­op­ing and testing rules in staging there is no acci­den­tal way that anything that is not approved and ready to go will end up in produc­tion and poten­tially impact not only your data quality,  but site perfor­mance 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 produc­tion site and SHAZZAM!….you have just imple­mented the base Adobe / Omni­ture Site­Cat­a­lyst code on your site with Satel­lite. Congrat­u­la­tions!

Note: Not count­ing the time is take you to deploy the embed code to your staging & produc­tion servers this whole process should take you less than ten minutes.

If you have any ques­tions or would like to see a demo of how Satel­lite can help you with your digital measure­ment initia­tives or to sched­ule a demo to see all of the features, email me rudi(at)searchdiscovery.com.