<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>WebAnaBlog.com</title>
	<atom:link href="http://www.webanablog.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webanablog.com</link>
	<description>Analytics Insights and Other Web 2.0 Thoughts from My Random Stream of Consciousness</description>
	<lastBuildDate>Thu, 07 Jan 2010 21:15:19 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Comparative Analysis: Omniture SiteCatalyst, Google Analytics, &amp; Yahoo Web Analytics</title>
		<link>http://www.webanablog.com/2010/01/07/omniture-google-yahoo-analytics-comparison/</link>
		<comments>http://www.webanablog.com/2010/01/07/omniture-google-yahoo-analytics-comparison/#comments</comments>
		<pubDate>Thu, 07 Jan 2010 19:49:51 +0000</pubDate>
		<dc:creator>ABatten</dc:creator>
				<category><![CDATA[Omniture SiteCatalyst]]></category>
		<category><![CDATA[Google Analytics]]></category>
		<category><![CDATA[Yahoo Analytics]]></category>

		<guid isPermaLink="false">http://www.webanablog.com/?p=25</guid>
		<description><![CDATA[This post will compare the various features and capabilities of the Omniture SiteCatalyst, Google Analytics, and Yahoo Web Analytics applications, and determine how appropriate each is for the measurement and analysis of website traffic. While writing this I will attempt to show no bias towards one application over another, and if I am presenting my opinion, I will be sure to point this out. The analysis is intended only for comprehensive competitive analysis.

Overview

Omniture SiteCatalyst has long been a major player in the analytics market, meeting the needs for many large, corporate clients. Google Analytics emerged just over 3 years ago after Google purchased the analytics solution Urchin, and as of the date of this posting (1.7.2010)  Yahoo! Web Analytics is still in a beta stage, only allowing access to certain small business customers and News Consortium members.

The Omniture, Google, and Yahoo solutions rely on the standard JavaScript/Image beacon methods to measure web traffic. In short, each time a page is loaded, a piece of JavaScript builds an image request that is sent to a data-gathering server. The image request consists of query parameters with data about the page view. The query parameters are then parsed by the analytics applications and input as data into the appropriate traffic reports.]]></description>
			<content:encoded><![CDATA[<div align="right" style="float:right;padding:0px 0px 5px 5px;"><a name="fb_share" type="box_count" share_url="http://www.webanablog.com/2010/01/07/omniture-google-yahoo-analytics-comparison/"></a></div><div class="tweetmeme_button" style="float: right; margin-left: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.webanablog.com%2F2010%2F01%2F07%2Fomniture-google-yahoo-analytics-comparison%2F"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.webanablog.com%2F2010%2F01%2F07%2Fomniture-google-yahoo-analytics-comparison%2F" height="61" width="51" /></a></div><p>This post will compare the various features and capabilities of the Omniture SiteCatalyst, Google Analytics, and Yahoo Web Analytics applications, and determine how appropriate each is for the measurement and analysis of website traffic. This post is likely to get quite wordy, so I apologize in advance.  This analysis is intended to be comprehensive for evaluating analytics solutions.</p>
<p>While writing this I will attempt to show no bias towards one application over another, and if I am presenting my opinion, I will be sure to point this out.</p>
<h2>Overview</h2>
<p>Omniture SiteCatalyst has long been a major player in the analytics market, meeting the needs for many large, corporate clients. Google Analytics emerged just over 3 years ago after Google purchased the analytics solution <strong>Urchin</strong>, and as of the date of this posting (1.7.2010)  Yahoo! Web Analytics is still in a beta stage, only allowing access to certain small business customers and News Consortium members.</p>
<p>The Omniture, Google, and Yahoo solutions rely on the standard JavaScript/Image beacon methods to measure web traffic. In short, each time a page is loaded, a piece of JavaScript builds an image request that is sent to a data-gathering server. The image request consists of query parameters with data about the page view. The query parameters are then parsed by the analytics applications and input as data into the appropriate traffic reports.<span id="more-25"></span></p>
<h2>Cost</h2>
<p>The <strong>Omniture SiteCatalyst </strong>application is extremely robust, providing expansive and expandable measurement capabilities, but such features do not come cheap. It is not uncommon for corporate clients to spend hundreds of thousands of dollars per year to gain access to the Omniture SiteCatalyst system.</p>
<p>While initially not nearly as robust as Omniture, <strong>Google Analytics</strong> became instantly competitive by offering their analytics solution <em>free of charge</em>, provided that a website stays within the set limit of 5 million page views. For sites that have in excess of 5 million page views per month, Google Analytics is free as long as the site has an associated, active AdWords account.   Since launching the solution publicly in November 2005, Google has made significant improvements to the application. Improvements and limitations of Google Analytics will be discussed later in this post.</p>
<p>Like Google, <strong>Yahoo Analytics</strong> is also a free solution, but Yahoo differs from Google’s application in that the page view limitation per-site is much greater (250 million page views per month vs. 5 million per month for Google Analytics.)</p>
<p><strong>Advantage: <em>Yahoo Analytics</em></strong></p>
<h2>Dashboards / Customized Reports</h2>
<p>SiteCatalyst, Google Analytics, and Yahoo Analytics all provide extensive capabilities for custom reporting and automated reports. This has long been a feature inherent in SiteCatalyst, and Google Analytics made numerous upgrades and interface improvements in the last 12 months which allow for this capability. In each of the applications, users can easily create and download customized reports which show traffic data alongside other important metrics. Reports can be downloaded from all systems, and automated emails can be scheduled to send reports in numerous formats.</p>
<p>Google Analytics can email reports in the following formats: PDF, XML, CSV, and TSV. Where Google falls a bit short, however, is when it comes to having multiple dashboards for various purposes. Currently, Google Analytics only allows users to have one default report/dashboard for each site (per login.) The default dashboard can be customized on a per-site basis within the same user login, however if a user wishes to have multiple dashboards for the same site, a separate login must be used.  <em><strong>In my opinion</strong></em>, such limitations of Google should not greatly affect the final recommendation for one product or the other. Dashboards can be scheduled for delivery in reports that are well-formatted, informative, and easy to read.</p>
<p>Reports in Yahoo Analytics can be downloaded or scheduled for delivery in HTML, Excel, PDF, or CSV. Scheduled reports in Yahoo Analytics can be configured for delivery daily, weekly, or monthly. An enhancement request has been in made for hourly alerting/reporting, and this is currently in the Yahoo queue. For daily reports, Yahoo allows for configuring delivery at any hour of the day. Downloaded and emailed reports can be configured to display up to 200,000 rows in Yahoo Analytics.</p>
<p>Omniture SiteCatalyst allows for emailing reports in Excel, PDF, HTML, and Word. When downloading reports, all of the same options are available except HTML. Unlike Google or Yahoo, Omniture SiteCatalyst is able to schedule <em>hourly</em> reports. Omniture also has “Data Extract” functionality which enables delivery of an unformatted report in .csv format for very large data requests. The caveat to Omniture’s custom report capability is that during periods of very heavy traffic, delivery of automated reports may be delayed. In my experience, some reports may fail altogether during periods of heavy traffic.</p>
<p><strong>Advantage: <em>Omniture SiteCatalyst</em></strong>*</p>
<p>*Omniture gets the edge because of the expanded capability for ‘hourly’ scheduled reports. If/when Yahoo Analytics implements hourly alerting/reporting, I believe Yahoo may have the edge here, though it is a tossup.</p>
<h2>Application Support</h2>
<p>Omniture relies heavily on a support network known as Omniture Client Care for answering support requests and enabling additional features. As part of the support system, Omniture also makes available documentation for virtually every piece of functionality and common questions. Included with acontract are “supported users”, those allowed to contact Omniture Client Care.  Omniture also has a <a href="http://twitter.com/omniturecare">Twitter account</a> for support that I have found <strong>extremely helpful</strong> and <strong>responsive</strong>.</p>
<p>Because it is a free solution, there are no guarantees of support when using Google Analytics, however there is a very large community of power users and Google support personnel that regularly monitor the Google forums to assist with issues. In fact, the Google Analytics help forums and other instructional documentation are extremely helpful, perhaps more-so than Omniture SiteCatalyst documentation, but <em><strong>this is only my opinion</strong></em>. In addition, there are Google-Certified consulting  companies which provide professional services for a fee. The key difference between both applications is that with Omniture Client Care, a supported user can get immediate access to personal support using the 24 hour support line.</p>
<p>Being a relatively new solution, Yahoo Analytics is still in the process of establishing a support network. It is not clear if Yahoo will have a personal level of on-demand support, or if a support “network” will exist, similar to that of Google Analytics. In the meantime, Yahoo has extensive documentation that appears to match that of Google Analytics in quality and scope.</p>
<p><strong>Advantage: <em>Omniture SiteCatalyst</em></strong></p>
<h2>User &amp; Access Management</h2>
<p>Omniture SiteCatalyst provides extremely robust user management tools, allowing administrators to assign access at many different levels. All contact information is within the Administrators interface, and passwords can be reset easily. Access to reports is setup using “Groups” in SiteCatalyst. Groups are granted various privileges, and one or more report suites can be assigned to individual groups. This level of organization can be both helpful and cumbersome, depending on circumstance.</p>
<p>Access rights in Google Analytics differ from Omniture SiteCatalyst in that users can only be given one of two levels of access/privileges (read-only or admin) to each website profile. Further, users can only be given access using a Google Account (as of this posting), and user contact information (phone number) is not stored on Google Analytics.</p>
<p>The Yahoo Analytics application makes user management fairly easy. Like Google Analytics, regular users are granted access to view reports on an individual site basis, rather than groups. Yahoo Analytics have four different levels of user rights:</p>
<ul>
<li>Administrator &#8211; Unrestricted      access to reporting, account and user management features.</li>
<li>Power User &#8211; Unrestricted      access to reporting, account and user management features, except for      editing or deleting Administrators.</li>
<li>User &#8211; Unrestricted access      to reporting, but they do not have access to account management or user      management features.</li>
<li>Restricted User &#8211; Access      to select reports and dashboards on an individual basis. Restricted Users      have no access to account or user management features.</li>
</ul>
<p>Unlike Google Analytics, a separate email address from the solution provider (test@gmail.com, test@yahoo.com) is <strong>not</strong> required to setup access in Yahoo Web Analytics.</p>
<p><strong>Advantage:</strong> <strong><em>Tie – Omniture SiteCatalyst &amp; Yahoo Web Analytics</em></strong></p>
<h2>Traffic Filtering</h2>
<p>Google Analytics allows for traffic filtering in a variety of different ways, including filtering by domain, IP address (or range), site section, geography, referrer, client browser settings, page title, etc.</p>
<p>Omniture and Yahoo Web Analytics do not have nearly the filtering capability of Google Analytics, but in both applications traffic can still be filtered by IP address or a range of IP addresses. The Omniture SiteCatalyst filtering options are sufficient for most website needs.</p>
<p>In addition to IP filtering, Yahoo Analytics also has the ability to exclude the current browser of an Administrator using cookie-based filtering. While this feature is admittedly pretty neat, I do not see it being used often as many ISPs use IP pooling.</p>
<p><strong>Advantage: <em>Google Analytics</em></strong></p>
<h2>Data Importing</h2>
<p>Known within the SiteCatalyst system as “Data Sources”, Omniture allows administrators to import data from various different sources, provided that the data is formatted correctly. As data cannot be <em>removed</em> from the system, there is inherent risk associated with such capability. Example usages of this feature include importing newsletter information to correlate with subsequent page views, as well as importing video usage data or mobile traffic (if not already tracked in SiteCatalyst).</p>
<p>Google Analytics and Yahoo Web Analytics currently do not have any way to import data into the system, so any external data must be analyzed separately.</p>
<p><strong>Advantage: <em>Omniture SiteCatalyst</em></strong></p>
<h2>Rollup / Multi-Suiting</h2>
<p>The ability to easily aggregate and analyze traffic across multiple websites is a very important consideration for corporate clients who must administer many different sites. There are two different methods that can accomplish this task: <strong>Rollup Accounts</strong> and <strong>Multi-Suiting (double/multi-tagging)</strong>. The ease with which aggregate data can be analyzed is also an important consideration.</p>
<p>Omniture SiteCatalyst provides features for both options for aggregating multi-site data. Via <em>multi-suiting</em>, SiteCatalyst tracking code can be configured to report data to more than one website profile (report suite.) Doing so allows SiteCatalyst to track overall page views across all tagged sites, determine unique visitors [not limited to one domain], and perform drill-down correlations for various traffic segments. The disadvantages to such an implementation are that each additional account ID that is tracked results in an additional server call to Omniture, and subsequently greater overall cost.</p>
<p>The alternative to multi-suiting in SiteCatalyst is to use <em>rollup accounts</em>. In Omniture, rollup accounts can be configured to report many of the same basic metrics as standard single-site reports, however there are a couple of significant limitations:</p>
<ul>
<li><strong>Correlations</strong> cannot be set up to report on specific      traffic segments, a feature that is possible in standard (non-rollup)      report suites.</li>
<li>Data in Omniture      rollup reports is always delayed approx. 2 days, as Omniture simply does      not have the ability to aggregate data from all accounts in real-time.</li>
</ul>
<p>Google Analytics does not have any rollup capability that will automatically aggregate data from selected sites, short of a multi-tagging option similar to Omniture’s <em>multi-suiting.</em> A similar feature that Google Analytics <em>does</em> have, however, is the ability to view some basic site metrics for a specified group of sites alongside others. Further, Google will display the data based on Day, Week, Month, or Year, and show the % change from the previous time-period. See screenshot below:</p>
<div id="attachment_29" class="wp-caption aligncenter" style="width: 491px"><a href="http://www.webanablog.com/wp-content/uploads/2010/01/google_analytics.jpg"><img class="size-full wp-image-29" title="google_analytics" src="http://www.webanablog.com/wp-content/uploads/2010/01/google_analytics.jpg" alt="Google Analytics Main Screen" width="481" height="454" /></a><p class="wp-caption-text">Google Analytics Main Screen</p></div>
<p>As previously mentioned, Google Analytics has the ability to use <strong>multi-tagging </strong>to gather traffic data across multiple sites. Resulting data can be analyzed in the same way as a single-site report, but unlike Omniture, Google is a free solution that does not charge a fee based on individual server calls (page views.)</p>
<p>Data rollup options for Yahoo Analytics are similar to that of Omniture. Websites (projects) can be grouped together for viewing very basic information across a number of different sites. The drawback to this method in Yahoo is that the only metrics available in a rollup are <strong><em>visits, monthly unique visitors, page views, time on site</em></strong> and a couple of e-commerce metrics. This list of metrics is far less extensive than the data that can be reported in Omniture rollups.</p>
<p>It is not clear yet if Yahoo Web Analytics will allow for a multi-tagging option for multi-site analysis, though it does seem likely.</p>
<p><strong>Advantage:</strong> <strong><em>Google Analytics** &amp; Omniture SiteCatalyst</em></strong><em> </em></p>
<p>**Though it appears that Omniture has more options for multi-site tracking, <em>in my opinion</em> the limited rollup analysis capability for Omniture SiteCatalyst, and the side-by-side comparison ability of Google Analytics make the two products very comparable in this regard.</p>
<h2>Segmenting / Correlations</h2>
<p>Segmenting data, called correlating in SiteCatalyst, is a way to break down two types of data to perform in-depth analysis of user visits. An example of segmenting would be to find out how many users referred by Yahoo.com viewed the site for more than 10 seconds.</p>
<p>Omniture SiteCatalyst has the ability to perform correlations, however each must be manually set up, and all data is <em>not</em> retroactive within the SiteCatalyst system. Each report suite in Omniture also has a limited number of correlations available, depending on your contract.  Omniture has a second product called DataWarehouse that allows for many different levels of segmenting and correlations.  While this data is retroactive for everything except newly added custom variables, reports can take up to 72 hours to process. DataWarehouse must be added to an Omniture contract before it can be accessed.</p>
<p>Google Analytics and Yahoo Analytics are <strong>much</strong><strong> </strong>more flexible when it comes to segmenting data for analysis. While custom segments and user-defined variables can be set up, most of the correlations that a user would need to perform are already built into both systems. Further,<strong> </strong>all custom segmenting is retroactive within the primary interface, meaning a breakdown of traffic by multiple dimensions can be viewed for the history of the report suite, and generation of these reports is nearly instantaneous.</p>
<p><strong>Advantage: <em>Yahoo Web Analytics, Google Analytics</em></strong></p>
<h2>System &amp; Account Limitations</h2>
<p><strong>Omniture</strong></p>
<p><strong> </strong></p>
<ul>
<li>Users – The Omniture contract dictates how many user logins are available for an account, and for large corporate clients it can be very easy to hit this limit.</li>
<li>Correlations – Each      non-rollup <em>report suite</em> in      Omniture has a limited number of correlations. A correlation in Omniture is a way      to tie two variables together for further breakdowns. Rollup report suites      cannot have any correlations.</li>
<li>Variable Limits      (props, evars, events) – Limits are in place for Omniture      custom variables (limits are <em>per      report suite</em>).  (Note: These limits may vary by contract):
<ul>
<li>s.prop variables: 50</li>
<li>s.eVar (custom       conversion,campaign) variables: 50</li>
<li>Event variables       (custom event tracking): 20</li>
</ul>
</li>
<li>Others – A variety of      other standard limitations exist within the Omniture system and contract,      though I have found that most others do not negatively affect standard reporting capabilities.</li>
</ul>
<p><strong>Google</strong></p>
<p><strong> </strong></p>
<ul>
<li>Page Views –      Currently, free usage of the Google Analytics application is limited to 5      million page views per month, per profile (each site generally has its own      profile.) Google accounts that are associated with an ‘active’ Adwords      account do not have the 5 million page view restriction. An active AdWords      account is defined by Google as spending a minimum of $1 per day.</li>
</ul>
<ul>
<li>Site Profiles – Called &#8220;report suites&#8221; in Omniture SiteCatalyst, a site profile in Google      Analytics is the name given to each individual site/rollup where data is      aggregated for analysis. <strong>Google Analytics has a limit of 50 profiles per      analytics account</strong>, however users can have multiple <em>analytics</em> accounts per overall Google Account. (An      administrator would only need to login to a Google Account once to manage      each analytics account and site profile.</li>
</ul>
<p><strong>Yahoo Web Analytics*</strong></p>
<ul>
<li>Site Projects &amp;      Multi-tagging – As mentioned previously, it is not clear whether or not      Yahoo will allow tracking of data for multiple “projects” on the same      page.</li>
<li>Variable Limits      (props, evars, events) – The following limits are in place for Yahoo      Analytics custom variables (limits are <em>per      tracked entity</em>):
<ul>
<li>Non-categorized       custom variables (action, campaign, etc): <strong>38</strong></li>
<li>Custom Event/Action       variables: <strong>15</strong></li>
</ul>
</li>
</ul>
<p>*As Yahoo Analytics is still in a beta state, it is not yet known what other system/account limitations might exist within Yahoo Web Analytics.</p>
<p><strong>Advantage: <em>Yahoo Analytics</em></strong></p>
<h2>Application Performance</h2>
<p>Performance of the application UI is much faster and more seamless in the Yahoo and Google offerings than in Omniture SiteCatalyst. The two most noticeable points of delay in SiteCatalyst are report generation and the total clicks to reach a report.</p>
<p>Google Analytics recently launched a new AJAX-based interface that allows for most reporting features to be loaded inline, without refreshing the entire page. As a result, items load much quicker and it is an overall better user experience.</p>
<p>While Yahoo Web Analytics does not make use of AJAX functionality to refresh reports inline, the overall UI appears to respond very quickly to most report requests. Still, Yahoo can’t quite match the speed of AJAX-based Google Analytics.</p>
<p><strong>Advantage: <em>Google Analytics</em></strong></p>
<h2>Custom Variable / Event / Link Tracking</h2>
<p>With Omniture SiteCatalyst, tracking code can be configured to track multiple different types of variables (listed previously in the <em>Account Limitations</em> section.) This ability makes it possible to break down traffic metrics and dimensions by various other custom metrics. Also available in SiteCatalyst is the ability to perform custom event and link tracking, both of which become useful when tracking actions that do not necessarily refresh a page or lead to a page that has tracking installed.</p>
<p>While Google Analytics meets most custom reporting needs with the out-of-the-box implementation, one key difference from Omniture is that Google Analytics only allows for 5 custom variables to be tracked on any single page. As a result, some level of compromise &#8211; or a different method of analyzing data &#8211; might be necessary. Google Analytics provides <em>custom link</em> and <em>event tracking</em> comparable with SiteCatalyst.</p>
<p>For custom tracking needs, Yahoo Web Analytics appears to combine the best of the Google and Omniture solutions. Yahoo has 39 built-in variables of various types that can be customized to fit tracking needs. In addition, Yahoo’s product allows for custom breakdowns (correlations) and custom report generation using any available metrics and data groups.</p>
<p><strong>Advantage: <em>Yahoo Web Analytics</em></strong></p>
<h2>Site Overlay Tools</h2>
<p>Both Google Analytics and Omniture SiteCatalyst have site overlay tools that can be used for viewing content popularity relative to surrounding items. Such tools are very useful for analyzing the effectiveness of ad positions, as well as user focus based on content placement.</p>
<p>Omniture’s site overlay feature is called ClickMap, and using the tool requires that a user download the installation file to their computer and install the application in the browser. One ongoing issue with ClickMap is that retrieving data for date ranges larger than one day can often take a very long time or time out completely. Compatibility has also been an issue with Omniture ClickMap, as new browser releases often disrupt the tool’s ability to accurately portray site overlays. Nonetheless, ClickMap is an effective way for web editors to view content popularity.</p>
<p>Google’s site overlay tool is often referred to as “heatmap” (or sometimes just “Site Overlay”). Unlike ClickMap, Google’s tool is opened in a new window and runs through the Google servers, so there is no installation required. The tool is relatively new and many in the analytics community are excited about what it can offer, however personal experience has shown that it is incompatible with my setup (I have not yet determined whether the issues are with the tracked website or my client.)</p>
<p>At the moment, Yahoo Analytics does not have any site overlay tool(s) available.</p>
<p><strong>Advantage: <em>Omniture SiteCatalyst*</em></strong></p>
<p>*There are many reasons why Google’s site overlay tool could have the advantage over Omniture’s ClickMap, however Omniture’s product has the advantage in this criteria simply for being around longer and proven effective.</p>
<h2>Data Export</h2>
<p>One very useful tool that is available from Omniture is the ExcelClient plugin for Microsoft Excel. With the tool, Omniture users can download data directly into Excel for analysis. This tool has proven to be very useful for creating custom-formatted reports, as well as running a standard report across multiple websites in a short period of time. Omniture also has a new API that can be used for exporting data.</p>
<p>An application similar to Omniture ExcelClient is available for Google Analytics.  Called the Tatvic Excel Plugin, the tool utilizes the Google Analytics API to pull data into Microsoft Excel.  Additionally, VBA Macros are available on the Google Analytics blog to further streamline data import to Excel.</p>
<p>Additional information regarding Google Analytics/Excel Integration can be found here: <a href="http://analytics.blogspot.com/2009/08/analytics-data-in-excel-through-our-api.html">http://analytics.blogspot.com/2009/08/analytics-data-in-excel-through-our-api.html</a></p>
<p>At the moment, Yahoo Analytics does not have any application similar to ExcelClient that can be used for exporting data. However, the Yahoo Analytics application does have an API available, which will likely lead to eventual Excel integration.</p>
<p><strong>Advantage: <em>Omniture SiteCatalyst, Google Analytics</em></strong></p>
<h2>Tracking Tag Performance</h2>
<p>In general, Google Analytics and SiteCatalyst tags do not appear to have a significant negative affect on page performance. From my testing with Gomez tools, the most obvious difference is that the Google tags appear to be much more consistent and reliable than Omniture tags.</p>
<p><strong>Omniture SiteCatalyst Tag:</strong></p>
<p><strong> </strong></p>
<div id="attachment_35" class="wp-caption alignleft" style="width: 686px"><a href="http://www.webanablog.com/wp-content/uploads/2010/01/omniture_tag_performance.jpg"><img class="size-full wp-image-35 " title="omniture_tag_performance" src="http://www.webanablog.com/wp-content/uploads/2010/01/omniture_tag_performance.jpg" alt="Omniture Beacon Performance" width="676" height="234" /></a><p class="wp-caption-text">Omniture Beacon Performance</p></div>
<p><strong>Google Analytics Tag:</strong></p>
<p><strong> </strong></p>
<p><strong> </strong></p>
<p><strong> </strong></p>
<p><strong> </strong></p>
<div id="attachment_36" class="wp-caption alignleft" style="width: 684px"><a href="http://www.webanablog.com/wp-content/uploads/2010/01/google_beacon_performance.jpg"><img class="size-full wp-image-36 " title="google_beacon_performance" src="http://www.webanablog.com/wp-content/uploads/2010/01/google_beacon_performance.jpg" alt="Google Analytics Beacon Performance" width="674" height="239" /></a><p class="wp-caption-text">Google Analytics Beacon Performance</p></div>
<p><strong>Yahoo Analytics Tag:</strong></p>
<p><strong> </strong></p>
<p><strong> </strong></p>
<div id="attachment_37" class="wp-caption alignleft" style="width: 681px"><a href="http://www.webanablog.com/wp-content/uploads/2010/01/yahoo_beacon_performance.jpg"><img class="size-full wp-image-37 " title="yahoo_beacon_performance" src="http://www.webanablog.com/wp-content/uploads/2010/01/yahoo_beacon_performance.jpg" alt="Yahoo Analytics Beacon Performance" width="671" height="230" /></a><p class="wp-caption-text">Yahoo Analytics Beacon Performance</p></div>
<p>In regards to performance of the tracking tags, Yahoo Analytics holds the clear advantage over Omniture and Google.  The average response time, measured over a 3 week period, was 0.025 seconds, faster than Omniture’s 0.061 seconds and Google’s 0.064.</p>
<p><strong>Advantage: <em>Yahoo Analytics</em></strong></p>
<h2>Ads / Conversion / Goal Tracking</h2>
<p>Because of the seamless integration with Google Adwords, Google Analytics provides a number of features for analyzing how ads affect page views and other conversion goals. Integration with Google Adwords is free with Google. Goal/conversion tracking can also be configured with Google, so that users following a certain path through a website can be counted and grouped together.</p>
<p>Omniture has an application known as SearchCenter which allows for integration with Google Adwords (and other PPC providers), however usage of this tool is at additional cost in the Omniture contract. Conversion tracking can be enabled in the Omniture interface, though the process within SiteCatalyst is much more tedious and confusing than in Google.</p>
<p>Yahoo Analytics can not only track the performance of Yahoo PPC ads, but can also pull in Google Adwords data for measuring performance of Adwords campaigns. This feature is available for free, making it the best option for PPC tracking between, Google, Yahoo, and Omniture.</p>
<p><strong>Advantage: <em>Yahoo Analytics</em></strong></p>
<p>So there you have it.  Of course there are many other things that may be taken into account when evaluating analytics solutions, but I&#8217;ve attempted to cover most of the basics here.  If you have any questions/comments about the data here, please let me know!</p>
<p>Enjoy!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.webanablog.com/2010/01/07/omniture-google-yahoo-analytics-comparison/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Tracking Facebook Fans in Omniture SiteCatalyst</title>
		<link>http://www.webanablog.com/2009/12/24/tracking-facebook-fans-in-omniture-sitecatalyst/</link>
		<comments>http://www.webanablog.com/2009/12/24/tracking-facebook-fans-in-omniture-sitecatalyst/#comments</comments>
		<pubDate>Thu, 24 Dec 2009 18:52:53 +0000</pubDate>
		<dc:creator>ABatten</dc:creator>
				<category><![CDATA[Omniture SiteCatalyst]]></category>
		<category><![CDATA[Facebook]]></category>
		<category><![CDATA[SiteCatalyst]]></category>

		<guid isPermaLink="false">http://www.webanablog.com/?p=6</guid>
		<description><![CDATA[In an effort to gather more data around &#8220;social media presence&#8221; in Omniture SiteCatalyst, I began investigating how to pull Twitter and Facebook data into Omniture SiteCatalyst.    After reading @VaBeachKevin&#8217;s post on importing Twitter Followers into SiteCatalyst on WebAnalyticsLand.com, I wondered if it would be possible to use the same concept to import Facebook [...]]]></description>
			<content:encoded><![CDATA[<div align="right" style="float:right;padding:0px 0px 5px 5px;"><a name="fb_share" type="box_count" share_url="http://www.webanablog.com/2009/12/24/tracking-facebook-fans-in-omniture-sitecatalyst/"></a></div><div class="tweetmeme_button" style="float: right; margin-left: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.webanablog.com%2F2009%2F12%2F24%2Ftracking-facebook-fans-in-omniture-sitecatalyst%2F"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.webanablog.com%2F2009%2F12%2F24%2Ftracking-facebook-fans-in-omniture-sitecatalyst%2F" height="61" width="51" /></a></div><p>In an effort to gather more data around &#8220;social media presence&#8221; in Omniture SiteCatalyst, I began investigating how to pull Twitter and Facebook data into Omniture SiteCatalyst.    After reading <a title="VABeachKevin on Twitter" href="http://www.twitter.com/vabeachkevin" target="_self">@VaBeachKevin</a>&#8217;s post on importing Twitter Followers into SiteCatalyst on <a title="WebAnalyticsLand.com" href="http://www.webanalyticsland.com">WebAnalyticsLand.com</a>, I wondered if it would be possible to use the same concept to import Facebook Fans.  After a bit of searching, I found <a title="Getting facebook fan counts using FQL" href="http://stackoverflow.com/questions/1888515/fan-count-for-a-facebook-fan-page">this</a> post at stackoverflow.com, and I was off and running.  Here&#8217;s how I did it&#8230;</p>
<p><span id="more-6"></span></p>
<ol>
<li>As I mentioned, I relied on the code at WebAnalyticsLand.com to get me started.  Specifically, I grabbed the code in Kevin&#8217;s post here: <a title="Track Twitter Followers in SiteCatalyst" href="http://webanalyticsland.com/sitecatalyst-implementation/track-the-number-of-your-twitter-followers-in-sitecatalyst/">Track the number of Twitter Followers in SiteCatalyst</a></li>
<li>To use the PHP solution from above, I also had to download the Facebook PHP client library. To do that, go here: <a title="Facebook PHP Client Library" href="http://wiki.developers.facebook.com/index.php/PHP" target="_blank">Facebook PHP client library</a>. The specific files you&#8217;ll need from the library are facebook.php and config.php.</li>
<li>You&#8217;ll need to modify config.php to contain your <strong>API Key</strong> and <strong>Secret Key</strong> from Facebook.  I set up a testing Facebook APP to get one.   Go here: <a href="http://www.facebook.com/developers/apps.php">http://www.facebook.com/developers/apps.php</a> From my experience, it didn&#8217;t matter what account/app keys I used for these; the API and Secret Key are just needed to create the Facebook object in the code.  You can remove the database info from config.php.  This won&#8217;t be needed, as we don&#8217;t need to query any local DB.</li>
<li>Upload config.php and facebook.php to the directory where your script will run.  I created a subdirectory for this.</li>
<li>Finally, here is the PHP template I used: <a title="Get Facebook Fans and Add to Omniture" href="http://www.webanablog.com/getFBFans.zip">Get Facebook fans and Add to Omniture</a></li>
<li><a title="Get Facebook Fans and Add to Omniture" href="http://www.webanablog.com/getFBFans.zip"></a>At the top of getFBFans.php, make sure the following lines reference the correct location of config.php and facebook.php:<span style="font-family: Consolas, Monaco, 'Courier New', Courier, monospace; line-height: 18px; font-size: 12px; white-space: pre;"><br />
include_once &#8216;facebook.php&#8217;;<br />
<span style="font-family: Georgia, 'Times New Roman', 'Bitstream Charter', Times, serif; line-height: 19px; white-space: normal; font-size: 13px;"><span style="font-family: Consolas, Monaco, 'Courier New', Courier, monospace; line-height: 18px; font-size: 12px; white-space: pre;">include_once &#8216;config.php&#8217;;<br />
</span><br />
</span></span></li>
<li>In the block beginning at line 14, edit the commented lines for the appropriate Omniture details and Facebook page ID. To get the Facebook page id, I found it easiest to search for the fan page, then click on the main profile photo. The URL will then show you the page/account ID. For example: <a href="http://www.facebook.com/album.php?profile=1&amp;id=6181619439">http://www.facebook.com/album.php?profile=1&amp;id=6181619439</a>.  The id <strong>6181619439</strong> is what you&#8217;ll put at line 23 in getFBFans.php.</li>
<li>The event you use in SiteCatalyst MUST be configured to <strong>numeric</strong>, rather than <strong>counter.</strong> Go into SiteCatalyst Admin settings for the respective report suite to configure this.</li>
<li>Upload getFBFans.php to a PHP server. Any time you hit that PHP file, it will perform the FQL query to Facebook and import into Omniture using the Data Insertion API.  My suggestion is to set up a cron job to run the script hourly,  for hourly trending in SiteCatalyst. <strong>NOTE: Running this script more than once per hour will inflate fan count!</strong> It is very important that you <strong>only</strong> run the script once per hour.</li>
</ol>
<p><span style="color: #ff0000;">EDIT: After looking at the data as its coming in, I think I will reschedule this script to run once per day. Because hourly granularity in SiteCatalyst can only be viewed for a maximum of 14 days, it&#8217;ll be much easier to see trends over large date-ranges by looking at a daily granularity.</span></p>
<p>And that&#8217;s it!  Of course, if you notice any issues with my explanation or the code in the files, <strong>please</strong> let me know so I can make corrections.  Enjoy!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.webanablog.com/2009/12/24/tracking-facebook-fans-in-omniture-sitecatalyst/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
