Sunday, March 16, 2014

"I want my Sitecore Analytics data in Excel"

Why should I care about Sitecore in Excel?

No matter what you've spent on reporting systems (and business analysts to run those reporting systems), inevitably there are still spreadsheets all over your organization.  I can't think of a company I've been at or worked with that doesn't have at least one Excel Workbook that is the voice of truth.  The person that owns it has confidence in it--the data has overcome the skeptics, and the Excel interface is common to all and within everyone's grasp.

Sitecore data can now join in.  Let's forget about the "but I should have dashboards that tell me what to look at" crowd.  You know that if you get all this great data in Excel, you'll be in control and will start to highlight the insights and outcomes that is important to your business and your business only.  You'll pivot, shoot...score.

Familiar Pivot Tables and Charts

With Sitecore data in our OLAP cube format (more below), within about 15 minutes I created the Pivot table and chart below.  Our Sales Engineering group will certainly be looking at more insightful dashboards as we go, but these simple views can get us to the next stage of our discussion:  "How can we put together a customer journey that will promote the best possible software evaluation experience, leading to Sitecore being selected as the best choice in digital platforms?".

Sitecore Data in MS Excel Pivot Tables and Charts

Sitecore's Engagement Intelligence Datamart 

To get to this, we are using Sitcore's Engagement Intelligence Datamart.  This product provides the tools necessary to create a standardized OLAP cube from the Sitecore Analytics database.  Once in an OLAP format, virtually any reporting environment will "understand" what the data is all about.  OLAP will define Dimensions (the facets, categories, rows, columns) and Measures (the values, numbers, calculations) that the data is now available in, and we can immediately use the standard interfaces of Tableau, MS Excel, SQL Reporting Services, Sitecore's implementation of the Targit BI Suite or any business intelligence strategy you currently have in place.  We can start thinking about easily tying to other data sources, tying authenticated users to CRM records....sky's the limit here.

So, after following the Engagement Intelligence Datamart documentation, we have the OLAP cube in our SQL Server instance:
The Sitecore OLAP Cube Database in SQL Analysis Services

Right clicking on Cubes/Analytics node gives us the option to "Browse" the Cube.  This provides a design interface very similar to MS Excel, where we can drag the Dimensions and Measures from the Cube to a canvas where we can analyze all the prebuilt calculation goodness.  Below I simply added our Pattern concept in Sitecore and used the single measure of Page Views:


Exporting to Excel

From here, there's a nice little export feature to Excel at the top of the window:



You can also start in Excel and use the Data menu to create the connection string to your OLAP cube database on SQL Server.  The above export feature will create the connection for you automatically.

Now in Excel, we can take advantage of our familiarity with this application--Pivot Tables and Charts, Slicers and all of the easy-to-use data analysis tools that Microsoft has provided.  Below is the Pivot Table fields that will be immediately available to you.  Within the list, you'll be able to find common web analytics elements such as:
  • Page Views
  • Unique Visitors
  • Time Spent on Page
  • Engagement Value (unique to Sitecore)
...and much more.  Happy Pivoting.

Pivot Table fields available from Sitecore's DataMart / OLAP Cube





Wednesday, March 12, 2014

Preparing for your next great Sitecore Engagement Plan

In every partner and client session I facilitate, we inevitably spend a lot of time talking about Sitecore Engagement Plans.  It's a fantastic platform feature that ties all the pieces of a Sitecore digital marketing discussion together--from considering why a site exists in the first place to laying out the goals we want our visitors to achieve to the actions we want to take in the process of creating hugely successful digital campaigns and experiences.

By the time we're talking about Engagement Plans, though, I've realized that we've already covered a ton of information.  Sitecore's feature map is incredibly impressive and always too much to fully consider in one sitting.  When I started facilitating these sessions, I tried to have the group go through the actual mechanics of setting up an Engagement Plan in the system.  While these mechanics are straightforward, I realized over time that the importance of the discussion wasn't about the points and clicks to create the Engagement Plan in Sitecore--it was the about the customer journey we were setting out to model.

So, a very simple thing hit me over the head--start with a Visio template to act as the brainstorming tool.  While I still recommend in most cases just diving into Sitecore and creating Engagement Plans directly, I wanted to offer this file in case it helped anyone with their brainstorming sessions along the way.

Download the Visio Template Here.

The Visio diagram is a model of our Launch Sitecore Engagement Plan described here.  With this, you can quickly brainstorm:

  1. States along your Engagement Plan / Customer Journey
  2. Actions to take as a visitor transitions from State to State
  3. Conditional checks to determine whether a visit should move to a new State
  4. Customer experience as it relates to a particular state (personalization rules if a visitor is in that State)
  5. The behavior you are trying to drive, the endgame, the Goals.

Content-As-A-Service and the Sitecore Item Web API

Why you should care about the Item Web API

There are many great articles and videos about using the Sitecore Web API, many of which are much more complete and sophisticated than this post (for particularly impressive skill, see Mike Reynolds's work).  In this post I simply wanted to point out the basics and explain why you might be interested in this Sitecore feature (and, really, why you should be confident in the power of the Sitecore API in general).  So read on as a non-developer.  As a developer, you'll at least get a couple quick lines of code that might save you some time as you dive into things.

The Sitecore Item Web API documentation may be found here.  The latest version is 1.2, and the feature is now part of the core Sitecore install (as of 7.1).  The basic premise of this feature is to expose the Sitecore API to modern, RESTful web service calls, to return JSON responses, and (as is always a core tenet to Sitecore) to provide an extensible basis for modeling virtually any business and technical requirements.

In plainer English, this makes Sitecore-curated content available outside of Sitecore sites.  It allows you to ensure all of your content policies are followed (workflow, validation, security, publishing) before making that content available to additional groups or applications.  Sitecore-Content-As-A-Service.  (Feel free to use SCAAS and sound cool).  By providing a modern RESTful service layer, it makes your developers happy and allows them to use all the productivity tools they are using today.

To consider a very simple use case, I'll use our team's Launch Sitecore project and consider an area of content that I'd like to make available to an external application.  The "Team" section on the site lists all of our N. American Sales Engineers:

Setting up the scenario

Let's say that we're starting a separate project and we want to start by leveraging this list of SE's.  Maybe we consider Launch Sitecore to be the place where we first add new SEs once hired and where we have some additional statistics and information about the SEs (# of articles written, favorite quote, etc.).  By defining Sitecore as the system of record for this content, it frees us from worrying about content governance and consistency.

To keep things really simple, I tried to include as few lines as possible to accomplish this via the Sitecore Item Web API.  First, the final result of the new application page:

A simple list of Sitecore content items (without that pesky styling getting in the way!)

Next, the HTML behind the page


<!doctype html>
<html ng-app>
<head>
    <title>List of Sales Engineers</title>
    <script src="https://ajax.googleapis.com/ajax/libs/angularjs/1.2.14/angular.js"></script>
    <script src="../js/myangular.js"></script>
</head>
<body>
    <div ng-controller="CallWebApi">
        <ul>
            <li ng:repeat="item in data.result.items">{{item.DisplayName}}</li>
        </ul>
     </div>
</body>
</html>


A couple things of note on the above:

  1. I'm using angular.js to allow the javascript library to do all the heavy lifting.  The first script reference is to that library as hosted on Google's CDN.  The second is simply my project's local javacript file that we'll look at.
  2. All of the "ng-" stuff is standard angular.js usage.  The ng-controller will call out to my local javascript method that we'll discuss below.  The ng:repeat will allow me to iterate through all Sitecore items I receive back from my web service call, showing each item's DisplayName field in a bullet list.
  3. Take special note of the "data.result.items" syntax above.  The bulk of time you'll spend (probably with any JSON parsing exercise) is figuring out how to pull out the specific nodes and fields you are interested in.

The javascript to make the call and return the Sitecore items:


function CallWebApi($scope, $http) {
    $http.get('http://mvc71/-/item/v1/?scope=s&query=/sitecore/content/home/team/*').
        success(function (data) {
            $scope.data = data;
            console.log('success ' + data)
        })
        .error(function(data) {
            console.log('failure ' + data)
        });

The document on SDN does a great job explaining the possible operations and queries that you can make with the Item Web API.  For now, consider that you can do things like:

  1. Get Sitecore Items
  2. Create Sitecore Items
  3. Create Media Library Items
  4. Change Items
  5. Get back the HTML output of a rendering
For this scenario, we're simply getting some Sitecore items and using their fields.  The query above makes a request to Sitecore to get back all the items in the "Team" area of our Launch Sitecore content tree.  In my case, that result becomes available to my angular.js within my page to list out DisplayNames for the Sales Engineers.  Below is the structure of the JSON that we receive back from the request:


In Summary

While this is a very modest use case, this really provides the foundation for incredible real-world use cases within your organization.  With Sitecore as the content hub, you are able to ensure your content-as-a-service project is fully governed.  Your mobile apps and sites will benefit from the "create once, use everywhere, maintain once" pattern this promotes.

The Item Web API is fully extensible and built on the same core pipeline architecture that drives everything in Sitecore.  Because of this, additional features and methods are able to be easily added to the standard set, and virtually any external application content need may be serviced by Sitecore.

Friday, January 31, 2014

A New and Improved Engagement Plan for Launch Sitecore

While Chris Castle, Brandon Royal and others were busy getting the new Launch Sitecore site out the door, the N. American Sales Engineering team at Sitecore got together to review our first implementation of the digital marketing features of our site.  Our goals have always been clear with Launch Sitecore--provide the best software evaluation vehicle in the business.  Allow folks to download the full site, support them as they dive into it and get to the next level of understanding and questions.  Provide a clean and simple framework to strategize much more complex real-world situations.

I always feel that the Engagement Plan discussion in Sitecore can become the centerpiece for the larger digital strategy discussions for the platform.  There's something about specifically discussing customer journey paths in the tool that expands ideas while focusing purpose.  Engagement Plans become the hub for modeling visitation flows, for defining integration points and messaging, for clearly identifying compelling personalization possibilities and more.

In our first iteration of our Launch Sitecore Engagement Plan, our flow was ultra-simple.

  1. Entice registration
  2. Convince visitor of the benefits of downloading the Launch Sitecore site package
  3. Provide a feedback loop
As a summary, "create incredibly valuable evaluation experiences for our prospects".  We had other side goals, but in essence our site existed to provide access to this great evaluation package, and everything we focused on was a funnel around that endpoint.

For this release, our goals are significantly loftier.  We started discussing our Sales Engineering Team goals in a broader context, at the company level.  Our team is here to ensure that our prospects have the very best evaluation experience in the industry, that they make the most efficient use of the incredibly small window of time generally dedicated to evaluating a software purchase.  In this window it is our job to show people why we are so proud to represent this platform, showing the balance of the ease-of-use and simplicity of entry points while starting to highlight the incredible platform power that lies deeper in the application.

Our main goal of making our Launch Sitecore download available hasn't changed.  With this release, however, we are setting the stage for the download journey to be the beginning of the path towards our loftier goals.  In essence, we are starting to analyze not only the flow our visitors follow as they navigate the Launch Sitecore content and download the package, but we are looking forward to the incredible insight this will lead to as we evaluate the place Launch Sitecore has in an overall Sitecore selection process.

I'll discuss the new plan in its two major sections.  The first section below is similar to our entire flow in our first version, where everything led to a download of the Launch Sitecore package:

The first "stage" of the new Launch Sitecore Engagement Plan

As you'll note, we don't evaluate every visitor to Launch Sitecore for this plan.  Our first goal, and the event that actually enters a visitor into this plan, is the fact that the visitor registered with our site.  While certain plans lend themselves to create flows for authenticated and anonymous users, our making the download of Launch Sitecore available requires that our visitors provide registration information.

Once again, our main decision point is whether or not our registrant has downloaded the Launch Sitecore package.  This is very easy to evaluate--we keep these downloads available in our Sitecore Media Library, and a request to this item in the Media Library will inform the Engagement Plan that "Yes" path should be followed for the "Downloaded?" question.

Instead of just sitting on the yes/no question about whether our visitor has downloaded, we take the opportunity to further assess his/her level of engagement with the content available in the site.  You'll see terms like "Qualified" and "Engaged" which simply represent our own checkpoints about whether our content is providing valuable results.  For instance, the "Qualified" check represents an overall Engagement Value Points check.  (Has this visitor spent some time, read a bit about our Sales Engineering Team, etc.?).
The Rules Engine Check for a threshold of Engagement Value points

Engagement Value Points may be achieved as our visitors are finding value within the site.  While the value of 7 is our own arbitrary threshold, we decided that it represented a reasonable blend of potential goals and activities our visitor would experience for our definition of "Qualification" or "Engaged".  The nice thing here is that we can use these state transitions as personalization triggers.  A "Qualified" visitor, for instance, will simply get some slightly catered messaging on the bottom of the home page, appreciating the fact that they've spent some time with us and encouraging them to do more.
Personalized messaging on the home page based on Engagement Plan State

So far, so good.  We are now able to consider messaging that will gently nudge our visitor towards the goal of downloading Launch Sitecore.  On to stage 2, where this year we will be striving for much more significant insights around how our evaluation teams decide to select the Sitecore platform.

The future stage of our Engagement Plan represents some great opportunities for this insight.  We know that the success of this part of the Engagement Plan is going to be our connection to our own CRM data (Dynamics).  Take a look at the stages our visitors will transition to, and then I'll discuss the ideas around that very important integration point.
The post-download phase of the Engagement Plan


This set of States represents the success (or failure) of the overall Sitecore evaluation experience.  Sitecore is, and has always been, a fantastic data integration platform.  In contrast to many systems out there, Sitecore never enforces that data be native to Sitecore in order to fully leverage in Sitecore-initiated decision point events.  This Engagement Plan is a perfect example of that.  Sitecore provides an incredible basis for this integration with Dynamics, where contacts that are managed and native to Dynamics become seamlessly integrated with this process modeled in Sitecore.

Since there is so much rich data in our Dynamics environment (opportunities that become prospects, partners, etc.), these contacts should always represent the system of record for these individuals and companies.  Our Engagement Plan will be able to leverage this information to assess State transitions--as our Launch Sitecore evaluators become customers of Sitecore, they will transition based on updates to CRM records and land in the appropriate Engagement Plan state.  We'll get insightful analytics around how our downloads could lead to purchases or how our evaluation flow should improve.

Beyond the incredibly rich Analytics that we'll get in Engagement Intelligence reports, our Engagement Plan itself will highlight these State transitions:
Engagement Plan Monitor Mode for State transitions

Along the way, we can use this Engagement Plan to discuss micro-segmenting opportunities.  A small example below (we don't have a ton of visitors yet) is an example of how I could create a list of all registered visitors who have downloaded Launch Sitecore and live in New Hampshire (note that I found 3 that fit those criteria):

Micro-segmenting with the Dynamic Segment Builder


Much more to come in future posts around this Dynamics integration and the insight we drive from this Engagement Plan analysis.

Thursday, January 30, 2014

The Sitecore Fitbit Project

On the second floor of the beautifully renovated mill buildings in downtown Newmarket, NH, a secret project has just concluded with the promise to change the world of digital marketing forever.  A small but growing software company set up shop just near Popper's Restaurant and just above Bloom'n Cow Ice Cream (meaning that many a brainstorming session was accompanied by beer, appetizers and gelato, depending on the time of day).  The four founding members of this startup decided that they were destined to rid the world of analytics confusion forever.

Over an amazing set of Oreo Coffee 3-scoop cones, the group tossed around the terms and concepts that had caused such inaction at the companies they left to launch this thing.  Big Data be damned. CLOUDy digital marketing strategies.  Consultant scare tactics.  Not at this new place.  There was going to be agreement--now--about the key metrics that would define success.  After all, there were only four of them.  How hard could it be for them to come to agreement about what success would look like for their company's built-from-the-ground-up marketing strategies?

Page Views, Time Spent on Page, Conversions, Bounce Rate, Average Visit Duration, Loyalty, Page Depth.  Already frustrated, the team decided to grab another beer and start again.  None of this felt right.  All these metrics represented a confusing mixture of commonly accepted values and certainly could provide great insight into their digital strategy.  But it felt dated too, very Web Page-centric.  After all, this company was launching their site, but they were talking much more about consistency of message, broadcasting messages through channels, speaking to their customers in short insightful sentences exactly when they were listening instead of dropping their book in Times Square and hoping the guy that tripped over it decides it's worth reading.

One of the founders slammed down his mug.  Looking at his wrist, he smiled and told the group confidently that he had it.  His Fitbit had just buzzed (an unfortunate miscalculation convinced his Fitbit that swinging a beer mug was good for his health).  He mumbled something about a single view of the truth, paid the check and told the team they had some work to do back at the office.

And so the Sitecore Fitbit project started.  The team had already decided that the Sitecore experience platform was what was needed at the core of their entire content and digital marketing strategy.  This team did their homework.  While the analyst reports initially led them to Sitecore, they put the company and the product to the test before this software purchase, and they hit it from the various angles these four professionals represented.  From their most technical, data-integration requirements to the ability to model their digital marketing dreams, Sitecore, in their opinion, had it all.

 (As a shameless plug to the N. American Sales Engineering team, they noted the use of Launch Sitecore as key to their evaluation).

The Fitbit idea added some fun to this.  Now, once the team decided on the key metrics defining success, they could allow Fitbit to be the ultra-simple feedback mechanism, the Pavlovian nudge to keep them on track towards their goals.  Gentle hourly pulses as things were moving along smoothly.  Fast shakes when things needed attention (either for crazy success or troubling dips).  Literally the heartbeat of the business on the four founders' wrists.  (Todo: have to find away to reduce the analytics noise from the hoisting of beer mugs).

The founder that had the AHA! moment opened the Fitbit API site on his laptop and projected to the group.  He started expounding on his single view of the truth statement, gathering agreement in the room that one of the main problems they'd all seen in the past was that, as a company grows, the charts and tables and numbers and metrics grow exponentially as well.  Wouldn't it be great if the feedback mechanism were much more simple, and the thresholds were defined so everyone agreed about the boundaries on both sides of the graph that would drive the right cadence of attention, discussion, strategy review, planning.

With the Fitbit app registered, now it was time to leverage Sitecore's analytics, publishing, reporting and data integration capabilities.  One of the great things that a team member remembered from their evaluation was that Sitecore already appreciated this concept of Value.  An Engagement Value scoring concept already exists in Sitecore.  This is the perfect abstraction that the group was looking for, and now it was time to specifically map their digital marketing goals to this concept.  While a single scoring mechanism like an Engagement Value could become the interface to Fitbit, it only needed to abstract--not to ignore or make irrelevant--the significant data points that lead to it.

The only real mantra for this company was an absolute, unrelenting commitment to their customer.  They commonly corrected each other whenever their conversations slipped to their own hopes and dreams.  Instead, the conversation was always (awkwardly sometimes) required to be spoken in the voice of their customer.  While the exercise sometimes became frustrating, the team knew that speaking in this customer voice would always lead them to ensure that it was the customer finding value from the company, and not the other way around.

So now it became a quest to define the thresholds, events and actions that would identify when their customers received value from the company.  The team had seen the capability they will have from Sitecore's analytics engine to gather scores of discreet metrics, dimensions, measures.  Now they saw that they they could abstract those discreet metrics into higher level categories that everyone could understand and communicate.  They could meet regularly and discuss the averages in these categories that for them would define ongoing success.  And their Fitbit on their wrist would congratulate them or warn them when things were happening on either side of these bounds.

An initial look back at the Sitecore Analytics offerings provided the group with the confidence that they really had everything they need.  A quick look at the Measures available in the Enagement Intelligence Analytics OLAP cube showed them all the usual suspects:
View of Measures within Sitecore's DataMart

Looking into the dimensions that could drive these calculations was even more telling--they would be able to look at these statistics for particular campaigns, for particular devices, for specific business accessing their content, in specific regions of the world and the country.  The DataMart was in a standard format, so they immediately started playing with the the MS Excel Pivot tables that would drive the deep analysis of the digital business.

But for now, it was back to the Fitbit app.  All of this great data needed to role up to events that would buzz wrists and lead to congratulatory beer raises or late night strategy tweaking sessions.  As the team started diving deeper, they realized that Sitecore had the key ingredients here as well.  Patterns would allow them to clearly define an audience segment they could cater to specifically.  Goals would allow them to define discreet events when their audience was gaining value within their digital campaigns.  Engagement Plans would allow the company to map the paths, and treat their customers to one-on-one digital experiences depending on the direction they took through that map.

With ideas a buzzin' (but wrists as of yet not), the team settled in on their first metric for Fitbit.  Average Engagement Value Per Day.  Simple.  But really powerful underneath.  Lots of work still to do to create an environment and a modeling of discreet Goals, audience Patterns and Engagement Plans that will drive this key metric for the business and gain consensus between the four founders that the digital strategy is on the right path.  Are customers finding information in the right place at the right time?  Are they talking about the company in a positive way on social channels?  Are they taking advantage of promotions and bringing their friends into the community?  Are they responding to mobile and email campaigns?

When customers are finding the value from the company's digital offering, a simple pulse hourly on the Fitbit will tell them they're on track.  And when that thing nearly shakes off the wrist, time to celebrate!

(So my startup software company is fake.  Yours, however is not ;)

Friday, March 8, 2013

The power of session-level analytics reporting in Sitecore Analytics

Some background on session-level analytics in Sitecore:


The conversation often comes up when discussing Sitecore Analytics: "when should I use Sitecore Analytics and when should I use xyz Analytics?".  The use of multiple analytics tools, the coordination between them, and/or the decision to standardize on one analytics tool is a significant topic, but from my perspective it's simply important to consider what the landscape of Sitecore Analytics provides.  On the surface:
  1. Sitecore has incredible analytics drill-down capabilities--from a list of recent visits, to all visits from a particular company or source, to an individual visitor, to an individual visit.
  2. Sitecore offers standardized OLAP cube data, and a set of sophisticated business intelligence dashboards
  3. Probably most importantly, Sitecore provides ACTIONABLE analytics.  Your reports are right there in your power tool of content authoring and publishing.  Now you can DO something with that analysis right away.
  4. Sitecore provides incredibly compelling segmentation possibilities.
Together these capabilities span the spectrum of the ultra-specific (an almost Tealeaf style capability of watching an individual session which could be interesting for many situations such as a high-price ecommerce transaction, evaluation of a sample session for usability, etc.) to the ultra-summary (the rolling up and tearing back down based on my own business’ dimensions or facets).

So for today, let’s get ultra-specific.  For those of you that have read other articles about Launch Sitecore, you’ll know that our purpose is pretty specific—create an evaluation package that’s best-in-class so that our prospects can quickly learn that Sitecore is the best platform choice on the planet.  For those of you that understand our Engagement Plans, you’ll know that this process looks like this:
  1. Through demonstrations and technical deep dives, our Sales Engineering team builds interest in having a prospect visit www.launchsitecore.net.
  2. While enjoying some articles about Sitecore, our visitor is really urged to login or register to get to the good stuff (the download of the package itself).
  3. After registering, the visitor wants to download the package (the site itself that they can apply to their local test installation of Sitecore).
  4. After a glorious evaluation of the product, the visitor (now our customer) tells us how great the experience was in an incredibly over-simplified feedback form.
So, since this is only intended to be marginally real-world, let’s go through this is a visitor, all in one visit and see what we get on the other end from the reporting side.

The Simulation:

First, visit www.launchsitecore.net.



Since we’re simulating a brand new visitor, we’ll go ahead and register:

We are so excited about Launch Sitecore, we want to get our hands on the package right away, and we choose to download the version for Sitecore 7.x:



As we read a Digital Marketing System focused article, we check out the slide out at the top right of the screen, used to show the type of information Sitecore is collecting about our visit.  We notice that we've been categorized in the Digital Marketer Audience Segment (based on a number of articles we've read, including the "Create a Goal" article.  We also notice that it seems we are investigating the site to a level that shows we have a "Detailed" interest in the content.  We're not just reading the home page--we've investigated some detailed articles about the Sitecore Digital Marketing System.


The Reporting:

In the Sitecore Marketing Center, we can find the Latest Visit report.  Lots more to talk about around this reporting interface itself (including filters, date ranges, etc.), but for today let’s get to the info about our simulation.  First, since I’m in my home office on a snowy New England day, I’m behind my Comcast ISP account.  Beyond the scope of this article is my ability to tag my visitor sessions with additional information (from forms filled in, from authentication events, etc.) that could further identify my visitors.  In addition, I chose to “categorize” all Comcast Cable visitors as “My Company”.  (I could have categorized this as “ISP” or anything else I’d want to use to describe visitors from the Comcast DNS resolution).

I could drill down to all Visits from Comcast Cable by clicking on that link.  That would then show me more specific visitor sessions (possibly with specifically identifying tags).  Since I just ran through the simulation, I know this session is mine and I’ll bypass that by clicking on the link under the Date & Time.

image

Now at the Visit (Session) Detail report, I get a nice snapshot of my overall visit.  Some things to notice:
  • We were able to tag the session with “MikeBlogTest” (the name I used to Register with the site)
  • We see that I visited by clicking on a link within my Blog
  • We see the total value of the visit was 85 Engagement Value points (with the breakdown of goal achievement following)
  • We get a nice breakdown of the Pattern Card shape that is emerging from my visit—the specific content profile key attributes that are accumulating based on my content consumption.
image

Further down in the report, we start to get even more detail about the visit, including:
  • The fact that my Campaign was triggered
  • Fields that were filled out in our registration form
  • Pages visited and specific duration for those page views
  • Goals achieved (Register)
image

Another page, and more detail to round out the entire session.  More goals and fields filled in.  One interesting thing I want to point out here is that we actually captured an “error” on the site (line 17).  Error is in quotes here since, depending on how we handled it in the application, this could have been completely invisible to the visitor.  While this isn’t in any way a sophisticated error handling technique (it’s not meant to be), it could provide incredibly valuable information to the reviewer of the report in the context of the site visit.  What this tells the reviewer is that when a visitor clicked on a Search Result, there was no presentation assigned to the item clicked on.  A nice bit of usability testing after the fact (hey, we can’t catch everything in QA).

image

The Summary:

While not every analysis requirement will focus on an individual session or individual visitor, it is important to know that we can drill down to this level.  This gives us an incredible foundation to consider ties to transactional systems (Ecommerce), CRMs and other data sets to develop a full picture of our customer experience and value.  This is the ultimate leaf of the analytics tree, while keeping the ability to aggregate and roll back up to the branches.  By rolling back up, we will be able to get this same insight at the company level (all visits from one of our prospects), at the Pattern level (with Sitecore's ability to model the audience segments, now I can use those segments to hold aggregate analytics), and much more....