Expand my Community achievements bar.

Webinar: Adobe Customer Journey Analytics Product Innovations: A Quarterly Overview. Come learn for the Adobe Analytics Product team who will be covering AJO reporting, Graph-based Stitching, guided analysis for CJA, and more!
SOLVED

Sudden rise in spurious traffic

Avatar

Level 4

Hi, we are seeing a sudden spike in our direct traffic. It has inflated by nearly 100%, plus this extra traffic is not having any attributed associated with it and everything is falling into none. This has increased our overall visit count, but the page views are consistent, indicating these are link calls which are setting a separate cookie other than the regular cookie. We cant see any extra hit on the browser debuggers. Is there any way to filter out the cause of these hits?

Sanmeet

1 Accepted Solution

Avatar

Correct answer by
Level 4

Do you have any contents that is shared/accessible from other websites? 
e.g. do you have your video players embedded on other websites? Or any social share widgets that has custom link tracking, OR any other such instances?
In such cases you will see those visits/visitors in your report suite, but there will not be an increase in page views (because video views or custom link tracking will not count as page views)

Also check your exit links report for any unexpected domain values. Someone might have copied your source code and pasted it on their website without including the s.t() code section.

View solution in original post

1 Reply

Avatar

Correct answer by
Level 4

Do you have any contents that is shared/accessible from other websites? 
e.g. do you have your video players embedded on other websites? Or any social share widgets that has custom link tracking, OR any other such instances?
In such cases you will see those visits/visitors in your report suite, but there will not be an increase in page views (because video views or custom link tracking will not count as page views)

Also check your exit links report for any unexpected domain values. Someone might have copied your source code and pasted it on their website without including the s.t() code section.