The Buzzz

We are very excited to announce the recent release of WASP 2.1.

Whats’s new?

• Detail view of your tags
  - Never miss an in-between call again, as we keep track of the last 5 pages you browsed
  - Filter solution list by type, so you only see what you need
• Capture title, description and meta data of the sites you’ve scanned to allow enhanced SEO and a powerful tag cloud for easy analysis and drill down on the specific pages that use those tags
• Localization in French
• Execution time and latency information for all the tags
• Seomoz.com related SEO data in the WASP popup
• Additional tags detected
• Minor improvements, including bug fixes as always
• Market research functionality to analyze your competitors’ sites (Did we mention new tag cloud! )
• Automate market research scans

Thanks for all the great feedback from the community,
and the help from my beta testers (yes you guys )

We sincerely hope you enjoy the new release!

BTW, you can try it free here: http://webanalyticssolutionprofiler.com/try.htm

We are almost ready to launch WASP 2.1, but we need to do another round of beta testing.

We are looking for users to jump in and help.

We will give you a 30-day license of WASP 2.1 Analyst.

Email us at support [at] webanalyticssolutionprofiler.com for more details.

This one will be a lot of fun!

I guess it’s no big secret that even before WASP 2.0 was released we had started working on 2.1. This release will be based on a mix of feedback from the community and some ideas that we came up with earlier this year.

So, here it is! WASP 2.1 Beta1 has been released to a small number of beta testers.

The goal of this release is to enhance the way we display tag details. You can now see historical data when the tag is fired, along with its latency and detailed information. We also added some features in the data reports: you can now see the title, description and metadata information for all the pages scanned.

We would like to thank our amazing community for the time, the feedback and the positive energy you are sending us about WASP! It is quite refreshing and plays a big role in making this product even better.

More and more companies are building communities using social networking sites and there has been a lot of buzz lately about tracking Facebook Fan pages with Google Analytics. Integrating GA into Facebook can be a challenge since what you can actually do is limited and trying to see if your implementation of GA works on your Facebook Page can be an even bigger challenge.

That’s why WASP was created, and as you have probably guessed by now, you can use WASP to see if those “invisible” tags you placed on your Facebook page are triggered properly and are sending back the proper data.

Yesterday, I created a Facebook Fan page for WASP, and then followed the instructions here to insert the data I want to feed to my Google Analytics account. I passed in 3 values:  googledomain=facebook.com, pagelink=/FB/Landing and pagetitle=FBLanding.

And, now if I visit my Fan page with WASP enabled, this is what I see:

When I open up the side bar, I can also make sure I am sending the proper data back to my Google Analytics account:

And, even if I created my Fan page yesterday, people are already finding me and here are the result in my Google Analytics report:

Voila! I’ve just confirmed that it’s all working properly. This technique will not only work for Google Analytics but with over 200 analytics solutions detected by WASP, even if they are triggered on event as mention in my event post.

I was just asked today if WASP 2.0 tracks Google Analytics events. Yes, it does!

So, take for example the following html code:

<a href=”#”color: red;”>pageTracker._trackEvent(‘Video’, ‘Play’, ‘Escape from New York’); alert( ‘Successfully called pageTracker._trackEvent()’ );”>Video, Play, Escape from New York</a>

In this example, a link to play a video, we want to pass specific information to GA to track a specific video being played.

Once you click on this link, if you look in the WASP sidebar you will see the Google Analytics call being made and all the data being transmitted. If you look carefully, the tag UTME will have the value you are looking for:

So, even if the event is not triggered on page load, WASP will still catch it at the moment it is fired. This also applies to other events such as flash animation and more.