I have a report I'm working on for a client with a relatively small amount of traffic. But what I've been seeing pretty consistently is their number one referrer is "typed/bookmarked" and I can pretty well guarantee this website is NOT getting that much direct traffic. When you break it down by IP - ALOT of it is clearly bot traffic. I filtered out the easy ones that were all originating from the same IP block (and filtered the IP in my account). But I'm still looking at what appears to be alot of junk traffic.
One thing I noticed is alot of the traffic still falls under "unspecified" for operating system which is typically signs of a bot. So my question is, would it be a bad practice to segment out the traffic to EXCLUDE any unspecified operating system? Or is there a use case where legitimate traffic could show "unspecified" for operating system?
Thanks in advance
Matt
Solved! Go to Solution.
Views
Replies
Total Likes
It's okay to ignore/exclude the unspecified value. Unspecified will appear for these scenarios:
“Unspecified” is a fairly common line item in reports. It is also frequently referred to as “None”.
https://experienceleague.adobe.com/docs/analytics/technotes/unspecified.html?lang=en
Views
Replies
Total Likes
It's okay to ignore/exclude the unspecified value. Unspecified will appear for these scenarios:
“Unspecified” is a fairly common line item in reports. It is also frequently referred to as “None”.
https://experienceleague.adobe.com/docs/analytics/technotes/unspecified.html?lang=en
Views
Replies
Total Likes
The other answer is only talking about "Unspecified" in general terms... let me add specific thoughts on your question.
I would say "no" it's not bad practice at all... I actually think it's a great idea.... but here are some additional thought that you might want to consider
I created a "Clean Data" Segment, and created a Virtual Segment based on "Clean Data"... Clean is where I can exclude data that I believe was inflated by potential bots, or tracking issues where we had double tracking after a bad code push, etc...
Using something like this, you can exclude the Unspecified OSs... but if you find that maybe something shouldn't have been removed, you can always adjust the segment and the data will flow back in (both current and historical). But being the main "report suite" that people use, no one has to remember to add a bunch of exclusions... and if you document what is blocked, then there is transparency. It will take a while to transition people to use the Virtual Suite, but then everyone uses that one source of truth.
I too do use IP Bot Filters, but as that is all "reaction".. it only applies as of the IPs added to the bot rules (but also, , I plan on using Clean (at some day) to try and also use it to help clean up the days/weeks of data from those Spam IPs
And now I am going to check my data, and maybe apply the OS filter as well if it looks problematic.
Views
Replies
Total Likes
We've actually run into "Unspecified" for OS, and after doing some breakdowns, we found that they mostly fall in two buckets:
It might be helpful to cross-check with other dimensions before you filter them out to make sure you don't filter out odd but meaningful use cases like we have.
Views
Likes
Replies