M,If you have session refresh marked to override you will see an influx in traffic.I think pulling raw data to see where you are getting the most of these is going to be the best way to determine where they are coming from and why.If you would like help from client care please email clientcare@adobe.comPlease include—Company:Report Suite:Issue:Thanks, Steven Hofheins | Adobe Support

I agree with Gigazelle​ and H_LI would change the "then" condition to "then within 1 hit" to be sure it is really a path you are looking for.remark: use falloutinstead of manually creating the segment you could follow those steps:In workspace create a new FalloutAdd the touchpoints as in your segmentChange the "path" between the touchpoint to "next hit"Change Fallout setting to "start on first touchpoint" and "visit based" (gear icon top right)on last touchpoint hit "create segment from touchpoi...

if you want to see the (old) "reports" you need the corresponding permission. within the product profile, change permissions for "tools" and allow "reports and analytics access"here is the link to the help page for the legacy permission settings: Customize Analytics Tools Permissions , it looks different under product profiles but the logic/naming is the same.

It's an older page, but it appears to still have relevant information: https://analyticsdemystified.com/adobe-analytics/internal-campaigns/

My 2 cents..Classifying the campaign variablePro - You don't have to burn any other variables. Maybe you have a ton of unused variables today, but you never know how your implementation will evolve/grow down the line.Pro - Classifications are retroactive. This is one of the biggest pros for classifications. Typos happen all the time. Format / value requirements change all the time. Once a key (base/raw value) is recorded, it's there forever unless you want to pay Adobe a lot of money to scrub it...

This would happen if you're sending multiple image requests on each page, either using multiple page views or a page view and a custom link call. If you have a URL you can share, I'd be happy to validate that.If you're not willing to update your implementation, you could use the alternative calculation of [single access] / [entries]. Single access counts towards anyone who has a single pagename value in a visit, which means that it counts people who trigger multiple image requests to the same pa...