Tracking Internal Redirects in Analytics and Tracing External Redirects

This post is split into two sections.  The first is for tracking your own internal redirects using Google Analytics.  The second portion is for tracing URL redirect paths.

Tracking Redirects with Google Analytics

One of the problems people run into is their inability to track redirects in Google Analytics. For example, let’s say you purchase radio or print ads in order to advertise a product. Rather than simply advertising your domain name (ie (www.yourdomain.com), you may add an easy to remember folder name (ie. www.yourdomain.com/adpage), which redirects to the appropriate product page (which is probably too long and complicated to display on a radio, TV, or print ad).

Depending on the type of redirect you use, Analytics may not be able to track visits and user behavior. Fortunately, there are at least 2 ways you can track redirects. In both instances, you have to make sure the directory actually exists as a file (ie. /adpage/index.php). The difference lies in the type of redirect you use. If you use a 301 redirect, you’ll want to add campaign tracking to the url you are redirecting to, so Analytics can track visits as a campaign. The other option is to use a standard javascript redirect, and add the Analytics tracking to the redirecting page (ie. /adpage/index.php). This way, you can track visits and user behavior in the Analytics Content section.

Read more