Skip to main content

We are running into 3-4 different problems with our data on Amplitude which I’d like to get help on. To start, we have instrumented the data into Amplitude via Google Tag Manager.

 

Issue 1: Multiple counting

For a single user, he/she is being counted multiple times (see 3 amplitude IDs being generated for me). What is the basis on which Amplitude assigns a unique Amplitude ID? What this is doing is really blowing up the metrics where WAU, DAU and MAU look overly large

 

Issue 2: How can we use E-mail or Visitor ID as the unique Identifier on Amplitude? 

 

Issue 3: How can we get E-mail address and the Visitor ID in the downloadable “CSV” data? These are missing from the data. 

 

Issue: Because the Vistor ID isn’t part of the CSV download report, I am also unable to view the entire ID in the Web UI

 

I suspect, because we aren’t using E-mail address or Visitor ID, as the unique identifier, it creates multiple sign-up events for the same user 

 

@Liping Yin Would love your thoughts on this

Hi Tools Fword,

Thanks for writing to Amplitude Community, happy to help!

Let's address your issues one by one:
Issue 1: Amplitude uses a system of User IDs, Device IDs, and Amplitude IDs to track unique users. A user can have multiple Device IDs and Amplitude IDs, but each unique user can only have one User ID. A user can get a new Amplitude ID when Amplitude sees a particular device ID for the first time. This is because Amplitude uses a system of three different IDs to track users: device ID, user ID, and Amplitude ID. The Amplitude ID is generated and associated with the user and device IDs that Amplitude has already collected for a user. Amplitude only needs one or the other (device ID or user ID) to generate an Amplitude ID; however, the user ID is preferred, as multiple unique users could share the same device. If there is a logged-in/logged-out state, users should also get a new Amplitude ID when they are logged out as they are considered anonymous users.

Issue 2: It is possible to use e-mail or visitor ID as the user ID. However, changing the user ID is not recommended. If you create a new user ID for an existing user, Amplitude will only recognize them as different unique users. If you want to avoid creating duplicate users, you could try setting the user with the same User ID value for the events before, during, and after they log in every time they access your product.

Issue 3: Can you let me know how you are downloading the data to a CSV? Are you pulling the data from a cohort or chart?

I hope this helps! Let me know if you have any other questions.

Best,
Yosimy


P.S. Checkout upcoming events and user meetups on our events page.

Reply


Terms & ConditionsCookie settings