Showing posts with label Report Builder. Show all posts
Showing posts with label Report Builder. Show all posts

Creating an interaction analysis dashboard


Interaction analysis is looking at how visitors interact with your website or other digital property. Examples could be click through rates on rotating homepage banners, % of page scrolled, online tool/feature interaction, video play rates and pathing reports. With so many interaction possibilities being tracked and spread across multiple reports, this feels like a good opportunity to create a consolidated view in a dashboard.

Why should you bother?
Over a period of time your website can become a virtual dumping ground for the latest fad marketing trend such as "Like" and "Tweet" buttons, moreover you may have many interactive gadgets and controls but does anyone know if they're being used or is it just unnecessary clutter? By creating a dashboard dedicated to interaction you can educate your UX team on what's working and what's not. And with a data engaged design team a Digital Analyst is more likely to get buy in for proposed optimisation and experiments.



Making the dashboard
For the purpose of this example we'll be using the following software (others will do the trick too): And for our interaction analysis example we'll take Apple's homepage. As of this writing their UK homepage looks like this:


We'll be taking a screen capture of Apple's homepage and adding to our dashboard, it helps to include a visual representation of the user interface, without this the dashboard data is more challenging to interpret. In the example below I've added numeric labels with corresponding chart titles to make reviewing of the data super easy, regardless of analytic level. For some light analysis there's a country option (top left) that allows going one dimension deep. And here's what it looks like in Excel:



And that's it. Hopefully this gives you some ideas. Over a period of time you can build out a dashboard to cover important pages and funnels, some pages can take a while to fully document but the effort is worth it IMO. If you have any comments, questions or feedback please leave them below. And you can follow new posts from this blog on Twitter, Email or RSS.

Building an experiment dashboard


This article will explain a cool way of monitoring and presenting your experiments that will save you time and make you look (more) awesome! Prerequisites are you're familiar with; Adobe Target, Analytics/Omniture, Report Builder, Excel and you're using the Adobe Target plugin ...that being said you can probably repurpose this for other analytic and testing tool environments.

What problem does this solve?
Building an experiment dashboard gives you a single view of all your experiment metrics without having to create multiple reports spread across browser screens. Moreover it can also become your experimentation documentation, and the dashboard format will copy & paste easily into presentations, so ultimately you'll be killing many birds with a single stone (sorry birds).

How to do it
For saving time in the long run we want to make our dashboard reusable so this means creating templates per experiment type. The 'types' are defined by KPI and number of variants. So if you're running an A/B experiment and your main KPI is orders - this would be a template, likewise so is an A/B/C experiment with orders as the KPI. You may have another A/B template where registrations/installs are your main KPI ....you get the idea. Once you've created the template types for your common experiments you'll only need to change a couple of parameters in your excel sheet and hey presto everything works! So let's get started with an example; here are the steps to create a dashboard for an A/B experiment where orders are the main KPI.

Step 1)
Plan the dashboard. When running an A/B experiment one of my favourite reports is viewing the conversion/order rate daily performance versus the control. This simply shows whether it won or lost and by how much and is a great way to see if there were any anomalies to investigate. Additionally we want to see the running totals so our first 2 charts look like this:

The next 2 are very similar but this time we're looking at revenue per visitor:

And the final 2 we're adding are for distribution (how many order and visitors have been part of the experiment) and average order value:

Step 2)
Next we fire up Report Builder and add our data blocks, we need to use the "Campaign > Recipe" dimension which allows us to select the experiment recipes/variants.

It's advisable to have a "settings" sheet in the Excel document where we can add; the running date of the experiment and the "Campaign > Recipe" values. The data blocks will then reference the cell locations (as it's doing in the screen captures above and below). For future experiments it means we just change a few Excel cell values and everything works opposed to editing a load of data blocks - which isn't fun.

Campaign > Recipe values:

Step 3)
Add calculated fields, conditional formatting, charts and make it look pretty. I'm not going to go into detail as I'll assume you know Excel and the template used in this example can be downloaded below.

Step 4)
Optionally you may want to add a section for describing the experiment and documenting the outcome. In a separate sheet you can also add screen captures of the control and variant content.

And once done the final output will look something like the below. It's worth noting that we should try not to go overboard with charts, our goal is to have a good overview. We can dig deeper if needed by going to our Analytics tool. That being said adding metrics such as visitors, orders and revenue trended seems perfectly valid.


Hopefully this was useful - the Excel template used in the above example can be downloaded here. If you have any comments, questions or feedback please leave them below. And you can follow new posts from this blog on Twitter, Email or RSS.

Cohort analysis - Adobe Analytics/ Report Builder

This article will show you how to carry out cohort analysis using Adobe Analytics/ Report Builder. For the purpose of this example a fictitious company called "Acme software" has a 30-day trial application and we'd like to know when orders are taking place post the trial download. This will mean using download date as a cohort and comparing it to the order date. Although this scenario might not be relevant for you, the basis of this article can be adapted for whatever cohorts have meaning, for example; order, newsletter sign up, registration, install, etc.

1) First off we'll create an eVar for storing the download date - which we've called "First touch download date", we're storing the date in YYYY-MM-DD format (this is an Excel friendly format too). Allocation should be first touch (means it won't be overwritten), and we've set the expiry to 90 days. Adding classification might make things easier for you, so this should be a consideration - for example; week number, month.


2) Now that we have an eVar for storing when the download occurred we need another for comparing when the order happened, we use the same format as before; YYYY-MM-DD and we're calling this "Last touch date". This is simply the current date and will be attributed to the order or any other event we want for future cohort analysis.


3) Next we're going to build a segment, this won't always be required but I suspect it'll be a common requirement when building cohorts. So for this example I want a segment that only displays a particular downloaded product ("Acme software") and only visitors that have completed an order - this will really refine our data request. Our segment uses a Visitor container with our downloaded product and sequential order event.


4) Now to Report Builder - apply our segment, dates and apply aggregated granularity:


5) Next add our 1st dimension 'First touch download date'.


6) Click "next" and add our 2nd dimension 'Last touch date' and add the order metric. Our preview now looks like this:


7) Run the request and our Excel output looks like this:


8) We now add a 'days difference' column which is a simple subtraction of order and download date which will return an integer. Our excel sheet now looks like this:


9) The final part is to create a pivot table based on the 'Orders' and 'Days difference' column:


And Voila! With this data we can now create line charts that tell us when we receive orders based on the download date cohort:

Monitoring your Adobe Target campaigns

When you have tens or hundreds of tests running across your websites you need a way to monitor all your campaigns to be sure everything is okay. Adobe Target makes it very easy to change content and I've experienced situations where "Offers" have been edited in error which has resulted in incorrect or broken "Offers" being displayed, moreover several situations where mboxes have been mistakenly removed resulting in the termination of a test. Unfortunately there's no "out of the box" way to quickly review all your campaigns on one screen. The workaround I'm going to propose requires that you have; SiteCatalyst, Report Builder & the TNT integration Plugin.

Step 1) Create a data block using Report Builder using your Adobe Target Campaign as the dimension, I usually look at the last 7 days.


Step 2)  Add orders to your data block and you're nearly done.


Step 3) I now schedule the report so I receive daily and add an Excel "Sparkline" so I can see a trended view of the orders. You can see from the graphic below, this is a pretty basic health-check however it's normally enough to tell you whether something has gone wrong. Hopefully Adobe will look into adding improved reporting options in the future.

(Click to enlarge)