Edit Filter - not as expected
I have a simply dashboard of Visits (no grouping) - I select edit filter, Business Transactions, Select "Visits by Client Family" and add one of the available splittings. When I apply all my visits disappear.
Have I misunderstood what the filter does? I am expecting it to show the selected splittings.
What I want to do is not have "Gomez Agent" being reported in a Dashboard and all subsequent dashlets to inherit that filter.
Hi Matthew,
What you are doing should work. Just to be sure, I tried it on my system and it does work. I can apply the filter to either the Dashboard or the dashlet. I select the 'visits by client family' BT and then add all but the 'gomez agent' to the splittings (really, any splitting works). I then get a list of all non-gomez agent visits in my visits dashlet. Are you sure you were looking at a long enough time frame?
There may be a better way to do this (although it still does require a BT filter). If you use the "Real User Visits" BT as the filter, you won't have to deal with the splittings. You should have two BTs - "Real User Visits" and "Synthetic User Visits" which are there, in part, to help with this kind of filtering.
And, there is yet another way to accomplish this, however it wouldn't be a Dashboard level filter (thus would not apply to other dashlets on the dashboard. Have you checked out the "Custom Query" capability on the Visits dashlet? It's the funnel button in the little button bar (where you toggle between group by user experience, group by application, no grouping, etc.). It allows you to do all sorts of cool stuff around splitting (with multi-level splittings) and filtering. If you haven't tried, it I recommend you do. In any event, you could enter ClientFamily != "Gomez Agent" in the Filter field and it would filter out all the Gomez Agent data.
Hope this helps!
===ted
Hi Ted,
It was indeed the time frame. Several of the BT's (Real user visits/synthetic visits etc) are exactly 30mins "slow" i.e reporting 1hr shows results exactly older than 30mins. Is this correct?
Matt
You're visit timeout is probably 30 minutes? The visit has to complete before we aggregate it, so that's probably the culprit here.
