Exclude visits for unwanted URIs
Using sensor configuration we can Exclude URIs in Web server properties so that we will not get unwanted purepath, similarly is it possible to exclude visits or page actions for unwanted URIs.
I have excluded some URIs from web server configuration so I am not getting purepath for that URIs but still I am getting the visits for that and it is single page visit which consume my visit license
Can we exclude visits.
Best Regards,
Jaydatt
Hi. You can only exclude Visits by IP or Browser. That can be configured in the User Experience Settings in your System Profile. What this setting really does is that it doesnt inject our JavaScript agent to Visitors that come in from these IPs or use these defined Browsers. If your HTML pages get cached somehwere and our JavaScript agent is on that page you woudl also get these visitors.
But - to your original question: right now its not possible to exclude a whole visit if they go to a certain page.
One last thing you can try out is to configure the User Experience Sensor Pack to not inject that JavaScript agent on these particular URLs. That means that visitors that only go to that page wiill not start a Visit. If they continue on other pages you will see them.
Andi
Jaydatt,
Unfortunately I don't think there is a filter as convenient as it is for the Web Server, .NET or Java agents. There is an option, however, to insert the javascript manually. This would give you the control you want, but requires some code changes on your side. Depending on what you're instrumenting that may or may not be an option.
This information is for 5.6, and may have changed in 6.0. Hopefully someone comes through with an solution for you if this isn't satisfactory.
System Profile - User Experience
James is spot on - good news is that 6.0 has a new feature to offer to exclude injection for certain URLs -> just what I said in my last paragraph. Here is the screenshot
Nice.
We had some interesting behavior with the JS agent concerning specific versions of Java, WebSphere, and a third party application back in 4.1. Ever since the we went the manual route to be on the safe side. I'm glad to see this.
thanks guys!!!!
