I need advise on how to better organize tracking via Amplitude.
We have 3 different space:
A) Public website with content B) Web app (Single page application with some onboarding form) C) IOS mobile app
Events coming from A are sometimes (usually) coming from anonymous users until they sign up or log in and then we identify them. When user login via B) web platform we create a user_id and he can fill in the onboarding form or see a screen with QR code or button to download the app.
Or user can sign in via app for a first time and we create user_id at that moment.
I want to implement JS SDK Web Attribution to track some activity on Web ( click button, view page) but most important store UTM parameters as user property and send it with all event user perform on mob app.
So the goal performs behavior user analysis in mobile app based on the source he came from (utm source, campaign and others).
The questions are:
1) Could I create two different projects Web and Mobile and share one user_id between these two projects?
2) When the user login via the existing user_id and we have some utm tag related to them from the website, send all these user properties with events.
3) or its better to keep one project (Web + Mobile)?
Now it is more interesting to keep track of mobile activity separately, and track MAU on Web (marketing) and Mobile MAU - core product.
Or maybe there are better way to track marketing source( utm tag) and link it to users.
Best answer by ttanView original