To edit the file to update the settings, please take the following steps:

1. Open up Insight
2. Navigate to the Admin section
3. Within the Admin area, go to Dataset and Profile -> Servers Manager
4. Right click on the main insight server and select Server Files
5. Right click the check mark in the server name and select Make Local
6. Maximize the Access Control Group and then maximize the Cluster Servers
7. Right click on Members and click Add New
8. Select New Member
9. Within the new member screen, input the server’s IP address for Insight
10. Save modifications

That’s it! With this in place you will be able to safely edit the access control.cfg file to update cluster server access control groups.

 Please Note:

The IP address has to be numeric and not just its friendly name.

Let’s say their is a view that all end users at your organization uses but its not currently set up as the default.  To change the default visualization, please take the following steps:

1. Open up the workspace that you wish to change the default visualization
2. Create a visualization containing the data that you want to appear in the new default visualization
3. Right-click the top portion of the border and then click Save
4. Click Context and then click Dimension Legend
5. In the File Name field, type the dimension name. Please remember that whatever name you have for the .1d file is the name you must have for the dimension.  You will also need to ensure that the file ends with the .1d file extension
6. Click Save. The file is saved to the User\profile name\Context\Dimension Legend folder. The next time that you click that dimension from the Schema Interface, the visualization that you defaulted the view to will display

Please Note:

To make this change available to all users of the working profile, you will need to open up the profile manager, and click on Context and then click Dimension Legend.  Within the dimensions legend, right click on the check mark next to the file name of the new callout in the User column and click Save to the working profile name.

Before we go any further, lets take a step back and define what a filter is.  A filter is an expression that defines a subset of data. Within the site profiles, the session filter is set up to include all users (visitors) that have a flag tied to them.  This flag is the vistorized flag.  When it is set to 1, it tells Insight that a tracking cookie for that particular user exists.  Within the default broken session filter.filter file provided by Omniture, you will need to modify the file with the expressions necessary to tackle your particular problem.

To make changes, you will need to adjust this value (and others depending on your needs).  To edit the filter file manually, please do the following:

1. Open the profile manager
2. Click Filters
3. Locate and select the file that you want to edit (in this case broken session filter.filter)
4. Right click the check mark the file and click Make Local (if the file resides on the server)
5. Right click the filter for User
6. Click open -> notepad
7. Edit the file

That’s it! Now you are able to edit your filter files to suit your specific needs.

Please Note:

I would highly suggest brushing up on your syntax for filtering expressions prior to editing the file.  If you are at a loss, contact your account rep or ClientCare for more assistance if you want to leverage Omniture’s help, or feel free to contact me and I will assist.

Omniture Insight provides the ability to copy workspaces and text notes from the interface to ClientCare. To set this up (and copy the data from Insight into say a word document), please do
the following:

1. Open up the desired workspace that you wish to copy to ClientCare
2. Within the window, right click on the top border of the workspace
3. Select Ouput -> Copy Image (to copy over a workspace) or Copy (for text)
4. Select the background options
5. Place the copied text (or image) into the word document
6. Save or send to the desired recipients

That’s it! By doing this, you will be able to copy workspace or text over from Omniture Insight and place in a word doc to send to ClientCare or anyone else.

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.