Closed Bug 1024507 Opened 11 years ago Closed 11 years ago

Add third-party sign-in state tracking to "Sign in to edit" page

Categories

(developer.mozilla.org Graveyard :: General, enhancement)

All
Other
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: groovecoder, Unassigned)

References

Details

(Whiteboard: [specification][type:change])

What feature should be changed? Please provide the URL of the feature if possible. ================================================================================== The "Sign In with Persona" to edit page: https://developer.mozilla.org/en-US/users/login?next=/en-US/docs/User%3Agroovecoder%24edit What problems would this solve? =============================== Signing up for MDN via Persona is a foreign experience for many visitors. We would like to know what other identity providers our visitors use to help them sign up for MDN more easily. Who would use this? =================== MDN devs & stake-holders What would users see? ===================== The copy from bug 988124: "Mozilla is working to improve our MDN sign-in process. We're running a test to analyze what third party sites are most popular for sign-in. When you access this page during the test, we detect (in an anonymous way) if you are also signed-into: Twitter, GitHub, LinkedIn or Stack Overflow. After the test, we'll use the aggregated results to select the best third party sites for MDN sign-in." What would users do? What would happen as a result? =================================================== 1. Visit an article 2. Click 'Edit' 3a. See the above copy 3b. We set a Google Analytics custom dimension for each site - Twitter, GitHub, LinkedIn, or Stack Overflow - that the user is currently signed into. Is there anything else we should know? ======================================
Severity: normal → enhancement
See https://bugzilla.mozilla.org/show_bug.cgi?id=988124#c16 for the final copy to put on the page that tracks the visitors' sign-in state.
Blocks: 1052453
No longer blocks: 1052453
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/5550d47b1fa2fee1183588101cfe0ace6cc8fcf1 Bug 1024507: Measure use of Twitter and Facebook Luke organized the logic so that Google Analytics event calls would work correctly [1]. His commit was squashed into the prior commit to maintain a history of working commits. [1] https://github.com/groovecoder/kuma/commit/4bbd5f89e3539faeecdcbdb850c45508e265b709 https://github.com/mozilla/kuma/commit/857325db8c4a61c2cacbf396184263eee583a3d3 Merge pull request #2734 from openjck/1024507-twitter-facebook-research Bug 1024507: Measure use of Twitter and Facebook
Can we close this?
Flags: needinfo?(lcrouch)
Yup.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(lcrouch)
Resolution: --- → FIXED
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.