I have a site that gets most of it's traffic (like 90%) from users who are only looking for a login-button that will take them to a different site. This button is a customer requirement I'm not allowed to remove it.
This setup is currently an nightmare when it it comes to the statistics since we want them for all users who actually browses the site.
If I have understood everything correctly, this is the solution proposed by Google (although _setVar has now been deprecated one should use setCustomVar instead):
To exclude traffic from dynamic IP addresses, you can use a JavaScript function to set a cookie on your internal computers. You'll then be able to filter all visitors with this cookies from appearing on your Analytics reports.
But then we would exclude that user "forever" and that is not an option, the next time the user returns her or she might be browsing the site for information and should then be considered a regular user.
Instead of stating that the user always should be filtered out, I'm lacking some kind of session concept where I could invalidate the whole visit on a session level. E.g. if the user presses the login-button within say 5 seconds, he should be discarded from the statistics.
Is something like this possible to achieve or is there another way around the problem?