Skip to main content

We have a series of the following events:

  1. A new anonymous user lands on our website
  2. We set utm params and other user properties
  3. They make a purchase
  4. Server side registers the purchase and creates a user with userId.
  5. At this point in nodejs we pass the userId to amplitude identity and we send a “purchase event” to amplitude from the server.
  6. After that, client side receives the userId and amplitude web sdk also sets userId

The problem that we run into is on step 5 the amplitude user that is attached to the “purchase event” is missing the utm and other properties that we set on step 1.

 

My understanding is that it happens because amplitude only merges the user ids on step 6 and on step 5 amplitude knows nothing about a user with “userId” hence no fields.

 

Question: What is the best way to make sure the “purchase event” has all the properties of the initial anonymous users? How do we tell amplitude nodejs sdk that we are dealing with a specific anonymous user?

Seems like we need to pass deviceId and amplitudeId to the server and then set them in the amplitude nodejs sdk, but there seem to be no way to read and set both of those ids through the SDKs, unless I missed it.

 

Any help on that is much appreciated!

 

Thanks,

Artem

Resolved it by passing deviceId.

 

From the doc on setting up cross domain tracking, which applies to client/server case as well:

 

Set up cross domain tracking

 

To track an anonymous user who starts on Site 1 and navigates to Site 2, you'll need to pass the device ID from Site 1 as a parameter to Site 2. After that, you'll have to reinitialize the SDK with the passed device ID:

  1. From Site 1, grab the device ID from amplitude.options.deviceId.
  2. Pass the device ID to Site 2 via a URL parameter or third party cookie.
  3. Initialize the Amplitude SDK on Site 2 with amplitude.init('YOUR_API_KEY', null, {deviceId: '$DEVICE_ID'}).

Reply


Terms & ConditionsCookie settings