Got it, very helpful - thanks so much!

_Cindy

OK, thank you.

If I understand correctly, the tracking code for a single site did the work of tracking visitors, and the 301 redirect didn't change the tracking results -- even though the "301 redirected address" was at one time different from the "GA default url."

If I may ask, what is a hostname injection? And if possible please explain a use case example where hostname injection is used.

_Cindy

Everything is consistent now - 301 redirect to www, default url in GA set to www.

Tracking code has remained the same within cms because the GA account's url was changed to go to www.

It is a matter of too many chefs in kitchen and no one had control of entire picture at one point.

My question really is... when there was inconsistency in web address from 301 redirect (www-address) and the GA default url (non-www), why was GA still receiving traffic?

And how much can one rely on older metrics when this inconsistency was in place?

_Cindy

If someone has set:

1. the default url in Google Analytics to a non-www address (http://mysite.com)

2. then placed the UA tracking script from that GA account within the CMS framework of the website...

3. ... and then set the permanent 301 redirect in the htaccess file to redirect to the www address (http://www.mysite.com).

How less accurrate will my GA analytics measurements be considering the default url within GA is non-www and the permanent 301 redirect in htacess is to the www-address?

Anyone know how reliable GA reports are until the default url in GA analytics is changed to match what is the redirected url in htaccess file?

_Cindy

Thank you Jennifer.

_Cindy

I bought the MozCon Video Bundle - how long will I be able to access it online?

And how do I access it online - keep clicking the promo icon?