By uploading your campaign cost data, you will have the ability to create calculated metrics like cost per acquisition and net revenue. To input cost data, please do the following:

1. Go to Admin
2. Next Navigate to Reporting Suites -> Edit Settings -> Marketing Channels -> Marketing Channel Costs
3. Click on Add Cost Item
4. Within The Marketing Channel  Cost window, input the desired name for the cost/budgetary data being input
5. Next, choose the channel to which you would like this cost applied to (whether that be paid search, display, email, etc).  Here you will also be able to select whether you want the cost to be applied on a first or last touch basis.  First touch cost is a one time new engagement while last touch is selected for click throughs and is the preferred selection among users
6. You will then have the opportunity to select the desired date range for your cost data
7. An important step is the selection of the type.  There is Rate vs. One time Cost.  I will dive into the difference between these shortly
8. Lastly, you have to select how you want the cost to be distributed.  It can be done by whatever metric you wish to have it by (click throughs, registrations, etc)

Going back to the difference between rate vs. one time cost:

• Rate – If your cost is tied to a re-occurring metric (say paying Affiliates $30 cost per acquisition), you will want to select this to calculate the rate amount per each conversion (or other metric this is tied to)
• One time cost – If you have a “one time” event that you want to see net revenue and CPA for.  This could be in the case that you have a TV spot that is being run in all major DMAs but will only have one tracking code (vs. several). This is where the one time cost would be applied

That’s it! Following those steps will help you add in cost and budgetary data into your marketing channels reports within Omniture SiteCatalyst to start seeing and taking action off of net revenue.

Passing in the user’s GMT time is pretty easy by leveraging the getTimezoneOffset() method.  This method will calculate the time difference between GMT and local time in minutes.  But, you are saying you don’t need the minutes but just the hour that it is.  Well, below is the code that you can use:

var curdate = new Date();

var gmtHours = -curdate.getTimezoneOffset()/60;

Now instead of returning the timezone difference in minutes you have it returned in hours.  So now you can easily insert it into your plugin.  An example of this is below:

var curdate = new Date();

var gmtHours = -curdate.getTimezoneOffset()/60;

var temphr = s.getTimeParting(‘h’,gmtHours,curdate.getFullYear());

var tempday = s.getTimeParting(‘d’,gmtHours,curdate.getFullYear());

s.propX = tempday+”|”+temphr;

That’s it! Very simple and easy but now allows your time parting report to reflect the correct GMT that this is coming from and makes things dynamic.  You will also notice that I am dynamically passing in the year for the plugin.  This is a good rule of thumb so that when the calendar changes, you won’t have to now redeploy the code to increment year by one.

The first type is the Standard rollup report suite.  This is the type that you can easily enable within the admin interface.  For more instructions on how to set that up within the admin section, please take a look at: Omniture SiteCatalyst Helpful Tip – Creating Rollup Report Suites.

The standard rollups include:

• Unique Visitors
• Visits
• Page Views
• Site Sections
• Channel
• Technology (all reports associated with)
• Servers
• sProps (all traffic captured values)

The next two types, commerce and premium, cannot be enabled within the admin interface.  You will need to work with ClientCare to get this turned on for your site.

The commerce rollups include:

• Products (cross sell, categories, conversions and averages)
• Purchases (units, orders, revenue, conversions and averages)
• Campaigns (tracking code, elements, conversions and averages)
• Customer Loyalty (zip code, state, DMA, time zone, languages, etc)
• Shopping Cart Activity (checkouts, adds, removes, views, starts, etc)

The premium rollups include:

• The full domain
• Languages
• sProps (all traffic captured values)
• Countries
• Time Zones

There are four things to think about when making the decision:

1. If you are on a budget and do not need the ability to correlate, pathing, or to de-dupe the data being captured, stick with a rollup report suite
2. If you are looking for the ability to perform pathing, correlations, need the data to be de-duped and do not want to be hamstrung by data limitations, then you will need to take on multi-suite tagging since this functionality isn’t supported within rollups
3. If you have a very large suite, are looking to break it up into smaller more manageable “chunks” and do not have the available budget to pay Omniture for secondary server calls (i.e. multi-suite tagging), you can look to leverage ASI (advanced segmentation insight) slots to create smaller reporting suites for your business needs
4. If you do not have to see pathing between reporting suites (since your visitors dont path between the tagged sites) but visit more than one of them with some frequency and you want to see a true visitor count for these individuals, then you should select multi-suite tagging

Consider your needs and then map out the pros and cons with the differences between each method.  If you need any assistance, please feel free to reach out to me.

Rollup Report Suites:

• There is no additional cost associated with rollup reports (depending on your contract so please double check with your account manager)
• No ability to correlate
• No dedupping of uniques.  Rollups cant do this because the visitor is counted as a unique visitor to each of the sites that are feeding into the rollup.  There is just no way to identify the visitors to each site as the same person
• The data isn’t live and is processed on a nightly basis.  This won’t be a good option if you are looking for real time data.  If, however, you can look at data 24 hours old or older, then this will work for you
• No cross domain campaign tracking
• No ability to see pathing.  Paths cannot be summed together because the visitors that are accessing the sites are being issued differing unique visitor IDs for each site so it makes it impossible to tell if its the same person that visited all of the sites or someone different accessing each site separately
• No ability to see pages reports within this suite.
• Ability to aggregate historical data without needing the data warehouse

Multi-Suite Tagging:

• There is a cost associated with implementing this.  The cost is an additional 50% CPM.
• The data is live and you do not need to worry about having it processed after the fact (you can take action on it in real time)
• No ability to aggregate historical data.  Using data sources, you could upload historical data to the top level suite, but there would be no dedupping of the data that was uploaded
• Ability to dedupe uniques.  If the same visitor visits the reporting suites that make up the multi-suite, that visitor is only counted once not three times
• Ability to perform pathing analysis across the reporting suites.  This option provides full pathing functionality between any of the pages in any of the reporting suites making up the multi suite tagging
• Ability to correlate/subrelate
• Ability to view the pages report
• Ability to perform cross domain campaign tracking.  Tracking codes picked up on site can be given credit for a conversion/success event trigger on another

1. Log into Omniture SiteCatalyst
2. Click on Admin
3. Navigate to Report Suites
4. Then select Create New Rollup
5. Name the report suite – This should be something that easily tells you that it is a rollup report and which RSIDs are folding into it
6. Select the time zone that the roll up report suite should have
7. Locate and drag the desired suites into the newly created rollup suite

That’s it.  Once you take the above steps, you will now have a rollup report suite that will house the necessary data you wanted it to.

Traffic variables (s.prop):

• Show what the most popular recorded item is
• Value counters that record the number of instances for a specific value
• Show how much traffic is coming in from visitor segments
• 75 variables available
• 100 byte limitation
• Case sensitive

Conversion variables (eVar):

• Persistent values that can follow the visitor between pages and visits
• 255 byte limitation
• Values are tied to conversion events (conversion metrics)
• Up to 75 variables available
• Ability to customize the expiration and allocation within the admin area

Success events (s.events):

• Show how many times did people complete the desired activity on the site
• Available in 3 different flavors – Currency: captures a currency value; Counter: increments by one each and every time the event is executed; Numeric: increments by any value necessary
• 100 events available

Using transaction IDs to tie offline data to online, you can leverage data sources to integrate:

• Product Cost
• Call Center Information
• Product Returns
• Leads
• Web Logs
• Traffic Metrics

This helps you understand as a whole.  Think of how your customers interact with your site.  They first search or get referred from another domain; they land on your site peruse and then purchase; then return the product via phone.  Both the pre-click data (searches prior to last one that drove to your site, impressions, cost, etc) and “after-the-sale” information (returns, call center data).

You can use Data Sources to help understand the pre-click data by importing the data via the search engine or ad network.  This will make it possible to calculate ROAS (Return on Ad Spend) by bringing in the cost data and dividing it by revenue (Revenue/Cost).  You can also use it to help understand the “after-the-sale” data to get a more accurate ROAS picture by bringing information such as Return Revenue or Return Units.

Now with Data Sources you can get that end to end or 360 degree view of your business to take action off of this increased insight.

1. Log into SiteCatalyst
2. Navigate to the Admin Console
3. Within the Admin Console go to Report Suite
4. Decide whether you want to create the reporting suite from a template (choose between aggregator/portal, commerce, content & media, financial services, job portal, lead generation, subscription and support media) or from an existing reporting suite.  With the existing reporting suite you will be able to copy many of the settings over from the existing suite.  Within the notes section below, I will list out the items that do not copy over.
5. Enter in your Report Suite ID (RSID)
6. Enter  your Site’s Title (Name)
7. Select your specific Site’s Time Zone
8. Enter the Base URL (the domain this code will reside on), Default Page (the home page), and the Expected Go Live Date
9. Estimate the number of Page Views you expect a day.
10. Select the Base Currency (defaulted to US dollars)
11. Click “Create Report Suite” and you are done!

Please Note:The following items cannot be copied over:

• Pathing reports on traffic variables
• Visit and Visitor metrics in conversion reports
• Participation metrics

1. The ability to correlate traffic and conversion variables – The data warehouse allows you to see multiple report breakdowns over both Conversion and Traffic variables (data). Unfortunately, this cannot be done in SiteCatalyst due to the fact that you can only break down conversion reports by other conversion reports as well as traffic reports by other traffic reports and not intermingle.
2. Able to perform historical segmentation – Within the data warehouse, you can look at older time periods and slice and dice data by say certain segments.
3. Not limited by defined correlation/subrelations set up within SiteCatalyst – If you want to break a traffic variable down by another traffic variable and haven’t set up the correlation within SiteCatalyst, you are out of luck.  However in the data warehouse this isn’t a limitation.  A good rule of thumb is if you don’t look at the correlation/subrelation often within SiteCatalyst, you should leverage the data warehouse so that you keep the processing of reports within SiteCatalyst fast.
4. Ability to pull in additional metrics – Within the data warehouse, you can pull unique visitor reports for custom data ranges. You can also add in metrics that are not available within SiteCatalyst like looking at page views in geo reports.