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
While ${documentReferrer} appears to return the correct value for other domains (like: www.twitter.com, t.co, linkedin.com, etc.) when the page's document.referrer value is "https://www.google.com/" ${documentReferrer} is empty.
I couldn't find any documentation indicating that the www.google.com domain carried any additional caveats. Is this a bug or expected behavior?
Inclusion of the vars.documentReferrer entry deviated from Adobe's documentation and appears to be the culprit. Once that extra value was removed referrals for "https://www.google.com/" started to work correctly.
Looking through the AMP documentation (https://github.com/ampproject/amphtml/blob/master/spec/amp-var-substitutions.md#document-referrer) is appears that the
${documentReferrer}
variable should reflect the JSdocument.referrer
.While
${documentReferrer}
appears to return the correct value for other domains (like: www.twitter.com, t.co, linkedin.com, etc.) when the page'sdocument.referrer
value is "https://www.google.com/"${documentReferrer}
is empty.I couldn't find any documentation indicating that the www.google.com domain carried any additional caveats. Is this a bug or expected behavior?
For some context, this behavior was observed after implementing the "adobeanalytics_nativeConfig" approach provided by Adobe: https://marketing.adobe.com/resources/help/en_US/sc/implement/accelerated-mobile-pages.html
The text was updated successfully, but these errors were encountered: