Gordon K
Has some bugs, sometimes stops working tracking events and requires a restart of Chrome. It does not record GA events with the transport:'beacon' option.
it is easier to read than GA debugger but ultimately less useful.
|
A Google User
It is part of my everyday analytics analysis. Works great.
|
Bradley Perry
I use this in addition to Chrome developer tools. It makes it much simpler to see what tags are on my pages and what information they are passing over.
|
Holly Halifax
I can't open it up
|
Bridgette G
Really helpful app. Only thing that drives me nuts is while the requests keep coming through, the list moves. So if you're hovered over a request, trying to read its parameters, within a few seconds, it's moving down the page. The list should remain still unless the user scrolls it. Makes it really difficult to read one individual request.
|
Paromita Bose
great app. helpful!
|
Ryosuke Sawada
シンプルで使いやすいと思います。
|
A Google User
Updating my rating based on usage over the past few months(now 6/25/13). ObservePoint is my go-to plugin for simple troubleshooting in Chrome.
1. Still no cookies. Validating visitors across domains still isn't possible. Would love to see another tab akin to Variables/Request and adding in Cookies.
2. Return code is there, I was just looking in the wrong spot! It is worth noting that the return code gets covered once you select a tag request.
3. Variables/Parameters are still categorized in an odd manner. Would like to see this cleaned up(specifically looking at Webtrends tagging).
____________________
Nifty tool aimed at Analytics tag troubleshooting. A couple of things I noticed that would be nice to have as well:
1. I don't see any cookies. Because cookies are often the primary way to identify a visitor, not seeing the cookies set or passed is a problem. Especially when dealing with cross domain tracking I want to make sure my cookies are consistent across domains and I can't validate that with this tool.
2. No way to see if the request was successful, IE no return code shown. Without a 200, or something denoting a success message I am not sure that even if the request was built that it was sent(mainly for event tracking where the visitor has navigated away from the page.
3. Page information and Variables are split, and some not categorized properly. It may be nice to split parameters into groups like page and variables, but there are parameters in Webtrends like dcssip, dcsuri which should fall under page information. And some parameters like Browsing hour, Resolution, JavaScript enabled etc. that is visitor information and not page information. Would also be nice to see custom variables have their own section as well.
Cool features:
1. Decoded version of the request is super nice because now I can see the special characters instead of trying to manually build the request back myself.
2. Icons for Analytics requests makes it easy to see if a page has multiple tags.
Hopefully this doesn't fall on deaf ears as this does have some cool features I wish were in other tools.
|
Jake West
I'm on 32-bit Windows, and like the note says I installed Canary and the tool works great.
|
Stuart Roskelley
Similar issue to the last comment. It was fantastic, but stopped working with the last chrome update. To make matters worse, it is constantly running a high process 8-10% cpu at all times.
|
ObservePoint TagDebugger
