Bots - Hundreds of IP Addresses that Change (2017-Dec) | Community
Skip to main content
J
jonr4296285
December 27, 2016
Solved

Bots - Hundreds of IP Addresses that Change (2017-Dec)

  • December 27, 2016
  • 1 reply
  • 859 views

Please see Cristine Drach post on July 1 2015:

http://help-forums.adobe.com/content/adobeforums/en/analytics-forum/adobe-analytics.topic.html/forum__y6ao-hello_thereisa.html#

18 months later and I also have this issue. I have ~5,300 one-hit visits from 13 cities around the world, most of which my company has no connection to. The IP addresses are very dispersed and no user agent information is collected. Adobe's Live Assistance rep said I should post here:

Harveer Singh Gill: Jon I won't be able to forward this incident to engineering team as this is not a bug with the tool as of now, it is working as designed. However, you can share your suggestion/recommendations for any new features directly with our product engineering team at ideas.adobe.com

Hopefully, Adobe can figure something out to exclude this bot traffic.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Gigazelle

Hi Jon, Harveer is technically correct. The data set is reporting on the information it received. Other than the IAB bot list, there's really no way to determine the legitimacy of a given hit unless you specify as such.

Here are a couple things I'd check:

  • Make sure your report suite is configured to filter all IAB bots.
  • Use segmentation to try and find a common thread for all suspected bots
  • While user agent is not an available variable to use, you can collect it in a custom variable like a prop. It is also available in clickstream data feeds.

1 reply

Gigazelle
Adobe Employee
GigazelleAdobe EmployeeAccepted solution
Adobe Employee
January 20, 2017

Hi Jon, Harveer is technically correct. The data set is reporting on the information it received. Other than the IAB bot list, there's really no way to determine the legitimacy of a given hit unless you specify as such.

Here are a couple things I'd check:

  • Make sure your report suite is configured to filter all IAB bots.
  • Use segmentation to try and find a common thread for all suspected bots
  • While user agent is not an available variable to use, you can collect it in a custom variable like a prop. It is also available in clickstream data feeds.
Terms & ConditionsAccessibility statement

Loading footer...