Expand my Community achievements bar.

Check out the November edition of the Analytics Community Lens newsletter to see what's been trending in the last two months!

Session Refresh data due to safari and iOS


Level 2

Hello Experts,


There is around 20% page view and unique visitor data in the session refresh marketing channel of an e-commerce website. This data is originating from Safari browser on Mac and iOS 16.5.

The other reasons like page load time, redirects, cross domain etc are rules out in our case. 

is something related to ITP causing this issue? Have you as well experienced the same? What could be the fix for this?


Many Thanks

2 Replies



Please note the Best Practices guidance with Adobe Analytics Attribution IQ capabilities is to not have Direct and Internal/Session Refresh channels anymore:



Check out the Marketing Channels FAQ for Session Refresh causal explanations:


Reasons for Internal (Session Refresh)

Last-touch Internal (Session Refresh) can only occur if it was also the first touch - see “Relationship between First & Last Touch” above. The scenarios below explain how Session Refresh could be a first-touch channel.

  • Session timeout: A visitor comes to the website and then leaves the tab open in their browser to use at a later date. The visitor’s engagement period expires (or they voluntarily delete their cookies), and they use the open tab to visit the website again. Since the referring URL is an internal domain, the visit will be classified as Session Refresh.

  • Not all site pages are tagged: A visitor lands on Page A which is not tagged, and then moves to page B which is tagged. Page A would be seen as the internal referrer and the visit would be classified as Session Refresh.

  • Redirects: If a redirect is not set up to pass referrer data through to the new landing page, the true entry referrer data is lost and now the redirect page (likely an internal page) appears as the referring domain. The visit will be classified as Session Refresh.

  • Cross-Domain Traffic: A visitor moves from one domain which fires to Suite A, to a second domain which fires to Suite B. If in Suite B, the internal URL filters include the first domain, the visit in Suite B will be recorded as Internal, since Marketing Channels see it as a new visit in the second suite. The visit will be classified as Session Refresh.

  • Long entry-page load times: A visitor lands on Page A which is heavy on content, and the Adobe Analytics code is located at the bottom of the page. Before all the content (including Adobe Analytics image request) can load, the visitor clicks to Page B. Page B fires its Adobe Analytics image request. Since Page A’s image request never loaded, the second page appears as the first hit of the visit in Adobe Analytics, with Page A as the referrer. The visit gets classified as Session Refresh.

  • Clearing cookies mid-site: A visitor comes to the site, and mid-session clears their cookies. Both First & Last-touch channels would get reset, and the visit would be classified as Session Refresh (because referrer would be internal).

Below is an example of Internal (Session refresh) being set both as first touch and last touch channels:

  • Day 1: User comes to the site on Display. First & Last-touch channels will get set to Display.
  • Day 2: User comes to the site on Natural Search. First-touch remains Display, and Last touch is set to Natural Search.
  • Day 35: User has not been to the site in 33 days and comes back using the tab they had open in their browser. Assuming a 30 day engagement window, the window would have closed and Marketing Channel cookies would be expired. The first touch & last touch channel will get reset, and will be set to Session Refresh since the user came from an internal URL.


Level 2

Thank You Brian for your answer. In our case the session refresh was precisely due to Safari Browser as Safari has extended its Tracking protocols. We are still figuring out by looking into the cause of mid session cookies deletion by Safari.