Skip to main content

I have a few questions regarding our event tracking setup and would appreciate your guidance:

  1. Tracking Unique Shadow IDs Before Signup:
    In our app, before a user completes the signup process, the user_id is null, and we assign a unique shadow ID to track events. However, we're facing difficulty tracking these unique shadow IDs before the actual user_id is generated. Could you please guide us on how to properly track these shadow IDs in Amplitude? If there is any documentation available that we can share with our backend team, please provide the link.
  1. Missing User IDs Post-Signup:
    After signup, we’ve noticed that some user_ids are missing in Amplitude, even though these IDs are present in our SQL database.
    Could you help us identify why these user_ids are missing in Amplitude and how to resolve this? 
  2. Some user_id are present in amplitude but not triggering the event, why this is happening and how to resolve?
  3. "Guest" Appearing in User IDs:
    We have observed that some user_ids are being recorded as "guest". Could you explain what this means and why this is happening?
Be the first to reply!

Reply