Webinar on the 02/12/10 about how to use WASP to debug your analytic tags.
register here: http://webanalyticssolutionprofiler.com/newsletter/semi/
With complex analytic funnels, multiple goal tracking and multiple technologies, keeping your analytics reporting properly can be a long and tedious process. Wading through html source code can take hours and you can never be sure you didn’t miss something.
We are pleased to announce today our new support platform for WASP. This platform allows us to consolidate your emails and forum requests into one repository, which makes it easier for us to help you.
Better search capability lets us find solutions to your problems quicker than ever before. And a more structured layout that includes email tracking and a new in-page widget, lets us streamline our communications with everyone.
Enjoy!
Migrating SiteCatalyst to version 14.9 ?
Any time there is a major update in your analytic tagging, such as necessary new variables or javascript changes that require references to new Javascript code, it can take ages to ensure that all of your tags are updated properly. Verifying large sites by hand is nearly impossible.
To ease this process, you can use the scanning capability of WASP Pro. This simple tool will automatically crawl your entire website and provide a detailed report of which pages have not been updated or are missing tags altogether.
Let me show you how WASP Pro does this. First, you define what you want to scan, including how many pages you want to scan, maximum depth, and even rules as regular expression to filter pages in or out of your scan.
Once the scan is complete, you can view a report that shows you all of the analytic solutions detected and the number of pages that have the solution integrated.
If you click on the tagged pages, you will see a list of all the pages with those tags, in a table format. If you click on the missing pages, you will see all the pages missing those tags. In the example below, we clicked on the missing pages for Omniture SiteCatalyst.
We also have what we call the “upside down” view. Instead of looking at the data at the page level in a table, we give it to you at the tag level using a tree. You can drill down into every single variable and value in order to see what page have those values. If we take our Omniutre SiteCatalyst example, you can see specifically what pages are tagged with what version.
And of course you can always export any of the data in .csv format to analyze in other tools such as Excel.
Naturally, once you have your report you can use the interactive functionality of WASP to diagnose the pages that are causing you problems and make sure all your pages are properly tagged.
Feel free to contact us for an interactive demo.
We are very excited to announce the recent release of WASP 2.2.
What’s new?
Keep the comments coming, there are always improvements underway!
Try the new version for free at: http://webanalyticssolutionprofiler.com/try.htm
We are very excited to announce the recent release of WASP 2.1.
Whats’s new?
)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 just posted a new video that explain how to install and use the basic feature of WASP, enjoy.
WASP Install and basic operation
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!
Great news! WASP 2.0 has been approved for general availability by Mozilla.
We are also working on 2.1 beta which will include some pretty sexy features. Stay tuned for the beta release announcement!
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.
