Skip to main content

Hello, 

 

We have a client using our platform for AB testing and they use Amplitude as their main analytics platform. 

 

To be able to compare data collected by our platform and Amplitude we’re sending AB testing variation id to Amplitude using JS SDK 

window.amplitude.getInstance().logEvent(key, eventProperties);

We’ve verified the event is successfully firing for 94% of users yet the events are not associated with events send by our client from their backend. They use a mixture of Segment events and Node backend events. 

 

How can we assure front-end events are tied with back-end events?

Hi @Invesp CRO ,

 

Thanks for writing in! This sounds like an issue where the backend events are coming in without a User ID and with a different Device ID than the front end events which would make it difficult for us to merge the user profiles if they do not share a same Device ID or User ID. Are you sending your back end events with the same Device IDs and User IDs as the front end events for those users? Can you show me a chart or a user URL so I can look into this some more for you? 

 

Kind Regards,
Denis

Thanks for the response Denis, 

 

Unfortunately we don’t have any control over the backend events, they’re sent from Segment. 

 

We’ve tried adding some other Event Properties that we know the backend is also sending like checkout_id and order_id but still no improvements.

 

Here’s an example link: https://sundaysfordogs.com/dogs/cd4e5a19-8bac-4d97-8d0f-68eee6ceaeb9/build/gender

Hi @Invesp CRO ,

 

Are you send in a lot of the front end events in with a User ID? Would it be possible for you to attach the User ID in your back end events or use Segment’s identify calls to update users User IDs if possible? THis would be necessary in order to merge the users. You could try and see if you can get the information from Segment and possibly pass it to your front end? Would that be possible? 

 

Kind Regards,
Denis

Thank you Denis, we’ll contact Segment to see if they can add User ID to the events. 

Reply


Terms & ConditionsCookie settings