Uploaded image for project: 'VS Code Extension'
  1. VS Code Extension
  2. VSCODE-249

Attach anonymous ID of users to the url of the cta link to Atlas

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 0.6.0
    • Affects Version/s: None
    • Component/s: Atlas CTA
    • None
    • Not Needed
    • Iteration Athens, Iteration Edinburgh, Iteration Firenze

      Problem Description

      Currently there is no way to link a particular user from VS Code to Atlas in Segment.  In Atlas a different anonymous id (and further down, user id ) gets created. 

      The link can be created by adding the following parameter to the url of the Atlas CTA (https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/querystring/ for reference):

      https://www.mongodb.com/products/vs-code/vs-code-atlas-signup?{{ajs_aid=abc123&....}}

      *,where *abc123 is the anonymous_id of the user in VS Code. This will trigger the user() method call while on the mongodb.com registration page  which will assign the anonymous_id to the newly created user, like so: 

       
      analytics.user().anonymousId('abc123');
      In theory  this should create the user in Segment on the mongo website side that can be then linked in tools like Amplitude (maybe) but definitely using Segment data. Once the registration is completed, the user gets a userID (expected to switch to "analytics unique ID" which is Okta ID,  according to this scope: https://docs.google.com/document/d/1unG654Dqc10_RKC8iDC3fihE-hSxjiVg48joi187a9M/edit?usp=sharing ) 

       

      Steps to Reproduce

      Expected Results

      It should be possible to link the users from VSCode to the ones in Atlas that register through the CTA link. 

      Actual Results

      Additional Notes

            Assignee:
            rhys.howell@mongodb.com Rhys Howell
            Reporter:
            natalya.furmanova@mongodb.com Natalya Furmanova
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: