HUGE spike in direct/bouncing traffic

Dear Devan,

Sorry, not sure why VISTA Rule is needed here? Any you give us some more background on Adobe's suggestion on VISTA rules?

Thank You!

Arun

Hi Arun,

When I've pointed out the traffic that is a HUGE spike and bouncing at 100% and all from a handful of IP addresses, Adobe is suggesting it is bots  and I should filter out the traffic. I can't keep up with bot rules (there are SO many coming in each week) that they suggested VISTA rules.

I'm trying to understand the cause of the spike and what can be done to prevent it - I'm not familiar with bot-type activity best practices!

Dear Devan,

Fine. Either we need to include the list of IP Address in Bot Rule or Adobe has to exclude by VISTA rules.

But it think even for Adobe, they need to figure out the Bots. So there should be some way to find those bots, i am curios on how would they setup VISTA.

Have you tried RegEx to exclude the set of IPs?

Thank You!

Arun

Yes, those are on and have been since we first started using Adobe.

I also have at least 30 custom bot rules defined to filter out traffic that was 100% bounce in weird spikes from months past.

I am using Adobe Bot rules -- filtering by IP address for bots that I identified by getting a datawarehouse report of visits/pageviews by IP address PratheepArunRaj​

Dear Devan,

Sorry, I am afraid that if there were any other better solution than the current.

Thank You!

Arun

can you see any other "common attributes" for those bounces? we once had a similar case and figured out they where all coming with a certain "user agent" (very unusual combination in our case). this allowed us to set the filter on those criteria (apart from IP where you are always too late...)

How did you get the user agent? That field is not available to me in data warehouse!

devanm60563341​ You can get the UserAgent through Data feed as that's the only option, UserAgent is not available through reports or DWH.

Or you can use eVar to capture the UserAgent in reporting and leverage that but it has it's own advantage / disadvantage, viz. due to the monthly limit of unique value a variable can hold you end up exhausting that limit and some UserAgent values end up getting into the low traffic line items. but you can definitely use that approach to see the UserAgent value in reporting.

or you can data feed as mentioned above.