Provide admin variable for toggling the status code filter override added here :http://drupal.org/node/270819
I have a patch for this if maintainer thinks it is reasonable. We found the automatic tracking of the 404 and 403 pages to be an issue on our sites.

Comments

hass’s picture

hass CreditAttribution: hass commented
Status: Active » Closed (works as designed)

What is the use case? Removing tracking would result in wrong statistics, wrong visitor counters, and so on and so on.

ben.hamelin’s picture

ben.hamelin CreditAttribution: ben.hamelin commented

I guess the use cases are to clean up analytics. There are plenty of ways to filter/configure the GA accounts to segment these hits out, but we've simply found it easiest to remove them altogether. We use other server stats and reporting tools to clean up / monitor 400 responses - I just thought other people might want similar control.

hass’s picture

hass CreditAttribution: hass commented

A 404 and 403 page is a valid page in your website. These need to be logged in the statistics.

If you'd like to remove them you need to fix your broken backlinks, broken urls, etc to clean it up. There is a module named redirect that is made to catch outdated links and redirect them to a new page. This is what you need to do with broken links logged in GA and redirect module and this is what it was made for. There are no plans to remove this logging as it is only useful and it describes 100% correctly that the website is broken in several ways and site admins need to be notified about this broken links as they break the internet.

yallara’s picture

yallara CreditAttribution: yallara commented
Issue summary: View changes

You asked for a use case.

We're using Google Tag Manager for most of the website. There is a small portion we can't (long story), so we're using the Google Analytics module, restricting it to the very small number of pages where GTM is absent.

After noticing weird entries in GA for "/404.html", I eventually discovered this module is causing our 404 and 403 errors to be double counted. And there's no accessible option to prevent this.