I’ve been thinking a bit about targeting, and how we in the web analytics industry have just a ton of visitor or segment-level data that can be used for targeting ads or content, but most tools don’t let you use the data or easily feed it to other systems to do any targeting.  It’s rather odd, don’t you think?   Even Omniture Test and Target isn’t using, as far as I’ve learned, a single data model or the data collected from their behavioral tools, like HBX or SiteCatalyst, for targeting.  All their data models and thus, their data, are unique to the products in their platform.   So I decided to resussitate/revise a blogviation and offer it as food for thought on MediaPost.  When I reread this post, it’s more of an informational post for product managers on how I’d begin thinking about targeting with analytics data and what types of targeting are possible, so here it goes.   

Targeting refers to the process of delivering content or ads to segments or visitors based on their known attributes.  The goal of targeting is simple to understand: maximizing the performance of content or an ad by serving it to visitors at a time when they are most open to the receiving the message. 

For example, you may visit a site, and see some type of ad unit calling out at you to “meet singles in <insert_your_city>.”  When browsing a real estate site, you may see ad units for realtors and mortgage companies.  After entering a keyword such as “car insurance” and clicking through the search results, you may land on a site and see an ad for a car insurance company or land on a page that persuades you to begin the process for creating an insurance price quote.  That’s targeting in a nutshell.  It’s simple for a site owner to understand:

1. Visitor X has these attributes.  
2. We have content or an ad that we think will appeal to Visitor X’s attributes. 
3. Let’s show the relevant content or ad. 

In online media, targeting is associated with paid search campaigning, ad serving, and content optimization based on recognizing and responding to the following attributes:

• Category and sub-category.  Conceptual constructs like “categories” of topics on a media web site or products on an ecommerce site can be targeted to include certain types of ads or messages.   The idea is that if visitors are browsing your category for “hardware floors,” you could offer them an ad or content specific to “flooring installation services.” 
• Geography.  Country, region, city, state, DMA are all targetable constructs.  You may run a sports site and choose to target people surfing in from 02116 (Boston) an ad for Red Sox tickets or content about Manny Ramirez’s recent trade to the Dodgers.
• Browsing environment such as the connection speed, type of browser, operating system, user software, domain, and ISP.  An ad network could serve an ad for DSL to a modem-based surfer by detecting the visitor’s browsing environment.
• Time.  The idea of only showing content during specific periods of time is called “parting.”  Common types include day-parting and season-parting.  For example, a B2B site only choosing to show ads for a particular manufacturer’s product during business hours — the site’s busiest time of day — would be an example of day-parting.
• Keyword.  There are many different types of keyword targeting.  Search engines target ads based on keywords in queries.  Content Management Systems target content based on site search keywords or referring keywords.  “Keywords” may be associated as metadata with site sections or pages, similar to zone or category targeting on an ad server.  Once a page is associated with keyword metadata in an ad tag, you can tell your ad server to target ads to that keyword on whatever page or pages the tag was placed. 
• Language.  When a language can be detected or known in advance, you can target ads to visitors in their language.
• Demographics. If the ad server is aware of a segment’s demographics, such as age, gender, income, title, purchasing power, and so on, an ad can be targeted on that basis. 
• Context.  Think of AdSense and how it matches text ads based on the semantics in site content.  Or when, after adding a product to your cart, a site offers you “free shipping” if your total purchase exceeds a certain price.  This is content targeting based on context.
• Profile.  Targeting is possible based on conclusions drawn and rules created from attributes about an individual or segment (such as purchasing propensity or job title).
• Rules.  Serve an interstitial ad only to visitors who don’t have a cookie set for the site.
• Events.  Someone deposits a large sum of money into his bank account, so the online banking site offers him a CD product on his next login.

We’ve all heard, of course, about a very specific type of often-discussed targeting in online advertising: “behavioral targeting.”  Behavioral targeting refers to the technology and process in which an ad or content is shown to a visitor based on their past actions and reactions.

Behavioral targeting involves:

1. Collecting behavioral data about visitors.
2. Identifying when those visitors visit a site.
3. Determining the current context of visitors on the site.  
4. Detecting the visitor’s current behavior.
5. Serving relevant ads (or content) matched to the behavior.

The goal being to use past behavioral data to influence the customer buying cycle or marketing lifecycle, in order to more effectively and more quickly deliver on advertiser and site goals.

So where does Web analytics come in?  You would think Web analytics data from “Web analytics” technology would be used to enabling “targeting.”  After all the best Web analytics systems store detailed visitor level data about past behavior.  Web analytics data certainly can be used, but in most cases, targeting is a function provided by the ad server or network, perhaps the ISP, or another technology called the “behavioral targeting platform,” not from data collected by the Web analytics tool.

In order to make Web analytics data useful for targeting, you will need to use your data to:

1. Define segments to target or identify visitors to target.
2. Feed past behavioral data about segments or visitors to the targeting technology.
3. Analyze segment and visitor performance against site or advertiser goals after targeting.

Targeting has a proven ability and amazing potential to generate tremendous returns, especially when combined with the rich, detailed behavioral data available in Web analytics.  As a method for optimizing site content and advertising, targeting technologies that integrate with Web analytics data will only become more important and a necessary “must have” for innovative companies that want to maximize business opportunities on the Internet. 

Hello good readers!  Every month I write a column for MediaPost’s Metrics Insider.  Here’s my most recent one:

Companies that derive revenue from multiple channels often have two analyst teams: the “database marketing team” and the “Web analysis team.”  These groups tend not to communicate.  In some companies, however, these teams are merging to form the “multichannel analytics team.”  This specialized team analyzes, reports, and evaluates both Web data and offline data — often in coordination with the “business intelligence team.”  The emergence of this new team structure makes sense for companies that are shifting their offline business models to become more online-centric, and thus want to understand value-generating connections among channels. 

Several macro-level catalysts are necessitating the shift to a multichannel approach to data collection and analysis.  The ongoing mainstreaming of the Internet channel for enabling commerce, conversation, and relationship marketing is certainly pushing this movement.  The burgeoning set of analytics tools that integrate with other technologies to enable event detection and trigger a customer-specific response is also promoting change in the way companies think about connecting offline and online data to improve overall business performance.

If database marketers and Web analysts are evolving into a new type of team, then what roles are necessary on this new multichannel team?  Here are a few:

• Web Analyst.  The overall Web analytics professional has a deep understanding of the Web channel.  This person uses a Web analytics tool to understand the performance of site traffic, online marketing campaigns, and to segment Web data in order to understand how visitors referred from certain channels navigate (or don’t) through the site.  They understand, measure, and report whether the site is fulfilling its purpose for conversion, task completion, and other KPIs when compared to business goals.  
• Site Optimizer.  A niche type of Web analytics professional, the site optimizer is in charge of determining the right approach for configuring and reporting the results for AB (champion/challenger) and multivariate tests.  This person is all about testing components of site and page design to yield the best combination of elements that provides a lift in a particular metric against a goal, such as conversion rate.  Content targeting may also fall under this person.
• Social Metrician.  Another niche type of Web analytics professional, the social media measurer is concerned about the performance of customer touchpoints outside of the main Web site.  He or she collects, monitors, and analyzes data related to things that happen “out there, on the Internet,” such as syndicated video, mobile, widgets, blogs, social networks, and other social media.
• Database Marketer.  The traditional offline analyst and database miner.  This role analyzes data from channels that are not online but may reference and promote online interaction, such as television, radio, print, catalogs, and direct mail.  Of course, these analytics skills can be applied to online data as well!
• Search Analyst.  The analytics professional in charge of keyword identification/selection, keyword management, bidding, and analyzing the outcomes of search.  He or she may be in charge of analyzing site performance against known SEO goals too, not just SEM.
• Market Researcher.  The traditional market researcher gathers, analyzes, and reports data about the overall market, key competitors, and customers. 
• Qualitative Analyst.  Part market researcher and part analyst, this individual is in charge of online customer and visitor surveying, relating customer feedback and visitor opinions to the context of on-site behavior to help deduce “why” people did something on your site.
• Ad Analyst.  Solely dedicated to assessing the performance of advertising campaigns, the ad analyst assesses and educates clients on ad campaign performance both online and offline.
• Audience Measurer.  The wielder of an audience measurement tool informs competitive decisions, influences media plans, and provides benchmarking and competitive data to give context to other data analysis activities, such as keyword bidding or media buying. 

How would these professionals all work together?  The market researcher’s data is used to help craft a customer-focused and competitively differentiated campaign strategy.  The audience measurer provides data that focuses the strategy on the right online demographics and sites, while the database marketer mines historic data to figure out the best-performing offline tactics for the identified demographics. 

Let’s say a mix of search, social media, and online and offline display ads are selected as part of the campaign.  The search analyst concentrates on SEO/SEM, while the ad analyst tracks the performance of display ads.  The social metrician examines the social media ecosystem’s response to the campaign.  The Web analyst analyzes how campaign-referred visitors behave and navigate through the site, taking into account the context of the qualitative analyst’s voice-of-customer data.  Meanwhile, the site optimizer tests landing pages and funnels to ensure they effectively convert visitors and fulfill business goals. 

For many companies, it would be unrealistic and perhaps impossible to find and hire people to fill each of the roles I’ve presented above.  In fact, in most companies these roles and activities are completed by only a few people, if at all.  An option for companies that seek to expand or combine teams is to look at consultants, contract workers, and full-time equivalents allocated across multiple people.

That said, companies that are unable to bridge together online and offline analytics teams will miss important data points.  In the digital future, we’ll see different types of analytics professionals working together across channels to yield profitable insights that support campaign and business goals.

That’s the first question to answer when determining strategy for using online metrics.  You should be able to answer in 10 seconds.  If you don’t know, or if key stakeholders can’t agree on your site’s purpose, then you are unable to use online metrics efficiently.  And, worse yet, you are missing chances for improving your business performance. 

Your web site exists for a purpose, perhaps multiple purposes, such as:

• Providing information or data.  Many sites entice people to visit for access to valuable, differentiated information or data.  Traffic is then monetized primarily through site advertising.  Many internal and external analytics packages will tell you where visitors come from and what they do onsite, which, when combined with demographic information, can be used to qualify a specific audience to an advertiser.
• Generating leads.  A content asset is placed on a site and gated using a form.  People fill out the form and download the asset.  The information captured in the form is stored and used by the company that generated the leads or profitably sold to another company.
• Selling products.  The typical ecommerce model involves acquiring customers via some method or offer, providing a product catalog or landing page, and creating a strong call to action and funnel that persuades people to purchase a product.
• Connecting people.  The explosion of social networking sites where people connect to other people, interact with each other, and use widgets, apps, and data services is a modern phenomenon in which many of us participate. 

Understanding why your site exists enables you to effectively use online metrics.  Once you’ve defined your site’s purpose, you are positioned to examine web data in way that helps you determine whether your site delivers on its purpose – does it effectively exist? 

Metrics and ratios that help you assess if you site fulfills its purpose are called Key Performance Indicators (KPI’s) – see Eric Peterson’s Big Book of KPI’s for a detailed review of the topic:

• For information or data driven sites, you may want to look at KPI’s that measure goal or task completion and conversion rates.  For example, if your site’s purpose is to expose video content to an audience, then a relevant KPI would be the percentage of all visitors that streamed a video or the number of streams per visit. 
• For lead generation sites, a key KPI you will track is the lead conversion rate.  In other words, of all the visitors that came to your site, what percentage of visitors successfully filled out a form and generated a lead. 
• For ecommerce sites, a key KPI that you might track is average order value, which is how much money the average visitor who purchases a product spends on a single transaction.
• For social networking sites, you may want to measure the average time between visits (latency) and the repeat visitor rate. 

But here’s the challenge with KPI’s: they are all academic, unless you have business goals for KPI’s.  KPI’s help you track progress toward predefined business goals.  What are the business goals associated with your site’s purpose?  For your informational site, what’s the goal for video streams per visit or time spent?  For your lead generation site, what’s the goal for the lead conversion rate?  By comparing business goals for KPI’s to actual KPI’s, you can begin to answer the question: “is my site successfully existing and fulfilling its purpose?”

You will continue to answer that question by segmenting your KPI’s, investigating distributions beyond averages, and using other techniques for data analysis.  You may ask: do certain referring sites, have a lead generation conversion rate higher than other referring sites, and why?  Do certain audience segments spend more time on site?  If so, where do they go on the site and what do they do?  If my goal for average time between visits (latency) to my site is five days, and certain customer segments haven’t visited in ten days (recency), what does that indicate about current business performance?

By defining why your site exists, creating KPI’s based on your site’s purpose, establishing business goals for KPI’s, and investigating what’s driving those KPI’s, you can enhance your online business performance in a way that increases bottom-line profit – from optimizing user experience and landing pages, to more efficiently allocating your marketing budget, to improving your product mix, and much more.

In Part 1, I mentioned that the Web Analytics team will look very different depending on company and business goals.  I identified three elemental constituents (business strategy, analytics, and technology) necessary to select a web analytics tool, and I divided them up into three different folks who fill those roles when you’re selecting an analytics technology.

Once the tool is selected, companies will want to create a structured team framework with defined roles and responsibilities in order to successfully deploy the tool.  What I’m describing is a suitable team-structure that enables you to successfully deploy a tool in your organization that finally gets you to a point where you are able to do web analysis. The team structure I describe below lets you get to the hub-and-spoke model that my good friend, Eric Peterson, described in these Part 1 and Part 2 of “what’s your web analytics communication strategy?”   What Eric excellently describes takes the team to the next level of actually doing Web Analytics.  It’s excellent stuff that I encourage you to read.

A formalized team structure for rolling out a web analytics tool may have the following constituents: 

• Executive Advisory Board.  Beyond the Executive Sponsor mentioned in Part 1, these board members are the ones who really control the budget and strategy at the highest level.  They may be your boss, your bosses’ boss, or board members at your company. Regardless, they are the analytics project champions at the highest level in your organization – often C-level executives.  They support the project structure and analytics strategy, confirm the scope of the project, and approve any budget allocation.

• Steering Committee.  You may be on the steering committee, Mr Web Analyst, or it may consist of very senior representatives of all the internal teams that the project touches.  These people work to define the strategic direction of the project, decide on how to resolve critical issues that come up during the rollout, and generally handle any escalations.

• Web Analytics Expert.  That’s probably you, fine reader.  You will provide analytics-based strategy and informed decision making across all aspects of the project. You’re obviously critical to the success of this project, and will ensure technical, tactical, procedural, functional, and financial adherence across the entire analytics program.   You are the chief evangelist, and will define the overall reporting and KPI structure.  In addition, you will be responsible for the overseeing the partnership with your vendor. Other things you may do will include managing costs, coordinating schedules, risks and resources, and reporting overall project status and important communications (often with the help of a project manager) to the steering committee and advisory board.

• Web Analytics Team.  If you are lucky enough to have a team, these folks will gather and document project and technology requirements, liason with business stakeholders, lead training, build awareness of and evangelize web analytics, and in general work with those who receive reporting and leverage the tool.  In many companies the solo web analytics expert will do all this stuff (and drink a lot of coffee or green tea too!).

• Project Manager.  A web analytics rollout can be complicated. While the solo web analytics team member may be expected to project manage, it may make sense to give that role to a formal project manager (y’know a PMP) who works with the Web Analytics Expert to manage the schedule, risks, resources, communications, change, and quality management plans.

• Business Partners.  Since web analytics will touch many different groups, you will need to ensure your analytics team communicates with them.  Business partner are critical stakeholders.  They can’t be neglected.  They will provide business requirements, test the technology, and work with analytics team to ensure the technology, reporting, KPI’s, and analysis you rollout helps drive business performance.

• Subject Matter Experts (SME).  Similar to business partners, these folks will probably be more technical in nature.  The Technology Expert you worked with when selecting the project will transition into a roll as a SME.  You may have one SME who oversees the overall technology architecture, another who coordinates BI resources, another who QA’s the system, another who creates interfaces to your data warehouse, and perhaps another who acts an IT contact covering issues across the operating system, database, security, and networks (especially if you are running an in-house tool).

• Vendor Professional Services Team Members.  Last, but certainly not least, are the folks sent from your vendor to do what you want them to do.  From installing the application (in a in-house environment), functional training, to advanced configuration, these people are critical to ensuring that you don’t make simple, avoidable mistakes that can thwart your efforts and delay the successful rollout, golive, and extension of the project.

In reality, you may not be able to effectively isolate all of these groups to support your analytics rollout.  To some degree I’ve presented big company structure above.  In smaller companies, one or only a few people may do all of the interlaced activities necessary to rollout a web analytics tool.  Regardless, I think the groupings I’ve presented above define the primary roles and responsibilities necessary for success when rolling out a web analytics tool (in fact I presented things in a general way to apply to other rollouts as well).  The next challenge comes once your up and running (make sure to read Eric’s posts)… You need to use the data to improve business performance and guide strategy, decision making, and online tactics that reduce expense and yield profitable revenue.


Image by Jim Sterne, from Emetrics 07 San Fran.

Every month I write a column for MediaPost’s Metrics Insider.  This month I wanted tackle my evolving take on Internet video measurement.  Very few companies offer solutions in this space.  Only a few are really differentiated.  Check out Visible Measures, NedStat, TubeMogul, Divinity Metrics, and the usual suspects, Omniture, Unica, WebTrends, ComScore, and Neilsen NetRatings. 

Here’s my column:

IN LATE 2007, THE DIGITAL Video Barometer Executive Survey indicated that more than 80% of media and entertainment executives believe tracking, measuring, and monitoring Internet video content is critical to bottom-line profit.  That’s not surprising. Accurate measurement informs decision-making and improves business performance, and Internet video is more mainstream and popular than ever before.  What may be surprising to those executives is that technology for measuring Internet video generally focuses on video content served on-site, not off-site.  It’s fairly straightforward for a Web analytics tool to tell you how people are consuming and interacting with on-site video, but consumption and interaction of videos distributed across multiple sites, perhaps virally or via social media campaigning, aren’t directly measurable by Web analytics tools.  Panel-based technologies can approximate certain off-site measures of video consumption and distribution, but don’t provide very deep on-site metrics. Measurements of Internet video consumption, interaction, and distribution may be categorized as follows:

• Instream measurement.  Refers to measuring the video itself and the various events and behaviors that occur during a video viewing experience, such as time-based duration metrics and interaction and behavioral metrics (for example, the number of stops, plays, pauses, rewinds, fast-forwards, sites that posted or syndicated the video, clicks on hotspots and social media features).
• Outstream measurement.  Refers to measuring the content environment and user experience surrounding the video on the site or in the skin, such as the conversion metrics (percentage of visitors downloading or viewing a video), source metrics (refers to the video page, players used), and content metrics (percentage videos viewed by topic, percent videos viewed by file type). 

Those categories form a framework for Key Performance Indicators (KPI’s) that help to identify how people interact with videos, how videos perform when compared to other videos, and against pre-defined business goals.  Analysis of KPIs enables video content to be tailored to maximize performance.  Example KPI’s include:

Instream KPI’s:

• Percent high, medium, and low duration video views
• Average viewing time per video
• Percent visitors who complete the video
• Percent visitors that stop the video within 10 seconds
• Percent visits when this video was the last video viewed
• Percent visits when this video was the first video viewed

Outstream KPI’s:

• Conversion rates by video, topic, channel, taxonomy node, referrer, geography, keyword, and so on
• Average video views per visit
• Percent visits/views from different channels (such as email/rss, organic search, paid search, direct)
• Average time between visits that include a video view
• Repeat visit rate for visits involving a video view or download

These KPIs are measurable using a Web analytics tool, and perhaps a few of them are possible using traditional panel-based measurement.  But if off-site video distribution creates a whole new set of challenges to using current analytics and audience measurement tools to track instream and outstream metrics and KPIs, what are publishers and advertisers to do?  It’s a business problem that demands a new technology solution for understanding audience behavior, consumption, and distribution patterns of off-site syndicated or viral video content.

So what would a new technology solution for measuring Internet video and audience behavior do?  First it would have to fill the gap between panel and census-based measurement systems in a way that helps both publishers and advertisers  – not just one or the other — understand audience reach, frequency, and behavior.  The technology must enable tracking and actionable reporting and dashboarding of key metrics and KPIs, distribution patterns, behaviors, and interactions regardless of where the video “goes” on the Internet.  Audience characteristics from external databases (like OpenID for example) and internal company databases (like subscription and registration dbs) should be able to be integrated with data collected about behavior, video metadata, and instream and outstream metrics. 

If measuring digital video is as important as eight out of 10 media and entertainment executives believe it to be, there are some huge money-making opportunities on the horizon — for companies that are already providing technology for tackling this emerging business need, for advertisers using Internet video to drive awareness and response, and for measurement professionals who can help make sense of the Internet video ecosystem, solve measurement challenges, identify significant business opportunities, and use video metrics to improve business performance.  We’re certainly at the beginning of the J-curve for Internet video measurement for both publishers and advertisers.  After all, Forrester predicts Internet video advertising spend to increase from $471 million last year to $7.1 billion in 2012. 

About a year ago, I wrote a guest blog post over on Robbin Steif’s blog about using Google Analytics for tracking Javascript and Flash events.  This weekend Jeremy Geelan, SVP over at Sys-Con Media, asked if he could republish the work.  Of course I said “yes.”  Then I noticed that a lot has happened to GA in a year (and more to come, ahem, API’s!).  What I had wrote was now incomplete, so what you’ll find below is my attempt to sum up “event tracking” using ga.js and the Great Google’s Event Tracking Data Model.  Let me know how I did covering it, and if you think I should clarify of expand on anything.

Since we all know about page tags, let’s get down to business with “the Google” and how it tracks “the Rich Media.”  Google Analytics currently has two different javascript page tags:

• urchin.js.  The legacy version of the Google Analytics page tag.
• ga.js.  The current, rebranded version of the Google Analytics page tag.

How you track rich media depends on which page tag you are using.  I’ll discuss using urchin.js first, then ga.js.  I’ll also provide some information about Google’s Event Tracking function for capturing specific “events” within their event architecture.

Tracking Rich Media using Urchin.js

In the legacy version of Google Analytics, the smarties at Google created a little JavaScript function called urchinTracker() that enables event tracking.  Use the JavaScript function with an argument specifying a name for the event. For example, the function:

javascript:urchinTracker(’/mysite/flashrichmedia/playbutton’); 

logs each occurrence of that Flash event as a page view of:

/mysite/flashrichmedia/playbutton

Some caveats:

1. Always use a forward slash to begin the argument.
2. Actual pages with these filenames do not need to exist.
3. You can organize your events into any structure or hierarchy you want.

Important: Google says to place your tracking code “between the opening tag and the JavaScript call” if your pages include a call to urchinTracker(), utmLinker(), utmSetTrans(), or utmLinkPost(). For example, if the page view is the major event and the “play” event a minor event; then, your hierarchy would be Page View > Event, where the page contains an event, such that:

/mysite/ria_bittons/playbutton
/mysite/ria_bittons/pausebutton
/mysite/ria_bittons/playbutton
/mysite/ria_clips/clip

Some examples of the code (from Google Help):

on (release) {
// Track with no action
getURL(”javascript:urchinTracker(’/folder/file’);”);
}

This one above tracks when you click and release (although technically, it just notices the release) of a flash button (and records the file you specify as a page view).

on (release) {
//Track with action
getURL(”javascript:urchinTracker(’/folder/file’);”);
_root.gotoAndPlay(3);
myVar = “Flash Track Test”
}

The second one is the same, but by using a function, passing it a parameter, and identifying the instance you want to track, you can measure when your file was used in a specific scene in a little flash movie. So it is a more specific method for handling event tracking in Flash.

onClipEvent (enterFrame) {
getURL(”javascript:urchinTracker(’/folder/file’);”);
}

And the third one repeats the action throughout the movie so that each time the file is loaded, it gets tracked as an event. If you were to pass a unique file at the end of the movie, you could recognize it using this method (or the other methods) to know that the whole movie was watched (as long as your session doesn’t time out). Next, wait until Google updates your analytics, then check the Top Content report to see if it all worked. Now let’s discuss how to the exact same thing using the new trackPageview function released with ga.js.

Tracking Rich Media using ga.js

In the current version of Google Analytics, the brainiacs at Google created a little JavaScript function called trackPageview() that enables event tracking.  Use the JavaScript function with an argument specifying a name for the event.For example, the function:  

javascript:pageTracker._trackPageview (“/mysite/flashrichmedia/playbutton”);

logs each occurrence of that Flash event as a page view of:

/mysite/flashrichmedia/playbutton

Some caveats:

1. Always use a forward slash to begin the argument and use quotes around the argument.
2.  Actual pages with these filenames do not need to exist.
3. You can organize your events into any structure or hierarchy

You must put calls to _get._getTracker and _initData above the call to _trackPageView.  For example, you would insert the following code:

<script type=”text/javascript”>
var pageTracker = _gat._getTracker(”UA-xxxxxx-x”);
pageTracker._initData();
pageTracker._trackPageview();
</script>

Here are some examples of the ga.js code (from Google Help) that replicate what I described above using the most recent code:

on (release) {
// Track with no action
getURL(”javascript:pageTracker._trackPageview(’/folder/file.html’);”);
}

This one above tracks when you click and release (although technically, it just notices the release) of a flash button (and records the file you specify as a page view).

on (release) {
//Track with action
getURL(”javascript:pageTracker._trackPageview(’/folder/file.html’);”);
_root.gotoAndPlay(3);
myVar = “Flash Track Test”;
}

The second one is the same, but by using a function, passing it a parameter, and identifying the instance you want to track, you can measure when your file was used in a specific scene in a little flash movie. So it is a more specific method for handling event tracking in Flash.

onClipEvent (enterFrame) {
getURL(”javascript:pageTracker._trackPageview(’/folder/file.html’);”);
}

And the third one repeats the action throughout the movie so that each time the file is loaded, it gets tracked as an event. If you were to pass a unique file at the end of the movie, you could recognize it using this method (or the other methods) to know that the whole movie was watched (as long as your session doesn’t time out).

Tracking Rich Media using Google Analytics Event Tracking

When Google released ga.js in fourth quarter 2007, Google also released a data model for tracking events.  It provides more flexibility and ease of customization than the methods I described above.   The data model makes use of:

• Objects. These are named instances of the eventTracker class and appear within the reporting interface.

var videoTracker = pageTracker._createEventTracker(”Movies”);

• Actions. A string you pass to an event tracker class instance as a parameter.

videoTracker._trackEvent(”Stop”);

• Labels. An optional parameter you can supply for a named object.

downloadTracker._trackEvent(”Movies”, “/mymovies/movie1.mpg”);

• Values. A numerical value assigned to a tracked object.

To set up event tracking you should:

1. Identify the events you want to track.
2. Create an event tracker instance for each set of events.
3. Call the _trackEvent() method on your page.
4. Enable “event tracking” in your profile.

To instantiate an event tracker object, you might do something like this:

var myEventObject = pageTracker._createEventTracker(”Object Name”);
myEventObject._trackEvent(”Required Action Name”, “Optional Label”, optionalValue);

createEventTracker() is order dependent and must be called after the main tracking code (ga.js) has been loaded.Next you would call the _trackEvent() method in your source code either on every page that contains the event or as part of the tracking code for every page:

_trackEvent(action, optional_label, optional_value)

If you wanted to track interaction with the Flash UI, such as the button on a Flash Video Player, you would create a videoTracker object with name “Video”:

var videoTracker = pageTracker._createEventTracker(’Video’);

Then, in your Flash code for the video player, you would call the videoTracker object and pass a value for the action and label for the event:

onRelease (button) { 
   ExternalInterface (”javascript:videoTracker._trackEvent(’Play’, ‘MyVideo’);”)
}

You could also use the ExternalInterface ActionScript function as an eval() function to parse FlashVars and attach them to every Flash UI element that needs a tracking action.  For example, the code below associates a Stop action for the Video object and retrieves the provided label and value from the FlashVars:

onRelease (button) { 
   ExternalInterface (”javascript:videoTracker._trackEvent(’Stop’” + label + “,” + value + “);”)
}

Adding event tracking code would generate event reports in the Content section of the Google Analytics Interface.  Pretty cool stuff, Google!

What’s the future hold for Web Analytics in 2008?  Here are a few predictions:

• Google Analytics releases a real API for getting (and perhaps setting) data.  As you know, I think GA is a fine tool for web analytics, but has severe limitations when you want to control over your data or to feed data into other systems.  Thus, I predict Google Analytics will go beyond the “Tracking API” and release a real API that allows you to at least get data out of the tool (if not set data as well).  Think of what Feedburner does with their REST-based Awareness API.  Wouldn’t that be nice to have with GA?!
• HBX Analytics goes away.  I’d be more than a bit nervous if I were an HBX customer because Omniture is going to sunset HBX and migrate everyone to SiteCatalyst, then try to aggressively sell them the rest of the suite. 
• Long live Visual Sciences.  VS is a powerful tool quite superior in some regards and very different than anything else Omniture offers.  It’s also real in-house software, not some blackbox.  VS’ extensible schema, flexibility in reporting, scalability, and performance is quite unparalleled in the industry.  I can’t envision Omniture killing it (unless they peel it apart in order to create Discover 3), like they will HBX. 
• WebTrends rebrands.  I’m not sure if you agree, but imho WebTrends Marketing Lab was an attempt to rebrand WebTrends.  I expect that interim management will continue attempting to differentiate WebTrends by rebranding products and perhaps the entire company.
• New and updated standards are released.  As a member of the IAB’s Measurement Council I can tell you that the IAB is getting ready to release the IAB Audience Measurement Reach Guidelines, which attempt to clarify and take a stand on various aspects of server/client-side analytics and audience measurement.  I also envision the WAA increasing the number of terms they define.  But standards are just dandy and quite meaningless unless they are adopted… thus…
• Standards enforcement is attempted in order to propel adoption. Existing and forthcoming standards will be enforced in 2008.  Enforcement from the WAA will probably come in the form of a publication of a matrix or documentation citing which vendors adhere to the standards and to what degree, what’s missing, what’s different, and so on.  If decision-makers who control budgets believe in standards, this type of document will cause the question ”do you adhere?” to be asked.  If vendors start losing deals because the answer is “no, not at all,” vendors will adopt the standards. 
• Internal data integration becomes more important for companies and problematic for ASP’s.  When we talk about “integration” I often think people can be a bit shortsighted.  They want to integrate data from other third-party services and tools (like Salesforce.com and their ad server).  While there is certainly real value in integrating external data with web analytics data, significant value comes from integrating web analytics with internal data, such as data residing in internally-hosted CRM systems, finance, subscription, and lead generation databases. Most vendors have barely figured out how to deal with detail-level external data integration in 2007, even though many customers are demanding it.  I expect that in 2008, internal data integration will be more commonly demanded and even more problematic for ASP’s. 
• BI tools provide better support for and integration with Web Analytics tools.  The current allotment of “enterprise” level web analytics tools are inferior to the capabilities provided by business intelligence tools from companies like Business Objects or Cognos.  Expect these BI vendors to create features for dealing with web analytics data in 2008.  Either that, or these web analytics tools need to grow up and learn a few things from BI. 
• Web Analytics as performance management.  KPI-based site optimization means using data to guide the modification of user experience to deliver on goals.   Since goals are measurable and can be plotted against performance, it’s totally logical to use web analytics as a performance management tool.  Expect to see that gestalt in tool usage come into vogue and be discussed more in 2008. 
• Web Analytics as part of business process automation.  Having the marketing department fielding page tags with campaign codes may work for some (small) companies, but when you work for an enterprise with thousands of clients and simultaneous campaigns across multiple channels, endemic tagging and subsequent tool configuration becomes challeging.  As part of the web analytics process, I expect to see tools support some level of business process automation enabling web analytics.
• Features for measuring the Mobile Web.  Right now, with a log file based tool, I can segment out Mobile traffic based on user agent.  If I want to use a page tag, I have to consider js limitations.  The mobile web is the next frontier, and I only know of one web analytics vendor who is doing a decent job measuring it right now, so I expect to see more features released this year for measuring Mobile.  

So that’s that.  Like a band named PIL once said in the song called Rise “I could be wrong, could be right!”  Am I off-base, misguided, accurate, do you disagree, agree, then let me know… I’d love to hear your thoughts and your predictions for Web Analytics 2008…

If you’re new to web analytics, or the management of web analytics, it’s always helpful to get advice from someone whose been in the industry.  Here are a couple of simple principles I’ve found helpful:

• Investigate and be skeptical of claims by vendors. Upgrading a tool?  Migrating to a new tool?  Completely replacing one?  Adding a tool to your analytics arsenal?   Someone is then trying to sell you something.  Vendors really want your money.  And when it comes down to it, it seems the bigger the vendor and the smaller you are, the less attention you will get, even when you need their help really badly.  Vendors attempt to have their own, differentiated spin on web analytics - one of the reason the WAA developed standards.  Avoid falling into the mental model of any one vendor… push their envelope… champion for standards.  In doing so, make sure to realize that a good relationship with a vendor based on an understanding of mutual strengths and weaknesses will lead to collaboration important to your success.
• Don’t bias yourself when it comes to data collection.  Page tags are imperfect.  Orchestrating and maintaining comprehensive, deep tagging is never easy.  Log file analysis, while often disdained, has utility for situations where page tags are insufficient (say you want to detect how search bots crawl your site) or when tags are impractical (mobile).  Packet sniffing can be beneficial when you can’t tag or access log files.  In fact, some combination of hybrid data collection, for example page tags and logs, might be the best option for a given situation.  It’s up to you to work with your team to determine what method is most appropriate to use to reach your goals. 
• Realize that your IT department is your ally.  Marketers can’t do web analytics without IT.  Whether they help you include page tags, locate and synch your log files, or monitor the implementation of your packet sniffer, you will need to develop and maintain a relationship with IT.  You, the business marketer, may think quite differently about web analytics than IT, so work toward a mutual understanding that supports business and technology goals.
• Reconcile what it means to you when you hear that “Web Analytics isn’t easy… Web Analytics is hard!”  That’s a quote from Eric T Peterson.  He’s right.  You need people, processes, workflows, dedicated resources, teamwork, teamwork, teamwork.  How do you prepare an organization for something that is hard?  How do you prepare a team?   Training, education, evangelism?  Yes, that helps… You can make it easier by reading the books, checking out the blogs, going to the conferences, taking a UBC course, and participating in industy organizations like the Web Analytics Association.   

Web analytics tools can be outgrown, like houses, clothes, shoes, music, books, and ways of thinking about the world…  But how do you know when you’ve outgrown your web analytics tool?  In part 1, I began the list of five symptoms of an outgrown web analytics solution, which was spawned out a preso I recently gave.  The five symptoms include:

• Inadequate segmentation (covered in Part 1)
• Poor visualization (covered in Part 1)
• No custom reporting (covered in Part 1)
• Limited Integration 
• Cost 

So without further adieu, here’s the rest of the list and some thoughts regarding these symptoms (click here for Part 1):

• Limited Integration.  Soon after deploying a web analytics solution, you will become intimately familiar with clickstream data and simple counts of things (like page views) and measurements (like time).  You will hopefully have deployed Key Performance Indicators for understanding how effective your web site is at converting visits and meeting defined business goals.  Depending on the web analytics tool you use you may even have insight into the behavior and KPI’s of visitors from online channels like newsletters, search, and rss because you have applied “tracking codes.”

Soon will come a time when you may ask yourself how do I integrate data from other data sources?  You may want to bring data from an email service provider, CRM system, and registration databases, so that you can see delivery rates next to conversion rates from newsletters, or so that you may pass behavioral information about a visitor who registered on your web site.

You may want to move data out of your web analytics system.  Perhaps you want to feed your data warehouse?  Or you may want to feed web analytics data into a targeting system.   Simple XML-based feeds from a hosted solution may not suffice.  You will need access to your data in a open database. You may even want to stop non-human readable text and character strings from appearing in your reports. To do so you may need to lookup data using various methods in order to make rep