Channel overview report | Session refresh (internal) traffic over 20%



Attempted to set up the channel overview report for a hotel website (domain A) and its booking engine (third-party shopping cart, domain B) utilizing third-party cookies and common omniture report suite. 

Although both domains are added to internal URL filters and

- channel processing rules were set up based on what Adobe outlines (screenshot attached) 

- last-touch channel override was turned off for direct and session refresh (internal) channels

- confirmed that appmeasurement tracking is set up correctly and there is no re-direct on the landing pages

we have been struggling with around 20-25% last-touch session refresh (internal) traffic for more than a month now.

As a last resort,we reached out to our Adobe consultant who advised that our numbers are align with the trends what their experts have seen:

" — the 50% we confirmed for Session refresh + Direct traffic is the trend most experts have seen across different clients w/r to Adobe Analytics, but it will vary based on strength of a clients brand."

This puts us in a very weird situation as based on the channel overview report we can not tell where 20-25% of the website traffic comes from. 

Luckily we have other ways to report on channel performance but would have been super comfortable to use the channel overview report on a daily basis for first and last-touch results.

Any advice or best practices on this would be much appreciated! 

Thank you!

View Entire Topic



potentially yes - Safari is particularly bad for 3rd party cookies which are needed when doing cross domain. If you're using an older version of MCID which has the short time out and no support for cross domain then I wouldn't be surprised if this is the issue, take a look at your entry pages for session refresh and see if it's cross domain. If it is then i'd recommend using the Append Visitor ID Function -

We had the exact same issues with visitor ID, very high session refresh caused by cross domain and the visitor ID timeout being too short. When we increased the visitor ID timeout time we noticed a drop in session refresh and then when we implemented the Append Visitor ID function which appends the visitor ID to the cross domain URL it dropped even further to within acceptable levels.