Expand my Community achievements bar.

Join us at Adobe Summit 2024 for the Coffee Break Q&A Live series, a unique opportunity to network with and learn from expert users, the Adobe product team, and Adobe partners in a small group, 30 minute AMA conversations.
SOLVED

What does session refresh actually mean?

Avatar

Level 1

So we've been neglecting it for a long time now within our reporting by taking it out... but the curiosity got the better of me.

Could someone please help me and my team understand what session refresh actually means within the Last Touch Marketing Channel report? 

 

See attached for a reference. 

 

Thanks! 

1 Accepted Solution

Avatar

Correct answer by
Level 7

Hi there,

Session refresh can mean a few things:

  1. Internal URL filters are wrong
  2. Not all pages of the site are tagged
  3. Long videos or content pages
  4. Landing page load times are long
  5. Redirects
  6. Cross Domain issues

If you're having issues with high session refresh (I think Adobe considers high to be over 4%) then take a look at your internal URL filters (if you're admin), and a full site tagging audit.

I had big issues with session refresh caused by cross domain issues and visitor ID not carrying over the same VID. This has been resolved with the latest updated to the VisitorID API and using the crossdomain function.

 

Check out this blog article for info: https://blogs.adobe.com/digitalmarketing/analytics/marketing-channels-5-steps-to-troubleshoot-sessio...

View solution in original post

2 Replies

Avatar

Correct answer by
Level 7

Hi there,

Session refresh can mean a few things:

  1. Internal URL filters are wrong
  2. Not all pages of the site are tagged
  3. Long videos or content pages
  4. Landing page load times are long
  5. Redirects
  6. Cross Domain issues

If you're having issues with high session refresh (I think Adobe considers high to be over 4%) then take a look at your internal URL filters (if you're admin), and a full site tagging audit.

I had big issues with session refresh caused by cross domain issues and visitor ID not carrying over the same VID. This has been resolved with the latest updated to the VisitorID API and using the crossdomain function.

 

Check out this blog article for info: https://blogs.adobe.com/digitalmarketing/analytics/marketing-channels-5-steps-to-troubleshoot-sessio...