Is there any way to Track 301 Redirected Sub-Example

**himeshRES** · 20-01-2011

I have a sub example which is redirected (301) to abc.com. I have to track the sub example. I did the entire essential step to track the sub example but because of, 301 redirection I am unable to track the record. Compassionately let me know the steps to track 301 redirected sub examples. Or if anyone has any other idea or any other information regarding this type of problem then please join me, or if have any solution for this then please provide.

**fellah** · 20-01-2011

While users come straight to example.com or www.example.com, I am redirecting them to shop.example.com through this .htaccess rewrite:

Code:

RewriteEngine on
RewriteCond %{ HTTP_HOST} ^www.example.com$ 
RewriteCond %{ HTTP_HOST} ^example.com$ 
RewriteRule ^ (.*) $ http://shop.example.com/ [R=301, L]

The information served by shop.example.com has the below tracking code parameters:

Code:

Var _gaq = _gaq || [];
_gaq.push (['_setAccount', 'UA-123456-7']);
_gaq.push (['_setDomainName', '.example.com']);
_gaq.push (['_trackPageview']);

Every direct visit which comes to shop.example.com as an outcome of the rewrite from example.com are tracked as transfer traffic, showing my personal example.com as transfer source in Google Analytics. I would like to track these visits as straight traffic. How to alter the configuration to track mod_rewritten traffic on my sub example arriving from my personal domain as straight traffic?

**Caiden** · 20-01-2011

You can make ineffective the referrer that Google Analytics is utilizing, read further in the documentation for _setReferrerOverride. To someway give this accurate referrer, you require passing it through the 301 redirect. I can recommend adding a query parameter to your forwarded URL, and writing a JavaScript clip which will take out this information from the document.location. An instance of adding JavaScript to your Google Analytics code:

Code:

var _gaq = _gaq || [];
_gaq.push (['_setAccount', 'UA-XXXXXXX-1']);
var _from = unescape(window.location.href.replace(/.*[?&]from=(.*)/,'$1'));
if (_from && _from.length > 0) {
  _gaq.push (['_setReferrerOverride',_from]);
}
_gaq.push(['_trackPageview']);

And, an instance of utilizing mod_rewrite to move the referrer, if a referrer exists:

Code:

RewriteCond %{ HTTP_HOST} ^example.com\.com$ [NC]
RewriteCond %{ HTTP_REFERER}! ^$
RewriteCond %{ HTTP_REFERER} (.*)
RewriteRule ^ (.*) $ http://shop.example.com/$1?from=%1 [R=301, QSA, L]

RewriteCond %{ HTTP_HOST} ^example\.com$ [NC]
RewriteRule ^ (.*) $ http://shop.example.com/$1 [R=301, L]

You will require replicating the over for www.example.com too.

**Eleeazar** · 20-01-2011

I have a trouble that is bugging the heck out of me. My business has associates which sell our online creation. They provide affiliates this URL to put a link to our site www.example.com/?lgr=12334334 so while a user buy via that link, they get the credit. This URL redirects to a sub example of our site: affiliates.example.com. Our developers were quite convinced that Google would treat the sub example as a split site. The information on our sub example site is way additional immature and optimized than the main site: example.com. It is a totally dissimilar design and has 2/5 of the content.

**Daniel23** · 27-01-2011

I will have to converse to the developers regarding the weblogs. I would say a few things are not preferably setup in the backend that is why we are running into this trouble. For instance, I at present can't track affiliates in analytics (split out the conversions from our individual).They have been utilizing affiliates this way for a short time. It is just now that as I am checking our rankings, they perceive the possible damage in the way affiliates are handled. We do utilize .asp; however I can observe the warning possibly a potential trouble for them.