If you’re using redirects in your site, you have two options:
- Ignore (don’t capture) the redirect
- Capture the redirect as a ‘valid’ page impression
When might you want to choose one or other of these options? Well, you would choose no. 1 when you’re using redirects internally, for example (as in Avinash’s example) if you’re using an ad platform to serve internal ads – the ad platform usually demands you redirect the click so that you get measurement within the ad platform (this is what we’re doing on microsoft.com). In your main web analytics data stream, you don’t want loads of extra ‘pages’ popping up that are odd URL formats and are going to throw your numbers out. So in this case, use a server-side redirect (e.g. 301) which will automatically re-point the browser without an actual page-load happening on the client.
A refinement of method 2 is to use a web analytics tool which you can redirect the outbound click through – that is, then vendor provides a mechanism where you can direct users to a URL on their domain which then redirects to the URL that you really want (which may or may not be one of yours). This is how the ad-serving companies capture click information. I think Omniture does this, and I know some others (e.g. NedStat’s SiteStat product) do too. In this instance the web analytics tool handles (and logs) the redirect; savvy tools can then report this information separately without it polluting the main page impression counts.
The only other thing to add is that the tool that Avinash references that Omniture uses to track tag coverage and deployment is (I believe) Maxamine. The folks at Maxamine are great; if you’re running tag-based data collection over a large ad complex site, you should give them a call.