Prevent self-referrals in AMP pages

Currently, when not overridden, the Viewer of an AMP page always reports as referrer window.document.referrer

This has the side effect that AMP-ANALYTICS always reports as referrer the previous visited site, and does not keep the original referrer of the current session when, for example, a user visits a second page.

At the end this means that a site like AMP Project, or a PWA that uses AMP Shadow, has almost all its traffic reported as referral.

I think that AMP could have the notion of session, like it already has for client in cid-impl.js, so we can do things like preserving the referral for the current session.

[avimehta]

correct. This issue will get fixed by that PR.

On Tue, Aug 22, 2017 at 1:17 PM, Rudy Galfi [e-mail] wrote:

It sounds like #11027 https://github.com/ampproject/amphtml/pull/11027 fixes this according to solution 2 described previously.

@avimehta https://github.com/avimehta @lannka https://github.com/lannka Can you confirm this will also cover the " https://google.com -> https://daily.spiegel.de -> https://daily.spiegel.de/news/…" case (thereby making the recommendation to add https://daily.spiegel.de to referral exclusion list obsolete)?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ampproject/amphtml/issues/7184#issuecomment-324139444, or mute the thread https://github.com/notifications/unsubscribe-auth/AAK8n6_7VnnX_yEVSdcSfA3o8xRytAQDks5sazdNgaJpZM4LsqMN .

[jridgewell]

Oohhh, I think I get it now:

1. Search for [Amp By Example]
2. Click top result
3. Click any link (should cause a top page navigation, not iframe navigation)
4. In Inspector: window.services.viewer.obj.getReferrerUrl()

In this case, I get https://ampbyexample-com.cdn.ampproject.org/v/s/ampbyexample.com/?amp_js_v=6 as my referrer.