#Measure Plaque for charity: water Project

As many of you remember, back in December the #Measure community rallied together to raise an astonishing $5,260 to provide clean drinking water for a very needy community.

Because we raised over $5,000 we are allowed to provide a short message to be written on a plaque that will designate who sponsored the project. The message on the plaque can only be 50 characters, including spaces. Messages are due by June 15, so I’m coming to you, the community who helped fund this wonderful project, for ideas on what our plaque should read.

In about 18 months, photos of the project will be posted along with the village name and information, and GPS coordinates to the well.

This is very exciting and I’m so grateful to be part of such an amazing community.

If you have ideas for our plaque, please leave them in the comments.


Posted in Tao of J | 4 Comments

Custom Omniture Dashboards: Part 1 – Getting the Data

Back in April I wrote a blog post titled ‘Analytics All-Stars: Create Custom Dashboards Using APIs.’ The post described the high-level framework needed to create actionable dashboards outside of the SiteCatalyst interface. After publishing the post, I received comments from several people asking for more detailed instructions on how to create custom dashboards, so I decided to create a 3 part series detailing each step in the process.

Part 1: Getting the Data
Part 2: Storing the Data
Part 3: Building the Dashboard

Your assignment. Create a custom dashboard to display your site’s top 5 pages. The dashboard will be delivered to executives daily and will trend the page views for each page against the previous day as well as the previous same day of the week.

By the end of Part 3 of this series, you will have all the information you need to complete your assignment.

Part 1: Getting the Data

In Part 1, we will review how to extract data from your Omniture SiteCatalyst report suite using the SiteCatalyst Reporting API.

What you will need:

→Undertanding of Omniture’s REST API
→Access to a SiteCatalyst report suite with data
→A SiteCatalyst user with Web Service Access rights
→A server running PHP
→A working knowledge of PHP
SimpleRestClient.class.php

The Rest API

Before we go any further, I strongly suggest that you take a few minutes to read Andreas Dierl’s post titled ‘How to start with the Omniture REST API in PHP.’ In this post, Andreas provides a great overview of how to use the REST API to retrieve data using the SiteCatalyst Reporting API. His post will serve as the foundation for this series.

Let’s begin….

Web Service Access

We will need a user that has Web Service Access for your SiteCatalyst login company. To give a user access rights, you will need to be a SiteCatalyst admin.

Navigate to Admin–>Admin Console–>User Management

Edit the user account for the user that you will grant Web Service Access to. In the ‘Access’ area of the User Management screen add ‘Web Service Access’ as shown below.

Make note of the ‘User Name’ and ‘Shared Secret’ we will need these values shortly.

Connection Details

We will need to gather a few other details in order to successfully connect to the appropriate SiteCatalyst Report Suite.

API Server: If your repor suite is located in San Jose then your server will be ‘https://api.omniture.com‘ If your report suite is located in Dallas then your server will be ‘https://api2.omniture.com‘ If you don’t know where your report suite is located, contact ClientCare.

Report Suite Id: Retrieve the Report Suite Id for the suite you wish to extract data from.

Download SimpleRestClient.class.php

As mentioned in Andreas’ post, we will make use of an existing class, SimpleRestClient.class.php, to make coding our script a bit easier. Download the script before continuing and upload it to your server. NOTE: To keep everything organized, create a new directory to house all the files associated with this project.

Download Omniture REST API Template

Rather than building the script from scratch, I highly suggest modifying an existing template. Download the Omniture REST API Template that was developed by Andreas Dierl.

Rename the file to ‘dashboard.php’ and upload to the same directory you uploaded SimpleRestClient.php.

Configure the Script

Now that we have a template in place, let’s configure the script to retrieve data from your report suite. Open the script in your favorite text editor and make the following updates:

→Line 5: $username = ‘INSERT_USER_NAME_HERE’;
Update this line to contain the Web Services User Name that we created previously. It will look something like ‘login:company’

→Line 6: $secret = ‘INSERT_SECRET_HERE’;
Update this line to contain the Shared Secret that we created previously. It will look like a random string of numbers and letters.

→Line 11: $server = “INSERT_SERVER_HERE”;
Update this line to contain the server associated with your Report Suite. Either ‘https://api.omniture.com’ or ‘https://api2.omniture.com’

→Line 26: “reportSuiteID”:”INSERT_REPORT_SUITE_ID_HERE”,
Update this line to contain your report suite Id.

You can optionally update lines 27 and 28 to change the reporting time frame. For this exercise, we will run the script daily using the previous date as our timeframe.

To automate the script, we would need to programmatically assign the ‘dateFrom’ and ‘dateTo’ to ‘YESTERDAY’ rather than hard coding a date. You could use the following:

date(“Y-m-d”, strtotime(“yesterday”));

Save the updated script to your server.

Test the Script

That’s it! We are ready to test the script. This script will return the Top 5 Page Names by Page Views for the selected period. This is a simple example we are using to teach the process, you would update the Elements and Metrics used in the script to match the data needed to create your custom dashboard.

To test your script, point a web browser to the location of your script, something like ‘YourServer.com/omniture/dashboard.php’

If everything is working as we expected, you should see a list of your top 5 pages in the format of ‘Page Name – Page Views’

Example Report Output
Page – PageViews
Corp : Home Page – 41
Corp : The Management Team at Keystone – 22
Community : /community/ – 22
Corp : Services – 16
Corp : Contact – 12

In Part 2 we will talk about how to take the output from the script and insert it into a database.


Posted in Omniture, Omniture SiteCatalyst, Web Analytics | 3 Comments

Failure is an opportunity

Failure is an opportunity.
If you blame someone else,
there is no end to the blame.

Therefore the Master
fulfills her own obligations
and corrects her own mistakes.
She does what she needs to do
and demands nothing of others.

~Tao Te Ching


Posted in Tao of J | Leave a comment

Mobcast: Valued Customer Service to Bagging Your own Groceries!

Measure MobCastOn todays show we discuss measurement as it relates to customer service and aspects of social media. Please feel free to add your thoughts and comments as we strive to make the show better every week. This week Michele Hinojosa joins us….. so that makes things better already!

Direct Download Link
Podcast RSS Feed

Segment One – Customer Service – Is it measurable?

1:00 – Michele Hinojosa joins us on the cast!
3:20 – Customer Service – Is it measurable?
5:00 – Are digital and social media based customer service teams doing a good job of integration with brick & mortar locations?
6:00 – Silo’s – We dislike them here at the Measure Mob, seems all they’re really good for is storing corn!
12:00 – Jason rants! Customer service centric business’ to bagging your own groceries?
14:00 – Customer service, a cost center? or valued department?
17:00 – CRM and web data integration
20:00 – Do we need a digital data czar?
28:00 Discussing a culture where by it’s ok to make mistakes. (Inspired by Evan Lapointe)

30:00 Goofy Break Time – Michele tells us what Jojoba and #TeamEvilForces means. (Inspired by Jeff Katz & Emer Kirrane)

Segment Two – Does the act of measuring effect good intentions?

36:00 Sponsored Tweets — Spam or value add?
40:00 Let social people be social and let analylists do the analysis.
48:00 Jason says, “If we couldn’t measure social, too bad, you have to be in it!”
50:00 Don’t measure because you can. Measure to solve business problems and make people more effective!


Posted in Marketing, Social Media, Web Analytics | Leave a comment

Analytics and Social within the organization, a mystery yet to be solved?

Measure MobCastWow, today’s podcast reached pretty deep into organizational structure, the value of data, social media integration, proof of value case studies and more! We really could have broke this up into a few Mob Casts! Find the show notes below for a snapshot of the show:

Direct Download Link

1:00 min: Social Media & Web Metrics — Stuck in Silo’s
6:00 min: How does leadership effect the use of data across the organization?
7:40 min: Setting up organizational outcomes and rewards.
10:30 min: Who’s in charge of defining where analytics and data professionals sit?
14:00 min: Are analytics professionals doing a bad job marketing their own value?
18:30 min: Jason shares his experience being stuck in a silo. You can’t keep this guy sequestered!
22:00 min: what can an organization learn from the structure of a professional sports team?
25:00 can the measure and analytics industry help the organization better understand the value of analytics?
29:00 Social Media and web data case study.
35:00 Do we need a digital czar in an organization
40:00 Insights from a Twitter conversation with Kevin Hillstrom aka @minethatdata
44:00 If the C-Suite is not defining KPI’s and setting measurable objectives is the organization screwed?

Also in the cast we give a little shout out to a great upcoming Web Analytics Association event coming up in Boston called The Evolution of Analytics: From Site to Social to Mobile to Predictive Some of us are hoping to make it there and heck maybe get some live interviews from the field!

On Todays show:
Jason Thompson
Keith Burtis and
Olivier Blanchard

You can also download and subscribe to the Measure MobCast on iTunes (Will launch iTunes app)
If you have any thoughts or comments on todays cast we’d love any feedback as we’ll take any data you have to make the show a better one. Thanks!


Posted in Marketing, Web Analytics | 2 Comments

The Measure MobCast

I’ve recently begun a new project, with a couple other buddies of mine, called the Measure MobCast. It’s a weekly podcast covering everything from traditional web analytics to marketing to social media and everything inbetween.

The first two episodes of the podcast are already out:

Influence, Lame Buzzword or Qualitative Metric?
“On the inaugural launch of the Measure Mobcast we have a spirited discussion on “Influence”. It seems like almost daily there is another tool launching to put a dollar value on our Twitter profile or measure our so called “Influence” in the social media channels. Whether you think influence is the latest and greatest metric or whether you think its a hoax I have no doubt you’ll get a lot from this discussion.”

Analytics and Social within the organization, a mystery yet to be solved?
“Today’s podcast reached pretty deep into organizational structure, the value of data, social media integration, proof of value case studies and more! We really could have broke this up into a few Mob Casts!”

You can also download and subscribe to the Measure MobCast on iTunes (Will launch iTunes app)


Posted in Marketing, Social Media, Web Analytics | Leave a comment

Don’t Track Me, Dude!

All of us have opted-in to being tracked for an eternity. This opt-in decision was made for us the moment our parent’s decided to have sex or perhaps even earlier at the time of the Big Bang. Before you completely write this idea off as far fetched, give me a moment to try to explain.

First, I think it is important to understand what we mean we we use the word ‘track.’ I believe when most people say “do not track me,” they are really saying “don’t analyze me.”

Merriam-Webster defines ‘track’ as: detectable evidence (as the wake of a ship, a line of footprints, or a wheel rut) that something has passed.

Regardless of how hard we try, every action we take leaves a track.

When we talk about ‘tracking,’ we are really talking about putting tools in place to amplify this detectable evidence to make the job of the analyst easier. However, a skilled analyst, detective, archeologist, etc. will be able to analyze this evidence regardless of the technology that is in place.

Governments are wasting billions of tax payer dollars to legislate against the laws of physics. Corporations are wasting billions of man hours attempting to do the same. They are giving consumers a false sense of security that if legislation is in place or if browsers have a “do not track” option then no detectable evidence will be left behind. That is not only a silly conclusion but it also violates the basic laws of physics. To every action there is always an equal and opposite reaction. Every action we take, we leave behind detectable evidence, we can’t fight that fact.

Legislation and new technology can serve to counter act the forces of nature for a given period of time but on a long enough time line, nature will always win. If you disagree with the law of gravity, you can build planes that can fly through the air for longer and longer periods of time but eventually every thing that goes up, must come down.

The technology that analysts use, simply will adapt to the current landscape. Today it is cookies and page tags, yesterday it was web logs, tomorrow it will be something else but let me reiterate, even if these tools of the trade are not in place, the evidence that something has passed is there just waiting to be discovered and analyzed.

So what does this all mean? To me, it means that as someone trusted with this evidence, I must be held to a higher standard. The same is said for anyone in a position to view information that the rest of the world is not privy to. We expect our doctors to hold our patient records in strict confidentiality. When we make a phone call, we expect our cell phone carrier to not abuse the information contained within our conversations. As web analysts, we have been placed in a similar position of trust.

Passing legislation and inventing new technologies to ensure no traceable evidence is left behind is as pointless as spending billions of dollars trying to stop the sun from rising in the East. Rather than fight the unchangeable laws of physics, why not put that time and energy into making sure that those who have been trusted with sensitive evidence treat it with the respect it deserves?

Legislation is pointless. Technology will only produce a false sense of security. Aligning with a Code of Ethics is the only path.


Posted in Tao of J | 3 Comments

Social Media Isn’t a Marketing Channel, Don’t Measure It Like One

Just because you “can’t allocate revenue” to each Social Media interaction, doesn’t mean you shouldn’t be there. Social Media is just another location where your customers may or may not be. If they are there, then you should be there.


Posted in Tao of J | 2 Comments

Analytics All-Stars: Create Custom Dashboards Using APIs

At Omniture Summit 11, I was honored to be part of the Analytics All-Stars team. In the break-out session, I talked about how you can make use of APIs to create custom dashboards that drive action.

One universal truth I have discovered, after working with many different companies to optimize their analytics practice, is that no two companies look at data exactly the same way. The major analytics players in today’s market have done a fantastic job at providing product offerings that cover a large part of most customer needs. However, it is not possible for a single solution to align perfectly with every customer’s needs and if it were, the product would be so bloated that no one would want to use it.

So if my analytics package of choice doesn’t present the data in all the ways my key stake holders demand, what options do I have? Many, if not all of the top vendors, have a set of APIs that allow you to export data out of the applications so that you can present the data in a way that better aligns with your business needs.

The desire to present data in ways other than what is available in out-of-the-box reporting seems to be high on everyone’s agenda, however I was shocked when I asked the Omniture Summit audience how many people were making use of the APIs and I saw less than 10 hands go up in a room of well over 250 people.

Building applications and dashboards using APIs doesn’t have to be scary. Let’s walk through a custom dashboard that I built using the Omniture Reporting API.

NOTE: If you are an Omniture customer and you want more information on using the APIs, there is a ton of great information inside the Developer Connection.

The following is the high level data flow for the custom dashboard I developed:

{click for full size}

1. Omniture Data Store: This is the Omniture Report Suite that contains all of the click-stream and conversion data for my site.

2. PHP Application: The PHP application is the engine the drives the process. It is a simple application that extracts data from Omniture, loads the data into an internal database, and then transforms the data into a format that aligns with business goals. It it scheduled to run on a daily basis at 4 am via a cron job. The first component of the application extracts data from Omniture using the Reporting API and loads the data into a custom MySQL database that has been setup to accept the specific data points being extracted from Omniture.

3. Internal MySQL Database: A custom MySQL database was setup with a table structure to match the specific data points that are being exported from Omniture in step 2. This allows for custom trending calculations that may not be available out-of-the-box with Omniture.

4. PHP Application: At this point, the data has been exported from Omniture and is now being stored internally. This component of the application transforms the data into a format the business is more familiar, complete with custom trending. Once the dashboard has been properly formatted, the application deliveries a daily copy of the dashboard, via email, to a list of subscribers.

The following is an example of a daily dashboard that is built using the process described above. Although this is a copy of a real dashboard, the dashboard has been populated with fictitious numbers for privacy reasons. The dashboard shows key conversion metrics for 3 segments of visitors.  The conversion metrics are trended against the 4 previous same days of week and a 7 day average.

{click for full size}

If you are interested in extending your reporting by using APIs and need a little help, please feel free to reach out to me, I’d be happy to point you in the right direction.


Posted in Web Analytics | 6 Comments

Analytics All-Stars: Think Before You Code

At Omniture Summit 11, I was honored to be part of the Analytics All-Stars team. One of the topics I covered in the break-out session was centered around the key things that should be done before you begin deploying tracking code.

Getting access to a new analytics package is like unwrapping that shiny birthday present that has been sitting in the corner of the room. It’s very tempting to rip off the paper, tear into the box, and start playing. However, based on the experience I’ve gained from participating in well over 100 different implementations, I’ve found a common thread that has run through the most successful implementations. That common thread is patience.

When I took the position of Manager of Web Analytics at Spark Networks, I felt the pressure of “getting things going” right out of the gate but I quickly learned that it was ok to push back. It’s ok to walk before you run. Managing a successful Analytics practice isn’t a sprint, it’s a long, long race and those who end up being successful learn how to pace themselves.

Before any code hit the page at Spark Networks, I spent several months getting a lay of the land. If it was my responsibility to provide insight to key departments within the business, how could I think about doing that without even knowing what those departments did?  I spent countless days literally sitting at the desks of product managers, marketing directors, executives, and developers.  After I had developed a better understanding of what made each department tick, I began to hold formal interviews, it was these interviews that formed that structure of the analytics implementation.

So who should you interview?  The following is a list of people I interviewed.  This list isn’t meant to be an exhaustive list by any means but should start you down the right track for your business.

→Marketing Director
→Email Marketing Coordinator
→Product Manager(s)
→General Manager
→Development Lead
→Developer(s)
→Customer Support Manager
→Customer Support Rep(s)
→Creative Director
→Office Manager
→CIO
→CEO
→CFO
→COO

My goal was to transform every employee in the company into a strong advocate for my analytics practice. I couldn’t accomplish this goal without taking into consideration everyone’s needs. You can implement the most perfect implementation the world has ever seen but if you fail to gain user adoption, your implementation will also be a failure.

You can read more about how I branded and marketed the analytics practice in my blog post titled ‘Are You Branding Your Internal Analytics Practice?

Use notes from your interviews to document requirements and make note of gaps in the current process. From there, develop a blueprint of what will be captured, where and when. This can take the form of a simple spreadsheet.

Now, break up your implementation into a series of phases, NEVER try to deploy everything all at once. For one it becomes too large of a project to deploy in a timely manner and it sets a bad precedent that the implementation will be complete after the initial rollout. If you remember nothing else from this blog post, please remember that an implementation is never complete, it is a living, breathing thing that needs constant care or it will die.


Posted in Web Analytics | Leave a comment

Switch to our mobile site