Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken referrer due to single-sign-on #12848

Closed
Vinutab opened this issue May 7, 2018 · 4 comments
Closed

Broken referrer due to single-sign-on #12848

Vinutab opened this issue May 7, 2018 · 4 comments
Labels
answered For when a question was asked and we referred to forum or answered it.

Comments

@Vinutab
Copy link

Vinutab commented May 7, 2018

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.

@Findus23
Copy link
Member

Findus23 commented May 7, 2018

Have you seen https://matomo.org/blog/2017/02/how-to-track-single-page-websites-using-piwik-analytics/ ?

You can always set the referrer manually with

_paq.push(['setReferrerUrl', previousPageUrl]);

@Vinutab
Copy link
Author

Vinutab commented Jul 9, 2018

Hi,

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.

Can you please help.
Thanks in advance

@jbrule
Copy link

jbrule commented Jan 31, 2019

@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.

@Findus23
Copy link
Member

Answered here and in #12932 (comment)

@Findus23 Findus23 added the answered For when a question was asked and we referred to forum or answered it. label May 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
answered For when a question was asked and we referred to forum or answered it.
Projects
None yet
Development

No branches or pull requests

3 participants