One of the most complex reports we have available in Webtrends is the scenario analysis report.  It’s also one of our most robust, and can provide you with worlds of good information to help you optimize scenarios on your site.  But I’ve found that a lot of people aren’t exactly sure what the report tells them.  They see the information, but they don’t understand what insights are being given. 

That’s what this series of blog posts is about: demystifying the scenario analysis report and making it work for you.

Let’s start by talking about a concept that’s bandied about a lot when talking about conversions:  abandonment.  In a lot of conversion funnels, abandonment equates to visits that did not “funnel through” to the following step in the scenario.  Not so with our scenario analysis reports; we focus, instead, on fall-out.

Here’s a sample scenario analysis report (click on it for a clear image):

At first glance you may think that this scenario has a 73.51% abandonment rate on step one, since that’s the first percentage to appear on the right.  On this, you’re right, but it’s not quite what it seems. Here’s what that number tells you:  Of the 38,232 visits to the “Product Page View” step in this scenario, 28,264 (or 73.51% of) visits did not on to the next step, but also did not entirely abandon your site.

From there, we get more detail on what happened with those 28,264 visits:

• · 619 (2.19% of the 28,264) visits did actually abandon the site entirely. The product page view was the end of their visit, hence the “End of Visit” label.
• · However, a full 27,645 (28,264 – 619) did not leave your site. Instead, they went elsewhere on your site. In the case of the first number (27,082, or 95.82% of the 28,264), they went to the Video Recorders page. How do I know this? I hover my mouse over the little blue name, and voila!

So, only 619 people from step one actually abandoned your site altogether; the others got distracted and did something else on your site, so they’re not completely gone yet.

How do I know what they did?  Well, if they went elsewhere on your site, this view of the scenario analysis will tell you, and will provide you with truly actionable information.  Here, for example, I see that the vast majority of people leaving my scenario on the very first step are looking for video recorders, so why not promote those video recorders on your home page?  Or maybe you could set up a bundle:  your most popular products with a video recorder at a reduced cost.  Upsell! 

Now, let’s shift to the Step Transitions view.  I do this by clicking the “View Step Transitions” button above the report (again, click for clarity):

This view provides us with completely different information.  Instead of telling you whether a visit ended or continued someplace other than the scenario, this process shows you two things:

• · The number of visits in which the visitor did not continue directly on to the next step, yet remained within the scenario process as a whole, and
• · Where that visit went when it left that step.

So, let’s look at what the numbers on this first step tell us here:  6,733 visits did not convert to the “Cart Add” step.  However, they still interacted with the scenario:  6,731 (99.97% of the 6,733) viewed another product page (so, they were still shopping), and 2 (.03%) actually started checkout (which probably means they’d already added something to their cart and decided not to buy what was on the last product page they viewed).

So, we can say that, of the 28,264 visits that did not convert from step one to step two, 6,733 did not leave the scenario entirely.  Instead, they either skipped a step or stayed on the same step; they didn’t abandon.  That’s almost a quarter of the visits that didn’t convert to step two – and that’s a great opportunity to ensure that, now that they’re in the scenario, they stay there.  Note, for example, that 317 visits went back to the “Product Page View” after they started checkout.  Is that a result of your efforts to offer them similar items or accessories on your checkout page?  Or, if you’re not making such offerings, could you increase that number by doing so?

Of course, these opportunities may seem fairly obvious; after all, we’ve been tracking shopping carts for a long time on the web.  But imagine tracking your three-step application/registration process, or your five-step “Give me more information” process, and you can see how this information becomes useful quickly.  You might be able to reduce the number of steps and increase conversions, or note where people are getting distracted and provide them, within your scenario, the information they need to stay on track.  That’s so much more helpful than just tracking abandonment, isn’t it?

I’ll discuss the left side of this report in an upcoming post – stay tuned.

With the recent release of Tag Builder 3.0, the User Experience initiative has been made visible.  In the previous article*, I introduced the new Tag Builder with a brief overview.  In this article, I will walkthrough the user centered design approach that grounded the new design, Paper Prototyping.

There is a good chance that if you hang around me for more than an hour or so, you’ll hear me sneak Paper Prototyping into the conversation. If it were a religion, I would be one of its most devout members.  For those of you that aren’t familiar with this usability design methodology, it is defined by Carolyn Snyder in her 2003 book on the subject as ,”Paper prototyping is a variation of usability testing where representative users perform realistic tasks by interacting with a paper version of the interface that is manipulated by a person ‘playing computer,’ who doesn’t explain how the interface is intended to work.”  This might not seem so revolutionary on the surface, just one of many usability exercise/methodology options that a designer has in their toolbox.  However, when you break down the fundamentals of Paper Prototyping into its core tenets, the power of its simplicity becomes more apparent.

Paper Prototyping hardware

1. Define the Problem
As Einstein once said, ““If I had an hour to save the world I would spend 59 minutes defining the problem and one minute finding solutions.”  With Paper Prototyping, you begin by creating scenarios.  These scenarios are tasks from a user perspective that need to be completed.  An example scenario from TagBuilder was, “Ryan does a lot of testing with his site and uses the subdomains testing.acmetoys.com and staging.acmetoys.com. He wants to make sure that these subdomains do not contaminate the data for the main www.acmetoys.com website.”  We started with about 50 of these scenarios and ended up with about 20 grouped by four different user types.  What is great about this exercise is that you can include others outside your development team to help define these tasks.  This includes support, services, and even customers themselves.  Again, this isn’t defining features, this is defining the tasks that a certain type of user is trying to accomplish.

List of tasks (or scenarios)

2. Collaborate
Designing and developing software is not a naturally collaborative process.  Each contributor usually has their own computer designed for one individual.  Sure there are technologies like chat, wikis, and shared source control, but these tools help add collaboration to an individual environment.  With Paper Prototyping, you gather the same team that is tasked to build the application into a room to create the prototype.  This includes the project manager, the developer, the designer, the tester, the writer, etc.  The goal is to go through the tasks and design the solutions on paper.  No computers.  Just paper.  Additional tools are scissors, sticky notes, markers, removable tape, and removable glue sticks.  This is the original cut and paste.  As you design the paper version of the application as a team (all should be working with marker and paper in hand), each team member must bring their constraints with them.  That way, if the designer slaps a button down on a certain screen, and the developer realizes the implication of that button being there implies that they must do a massive restructure of the backend to allow the functionality that that button implies, the developer can speak up and offer an alternative to solve the task another way.  By bringing these constraints forward, the team avoids most situations where one team rejects a design late in the process due to a time and resource issue.  With Tag Builder, we completed the new design in one week with a six member cross departmental team.

The Paper Prototype

3. User Testing
When the design is ready by solving all of the tasks in the scenario list, it is good practice to user testing with each other by taking turns playing the user.  You’ll find by putting on the mindset of the user, you’ll find quirks and issues with the design you just couldn’t see when you were in design mode.  When the team is confident they have a good prototype, it is time to bring in outside users for testing.  You can also take the prototypes with you and take the tests to where the users are.  I once tested a website designed for professional truckers and conducted the testing for that project at a truck stop.  The nice thing about paper prototyping is that users seem to have a good time during the tests.  One reason is that it is paper.  Instead of sitting a user down in front of a computer where it can feel like you are testing their computer skills, you sit them down in front of a paper sketch of an interface.  Immediately this puts the users at ease and they are quite relaxed.  Their finger becomes the mouse and scraps and a pen becomes their keyboard.  Paper Prototyping also works best when you test with two users at a time. You ask them to work as one user and to agree on any action before taking it.  This allows you and the team facilitating the test to hear the dialogue between the users as they try to accomplish the task.  This avoids the problem of interrupting the user and breaking their natural flow to constantly ask them why they did this or that after the fact.  When the first test is done, the team regroups and tries to solve any problems the users ran into during the test before the next test starts.  This allows you to iterate between tests.  I usually try to allow for an hour to an hour and a half.  With Tag Builder, we tested with five groups of two people.  By the last test, the users had no challenges with the interface on any of the tasks.

Screen grab from a Paper Prototyping session

By starting off our process with Paper Prototyping, it allowed the Tag Builder team to start with a shared, collaborative design experience and to iterate the design of the application many times before we sat down in front of our computers.  The process doesn’t catch everything and a few concerns or issues have been brought up with the new design since it launched.  We are aware of these and will adjust the design/flow to correct them in upcoming releases.  However, the new design is a reflection of not only our own design sensibilities but also a direct response to the usability issues that surfaced during our design process with actual users.  We also ran a series of Paper Prototyping sessions at the Engage conference April 7th and 8th on a different and much more ambitious product. We appreciate all who participated and their feedback is influencing our design in a profound way.

If you are interested in learning more about Paper Prototyping,
the book is a great place to start or you could attend the workshop that I am conducting at WebVisions May 20th in Portland, Oregon.

Paper Prototyping Workshop at WebVisions May 20th

In the next article, I will walk through the specific design changes with the new Tag Builder and what they mean for the future of Webtrends user experience.

* Between the first article and this article, my wife and I had a new baby boy and so the frequency of updates to this series was thrown for a loop. The rest of the series should be published much more frequently.

Microsoft Office SharePoint Server 2007 (MOSS) is a great platform for an organization that needs to roll out an intranet with very little effort because MOSS offers an easy way to organize content based on a company’s organization model.

However, what many companies found was while it was easy to implement the website, trying to get accurate analytics on a MOSS portal was difficult, if not impossible.  Log file analytics yielded inaccurate results and advanced JavaScript tracking was nearly impossible for most organizations due to the complexity of the SharePoint code.  If your organization did not have a C# programmer with SharePoint Portal experience, you were out of luck.

After hearing this concern again and again, we decided there had to be a better way and we were going to find it. The current analytics experience was difficult and frustrating – this was unacceptable.  With this goal in mind, my colleague Michael Love and I researched the issue and came up with a simple solution: directly interact with the SharePoint Portal template structure.  The data is already there on the page; let’s use it.  Just as the Webtrends SmartSource Data Collector code pulls data like refers automatically, this altered code allows us to pull details about the portal experience automatically from the SharePoint templates.

So exactly how much development is required?  This is the best part; the effort involved in implementing the code is minimal.  No C# coding required.  No major template modifications are required.  Your developers should be able to apply the code and get you up and running in minutes.  Webtrends will provide you with the code you need to apply to MOSS 2007 to make this work.  Webtrends will do the rest.  We’ll set up the reporting and help you test the data output.

How rich is the data?  Using this methodology we can collect data on Content Areas, overall site traffic based on a Breadcrumb drilldown report, document tracking, Webpart views, onsite search results (including found vs. not found) and all of the standard reports you expect out of Webtrends Analytics.

The document reporting is probably my favorite functionality.  We can build a report that will track document interaction within a document library including check-outs, downloads, emails directly from SharePoint and a number of other options.  The best part is you get you pick the standard document interactions you want to track.  User level reporting is also available.  If you have an external list of departments that users belong to, we can create a report that will allow you to see activity based on departments.

How do I get it? If you are interested in this offering – touch base with your account manager for implementation details and pricing.

This is just the first step.  Webtrends is serious about getting you the data you need and giving you direct access to you.  Many of you saw our press release about integrating with WebSphere Portal.  The integration will be equally easy, giving step by step guidance on how to track your WebSphere Portal with minimal effort.

It’s time to make things easy!

Microsoft Office SharePoint Server 2007 (MOSS) is a great platform for an organization that needs to roll out an intranet with very little effort because MOSS offers an easy way to organize content based on a company’s organization model.

However, what many companies found was while it was easy to implement the website, trying to get accurate analytics on a MOSS portal was difficult, if not impossible.  Log file analytics yielded inaccurate results and advanced JavaScript tracking was nearly impossible for most organizations due to the complexity of the SharePoint code.  If your organization did not have a C# programmer with SharePoint Portal experience, you were out of luck.

After hearing this concern again and again, we decided there had to be a better way and we were going to find it. The current analytics experience was difficult and frustrating – this was unacceptable.  With this goal in mind, my colleague Michael Love and I researched the issue and came up with a simple solution: directly interact with the SharePoint Portal template structure.  The data is already there on the page; let’s use it.  Just as the Webtrends SmartSource Data Collector code pulls data like refers automatically, this altered code allows us to pull details about the portal experience automatically from the SharePoint templates.

So exactly how much development is required?  This is the best part; the effort involved in implementing the code is minimal.  No C# coding required.  No major template modifications are required.  Your developers should be able to apply the code and get you up and running in minutes.  Webtrends will provide you with the code you need to apply to MOSS 2007 to make this work.  Webtrends will do the rest.  We’ll set up the reporting and help you test the data output.

How rich is the data?  Using this methodology we can collect data on Content Areas, overall site traffic based on a Breadcrumb drilldown report, document tracking, Webpart views, onsite search results (including found vs. not found) and all of the standard reports you expect out of Webtrends Analytics.

The document reporting is probably my favorite functionality.  We can build a report that will track document interaction within a document library including check-outs, downloads, emails directly from SharePoint and a number of other options.  The best part is you get you pick the standard document interactions you want to track.  User level reporting is also available.  If you have an external list of departments that users belong to, we can create a report that will allow you to see activity based on departments.

How do I get it? If you are interested in this offering – touch base with your account manager for implementation details and pricing.

This is just the first step.  Webtrends is serious about getting you the data you need and giving you direct access to you.  Many of you saw our press release about integrating with WebSphere Portal.  The integration will be equally easy, giving step by step guidance on how to track your WebSphere Portal with minimal effort.

It’s time to make things easy!

Microsoft Office SharePoint Server 2007 (MOSS) is a great platform for an organization that needs to roll out an intranet with very little effort because MOSS offers an easy way to organize content based on a company’s organization model.

However, what many companies found was while it was easy to implement the website, trying to get accurate analytics on a MOSS portal was difficult, if not impossible.  Log file analytics yielded inaccurate results and advanced JavaScript tracking was nearly impossible for most organizations due to the complexity of the SharePoint code.  If your organization did not have a C# programmer with SharePoint Portal experience, you were out of luck.

After hearing this concern again and again, we decided there had to be a better way and we were going to find it. The current analytics experience was difficult and frustrating – this was unacceptable.  With this goal in mind, my colleague Michael Love and I researched the issue and came up with a simple solution: directly interact with the SharePoint Portal template structure.  The data is already there on the page; let’s use it.  Just as the Webtrends SmartSource Data Collector code pulls data like refers automatically, this altered code allows us to pull details about the portal experience automatically from the SharePoint templates.

So exactly how much development is required?  This is the best part; the effort involved in implementing the code is minimal.  No C# coding required.  No major template modifications are required.  Your developers should be able to apply the code and get you up and running in minutes.  Webtrends will provide you with the code you need to apply to MOSS 2007 to make this work.  Webtrends will do the rest.  We’ll set up the reporting and help you test the data output.

How rich is the data?  Using this methodology we can collect data on Content Areas, overall site traffic based on a Breadcrumb drilldown report, document tracking, Webpart views, onsite search results (including found vs. not found) and all of the standard reports you expect out of Webtrends Analytics.

The document reporting is probably my favorite functionality.  We can build a report that will track document interaction within a document library including check-outs, downloads, emails directly from SharePoint and a number of other options.  The best part is you get you pick the standard document interactions you want to track.  User level reporting is also available.  If you have an external list of departments that users belong to, we can create a report that will allow you to see activity based on departments.

How do I get it? If you are interested in this offering – touch base with your account manager for implementation details and pricing.

This is just the first step.  Webtrends is serious about getting you the data you need and giving you direct access to you.  Many of you saw our press release about integrating with WebSphere Portal.  The integration will be equally easy, giving step by step guidance on how to track your WebSphere Portal with minimal effort.

It’s time to make things easy!

The analytics world is abuzz about the new changes to Google Search coming this week. No need for concern as these changes won’t interfere with any of your Webtrends products.

Just two months ago many of us thought we saw smoke rising from what looked like Google’s new design for their search results display page. The initial concerns rooted in the fact that new page, built in Ajax, completely annihilated referrer information that all of us online analytics providers rely on to identify the source of organic traffic to a web site. The ramifications would have been huge, but it turned out that they were just doing some testing.

Yesterday, Brett Crosby, group product manager with Google Analytics provided us with a very considerate preview of the changes coming in his blog . Thanks Brett!

Key excerpt describing the nature of the changes:

Starting this week, you may start seeing a new referring URL format for visitors coming from Google search result pages.

Up to now, the usual referrer for clicks on search results for the term “flowers”, for example, would be something like this: http://www.google.com/search?hl=en&q=flowers&btnG=Google+Search

Now you will start seeing some referrer strings that look like this: http://www.google.com/url?sa=t&source=web&ct=res&cd=7&url=http%3A%2F%2Fwww.example.com%2Fmypage.htm&
ei=0SjdSa-1N5O8M_qW8dQN&rct=j&q=flowers&usg=AFQjCNHJXSUh7Vw7oubPaO3tZOzz-F-u_w&sig2=X8uCFh6IoPtnwmvGMULQfw

The key difference between these two urls is that instead of “/search?” the URL contains a “/url?”. If you run your own analyses, be sure that you do not depend on the “/search?” portion of the URL to determine if a visit started with an organic search click.

What does this mean if you use Webtrends Analytics?

• All the insight we provide about the Google engine, phrases and search type remain completely unaffected by this change.

• We provide a number of different views of the referrer, including domain – google.com, site – www.google.com, and page- www.google.com/finance. The only difference will be the introduction of a new Google page in your referring pages data. So now you may see both www.google.com/url and www.google.com/search.

• Other WebTrends products (Ad Director and Marketing Warehouse) are not affected by this change.

Is there gold in the stream of query parameters?

We are panning through this new information to see what additional insight Google is sending you. Check out what others are saying about this. But you don’t need to wait for us to publish new reports before being able to take advantage of this data. If it is in a parameter, you can build a report on it today.

Let us know what you would like to see or what you have customized yourself. We’re always working hard to improve your experience with Webtrends and keep you abreast of industry trends. Let us know how we’re doing – provide feedback from within the products, comment here on the blog, user forums, Twitter or contact any of us directly.

A few months ago my wife and I were in the market for a new jogging stroller and I couldn’t help noticing how product research has changed in the 8 years since having my first son. The first time around we walked into Babies R Us, pushed around a few strollers on the smooth tile floor, strapped the baby in until it started to piss him off, tested how easy they were to collapse, and then bought one. Then the first time down the block the design flaws began to reveal themselves. The second time around our research started with Yahoo groups and led us to a brand not even carried by large department stores, to our great satisfaction.

As savvy internet users this is not enlightening. We use the web to research products, get ideas on restaurants, decide which movies to see, and so on. But I can only wonder to what degree the stroller manufacturers who lost my business are clued into the online chatter about their products. As owners of products and services, we’ve entered an era where your brand identities are decreasingly under your direct control. Consumers are talking about your products through email and text, and on Blogs and Facebook and Twitter. People trust their friends, peers and virtual communities over TV commercials and sales people, especially those who are growing up in the social media era … and who represent an ever increasing proportion of the global economy.

So what are brand owners to do? It’s simple and trite. Provide the best experience you can for your customers and prospects, both online and offline. Instill a culture of customer service and support. Make customer satisfaction a fanatical pursuit of every employee. Make quality products. Do these things and social media works in your favor.

So what is Webtrends Open Exchange? As we revealed last week at our Engage conference, it’s much more than open access to data. Open Exchange is a philosophy. It’s the recognition that our success is entirely reliant on our customers’ success. It’s the pride of knowing we have great products and people. It’s the humility of knowing we aren’t perfect and the honesty of owning up to our mistakes. It’s the realization that web analytics and digital marketing is NOT easy, and that despite our 15 years of experience we are still learning too. But through collaboration, we will help you succeed. What is Open Exchange? It’s a spirit of communication that forms the cornerstone of our mutual success and the way we at Webtrends do business. To our customers, our partners and those concerned with the evolution of digital marketing, we welcome your ideas, your challenges, your criticisms and your innovations. For our part, we will grant you unfettered access to YOUR data, our people and our experiences.

Welcome to the new Webtrends.

Well, our conference is officially over. It has been a wonderful experience for everyone at Webtrends and we were honored by the strong response we received from our attendees and those following the news. Over the next several days we will be pulling together video highlight reels and digitizing the keynotes to share via our blog. In the mean time, we’ve gathered some additional links to pictures, videos, and stories from day two and three from the conference.

Enjoy!

Links

• Our YouTube account with short vids from our Flip cam crew
• Pictures from the final day by Web Analytics World
• Killer video of Obama’s campaign by the numbers
• A couple of videos from the final day by Web Analytics World
• A thanks from Douglas Karr
• Anil Batra’s video interview with our CEO, Alex Yoder
• Write up on CMS Wire – Webtrends Offers Social Media Monitoring, Unlocks Customer Data

Tweets

Throughout the course of the conference attendees and followers generated over 900 total tweets. We pulled together a selection of those tweets that really told the story of the conference. Here’s a sampling of the discussion:

jacqueswarren: RT @cgrantski: All in all, the best WebTrends conference yet. If this is a repr. sample of their current staff & customers, look out world!

nbreau: RT @douglaskarr: #wte09 an interview with Chris Ramsey and Chris Newton from Radian6. http://is.gd/rDaI (expand) Webtrends partnership is exciting..

AdamBroitman: reading about Radian6+Webtrends–The Inner Social QuantGeek is happy–me likey!

krispatel: Webtrends Social Measurement is all a-buzz. Great for branding campaigns. VERY valuable to kno whos saying what where http://snurl.com/chk6y

bigbryc: @paynt great meeting you too. #wte09 was great and I look forward to the next one.

smith0902: Writing up my key takeaways from WebTrends Engage 09 to disseminate to the team. Great to see a company re-energize – they get it!

jinnyp: bids farewell to all the awesome #wte09 and awesome attendees. I’m sticking around for the WebTrends for Marketing Pros training until Fri.

erictpeterson: @cdnewt Indeed I had a wonderful time and got to know some great folks! Thanks #wte09!

douglaskarr: @Thommer wonderful pic by Webtrends. I don’t get pampered like this very often #wte09. Let’s see what emetrics comes up with, ha!

douglaskarr: http://twitpic.com/30zcy – Blurry photo of Alex closing the #wte09 Webtrends Engage 2009 Conference. Great job Webtrends! Well done!

1salman: RT @jacqueswarren: Best @WebTrends conference ever. Plainly, they’re back! #engage09 #wa

jonparks: thanks to @webtrends for the engage 09 conf & to @yodera for the new WT approach. Really like WT once again & ready to get going #wte09

Terrible30: #wte09 Best WebTrends conf 2 date! Is reenergized and passionate once again. Promise greater visability and insight into what they are doing

ebeane: #WTE09 open access to data is a game changer imo

jonparks: I feel like I finally understand the advantages of webtrends over google analytics. Thanks to mike love w/wt for the help #wte09

kylebamford: #wte09 The numbers video that plays before the main sessions should really be released as a screensaver…

Terrible30: #wte09 Almost to the end of day two of WebTrends Engage. Definitely worth the time to attend. I’m ready for more!

BillBruno: #wte09 #wa Open Exchange, Free APIs, and what I heard from Teradata’s presentation: I’m very excited about WebTrends and our WT clients

johnlovett: Just had an awesome conversation with Alex Yoder at #wte09 about Open and the future of Web analytics.

seanking: Getting pretty geeked about the new REST api an data exporting capabilities in public beta from WebTrends. #wte09

jebby27: Radian6 and Webtrends partnership is a huge step in merging traditional measurment with SM it was a matter of time and is the way to go.

Jenicaivy: RT @leeodden @jcousineau: SMM & web analytics get married: Webtrends + Radian6 http://tinyurl.com/cmvn7a (expand) via (@mediapost) – WOOOOO!

waworld: Another exciting day at #wte09 is just about to begin. PS No more tweets using JOTT, the transcribing left a lot to be desired.

alexbrasil: #wa Good for Webtrends and R6– about time something like this happened formally. The connection between the two is bloody obvious.

jacqueswarren: Great first day today at @webtrends #engage09 Good presentations, and a cool evening with @yodera @kaykas whose hospitality is impeccable.

mikegero: @AmberCadabra Congrats on the Webtrends announce – a very powerful collaboration IMHO

seanking: Enjoying the WebTrends conference! Seems WT did some real work to clarify and build on their core value to customers. #wte09

slicecast: RT @pyesawichjr:WebTrends announces collaboration w Radian6. http://bit.ly/yTrC (expand). Web analytics w social media. Where’s Omniture?

seanbrowning: #wte09 – Radian6 makes sense behind the numbers – cust service, 1:1 marketing and support – super cool!

OnlineStrategy: RT @kdpaine: webtrends + @radian6 bring us 1 step closer to the holy grail of measurement.

OnlineStrategy: I want me some! RT @kdpaine: the link to the Radian 6 + Webtrends product announcement is here: http://bit.ly/11tkU

douglaskarr: Webtrends announcing free access to all analytics data today via API and Dev network. ‘It is your data, you should not pay for it’. Woohoo!

Terrible30: #wte09 #wa great news: open API access. One of the best things I’ve heard. Open Exchange. Free access to your data!!!

pageoneresults: The new http://www.Webtrends.com/ is live today. Check out the new branding. RT @paynt / WOW! Killer intro. I got goose bumps. A 10! +1

gostats: @WebTrends I like your new site design!

mccook: Very cool: Webtrends Social Measurement Powered by Radian6 http://ping.fm/zwziT

siegertd: RT @davidalston: Analytics for the web & the social web step closer http://bit.ly/WTR6 (expand) #WebTrends #radian6 #wa

adamcohen: This is a very smart evolution toward insight from combo analytics & social – http://bit.ly/WTR6 (expand) #WebTrends #radian6 #wa (via @AmberCadabra)

kenburbary: If you’re a Webtrends customer, then your analytics for the web & the social web just got better http://bit.ly/WTR6 (expand) #WebTrends #radian6

nickp_uk: No more orange for WebTrends. They’ve rebranded and are now all blue. Nice! #wa http://www.webtrends.com

Webtrends worked with the Obama campaign team to pull together a look back at the historic campaign by the numbers. We hope it gives you the kind of goosebumps it did for us

[youtube=http://www.youtube.com/watch?v=BKwSEi_zHII]

Webtrends worked with the Obama campaign team to pull together a look back at the historic campaign by the numbers. We hope it gives you the kind of goosebumps it did for us

[youtube=http://www.youtube.com/watch?v=BKwSEi_zHII]