Our first tracked events in Amplitude are “User Signed Up” and “User Signed In”. These events are the starting point for the user’s journey.
The tracking of these two events needs to be done using HTTP API V2. Any subsequent events (such as “Feed Scrolled”, “Created Post”, etc...) will be done using the JS SDK.
A few questions:
- From what I understand, if we use HTTP API V2 then we have to manually update all the user’s properties such as location, IP, referrer, etc?
- Should/can we grab those user properties from the JS SDK and then add them to our POST call coming from the backend?
- We tried doing the above by sending an event with some of the user properties but got a random event ID that wasn’t in sequence with any preceding or subsequent events. We can set event_id to 1 but not sure if that’s recommended.
- What is the safest way to do this? Basically we want to send an event that the user signed up with his user_id. Ideally it would all be in the JS SDK but we can only safely know when a new account is created from the backend so that’s why we’re trying to use HTTP API V2.
Best answer by belinda.chiuView original
@davidgrey! Welcome to the Amplitude Community I’ll go ahead and address your questions accordingly:
Hope this helps!
Thank you so much
@belinda.chiu! Your answer definitely cleared things up.
@davidgrey ! Happy to have helped :)