Q about user & session merge in amplitude
we use the web amplitude gtm to report all events. Due to the incomplete data sent by web pixel, we are getting only ~95% of the events to amplitude. For finantial events like purchase/refund this is too much.
Therefore, we migrated only the purchase events to send from our back end side.
We do send amplitude session id, amplitude device id and also our User ID with every purchase event.
We would expect that amplitude will merge data like geo location, device type and utms from the session start and attach it to the purchase event. But its not happening
Amplitude treat the purchase events from back end very strange.
- It does assign the purchase events to the session (can be seen in the User Look-Up)
- it does not attach those events utm’s params, therefor all purchase events are considered as no utms - direct traffic
- SOME of those purchase events get geo location and device data and some not
Are we doing someting wrong? is this amplitude bug or its just the way amplitude behave ? :)
Best
Ronen