You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we open the site(site A) and click a link leading to another site B.
Site B will notice that the visitor has no active single-sign-on session and redirect the visitor to the login page, which will redirect you back to site B.
The referrer is now 'site B', instead of the original site referring (site A).
Can anyone please advise.
The text was updated successfully, but these errors were encountered:
Sorry, there was a mistake in my earlier understanding.
When we open the site(site A) and click a link leading to another site B.
Site B will notice that the visitor has no active single-sign-on session and redirect the visitor to the login page, which will redirect you back to site B. The referrer is now the login link of the Site B instead of the original site referring (site A).
So setting _paq.push(['setReferrerUrl', previousPageUrl]); is providing the login link of site B.
I also tried paq.push(['setConversionAttributionFirstReferrer', true]);, in the site B tracking code, but it is still showing the referrer as login link of site B.
@Vinutab There is no way that matomo can know the original referrer as the browser does not forward it through the SSO (that would break standards). To remedy the issue many SSOs can be configured to carry the referrer forward as a querystring parameter i.e &referrer=http://referrerwebsite.com . If the SSO supports that you can then grab the referrer from the querystring and set it like @Findus23 said.
When we open the site(site A) and click a link leading to another site B.
Site B will notice that the visitor has no active single-sign-on session and redirect the visitor to the login page, which will redirect you back to site B.
The referrer is now 'site B', instead of the original site referring (site A).
Can anyone please advise.
The text was updated successfully, but these errors were encountered: