I believe when attempting to access the page in content overlay within Analytics what is crashing the Browser experience is not the added link parameters themselves but it is the interaction with the deeply nested stack of programming being pushed when this landing page is rendered.

As the Server Response is pushed the .Net driven random load smart targeting banner add I have added the “unique tokenization” to the link to track must cause the script to blowup and crash the browser as it is read into the Client Request on the front end. maybe its a IE 8 issue – who knows lol

I will try to find a simpler page without the smart targeting rotator widget which I can test with through the CMS engine that drives the website and see if when the browser tries to read in and interpret the link parameters it will not truncate and blow up.

nevertheless I intend to use your tricked out click thru concept on my own pages as well…
thanks for the tips

There are a lot of very complex ways one can track in GA and the scenario you described would not be considered that “elaborate”. Having said that, since in the end you are tracking a url in essence the worst that could happen (in your scenario) is that it is not tracked at all … again, I would not think it would crash your browser.

Have you tried to view that same section of GA using another browser?
What version of the current browser are you using?
Have you tried viewing that same section from a different computer?

If you can view it ok using any of the methods above then the problem is related to your computer itself and how it interacts with GA (maybe updates etc… would help.)

If however, none of the above options provide any success in viewing, then it might be attributed to the way the data is being recorded in GA (but I would doubt that.)

Check these things out and let me know what you find out. We’ll see if we can get you through it here.

http://widener.edu/admissions/undergraduate/visit/openhouses.asp?cPath=19&location=3&key=WidenerDay

and everytime I attempt to open up Content Overlay, it crashes and I must close out of the pop-up which then of course does not allow me to report on my designed metric.

Could it be that it is because of the condition it is a nested random load, with a nested analytic reporting snippet?

any thoughts are helpful

thx

Google Analytics Manual…

Google Analytics Manual…

1. as stated above, let’s assume 2 links on a home page which point to a “Products Overview” page. The URLs lets say are something like:
1a – http://www.domain.com/products-overview.html
1b – http://www.domain.com/products-overview.html?Path=20whatever
2. assume nofollow or noindex & robots.txt are dealt with accordingly for the “?Path” page/link

QUESTION
Won’t log file reporting now report visits to two different Product Overview pages rather than one?

There must be a better way. Or maybe this is a good solution. I definitely wouldn’t want search engines thinking I have 4 of the same page because of the extra url variables. I’m wary because I have read how important keyword based internal linking is in SEO.

It’s tough with Google’s site overlay because they track the URL (not the click). But I did give a comment in reply to that first comment on this page that provides an answer to that “SEO” question. Scroll up and take a look at that for more assistance.

How do you suppose those “heat map” tools work? I imagine they use something similar to your idea. Site Overlay is really the same idea as a Heat Map. Or does the Heat Map tools actually track your mouse cursor movements?

HeatMap software (that isn’t the actual kind which “connects to a users eye” operates by recording mouse clicks on a page. I am working on a heat map application as part of a full package of coaching services I provide. I hope to have that released in the near future.

One some pages, I have 4 different ways of getting to the same page. (e.g. header, main content, right column, footer) I’d love to be able to know what content gets read/clicked which would help me optimize the layout for visitors.

For this you might be better off with an actual “Heat Tracking” system in place that tracks the “click”.