Docs-website: Referrer URL is not passing with the `TLMK_Signup_Signup` event

Created on 14 Apr 2021  路  7Comments  路  Source: newrelic/docs-website

Related

We thought this change should fix this problem, but after testing it, it's still not working

https://github.com/newrelic/gatsby-theme-newrelic/issues/342

Step to reproduce

  1. go to docs.newrelic.com
  2. click on free account
  3. using the segment chrome extension view the TLMK_Signup_Signup event
  4. the referrer url should be present

Acceptance Criteria

  • [ ] The Referrer URL is present in the TLMK_Signup_Signup event.
  • [ ] This URL is visible in Segment
  • [ ] Zoe confirms this issue is resolved through the analytics pipeline.
  • [ ] Upgrade theme for docs, opensource, developer site.

Screen Shot 2021-04-13 at 5 27 08 PM

Screen Shot 2021-04-13 at 4 01 06 PM

P2 analytics bug gatsbysites 1

Most helpful comment

checked with security juuuust in case and we have the green light for noopener only

All 7 comments

This wasn't fixed by removing the utm param from the signup button click so moving back in todo

Okay, @LizBaker and I were able to figure out what's happening. The referrer field was not being sent when a user clicks the free account button on our sites. This was caused by the rel="noreferrer" property on our the SignUpLink component.
The noreferrer and noopener types control the information passed to the new tab. The former prevents referrer information from being passed to the new tab and the latter prevents the new tab from accessing window.opener.
The noopener type is sufficient to protect the user from any malicious code, but it is not implemented in some older browsers.

We have 2 main options to fix this:

  1. Remove the noreferrer type and stick with just noopener
  2. Link directly to the signup page instead of opening it in a new tab

References:

I like 1 馃コ

checked with security juuuust in case and we have the green light for noopener only

I asked Zoe for input here as well. 馃啒

Let's go with option 1 for the win here. @aswanson-nr 馃

published a release for the theme so now its 2.0.1. i pushed a branch for the theme upgrade in opensource and docs, but was waiting for other changes in developer to go through. so those can be picked up.

Was this page helpful?
0 / 5 - 0 ratings