I posed this question on the monthly call to see what other WTD users are doing. It centres around Aggregators and the fact they have a large effect in scoring. Mint in particular has the largest amount of traffic in our environment and constantly is responsible to triggering high scores.
I've been able to write rules that ignores the IP's but that doesn't stop the scores from elevating.
Is the simple answer whitelisting those IP's in schema? or is there another way to eliminate this activity from affecting your scoring?
Hi, Chris. Having worked with a variety of our customers I can tell you that the most popular approach seems to be whitelisting IP ranges via Schema. This prevents high-traffic IP's from impacting WTD scores, leaving the remaining traffic to be scored accordingly.
It's pretty much an "either-or" scenario. Either you address high-traffic/aggregator traffic by whitelisting it (and thus prevent the scoring impact), or you handle it in other ways (for example, via an EDS list). The later approach allows the scoring impact, but gives you the flexibility to keep the traffic in case you are suffering attacks/fraud from a percentage of users in those IP ranges. Of course, there are pros and cons to each approach.
Thanks for this Michael,
Yeah this is what seems to be the best strategy. I'm wondering if there is a common list of aggregator IP that people are using that someone would be willing to share.