Skip to main content
Solved

App Set ID instead of Ad ID...implications for existing data?

  • October 8, 2021
  • 3 replies
  • 1092 views

Forum|alt.badge.img

I’m currently looking at the Android 12/Google Ad ID topic and it is my understanding, that the Amplitude documentation suggests to use the App Set ID to identify a specific device instead of the advertising ID. Or in more technical terms client.useAppSetIdForDeviceId(); instead of client.useAdvertisingIdForDeviceId();  

Before implementing this change I would like to understand the implications for our existing data:

If a device so far was identified via Advertising ID will switching to the App Set ID create a new Amplitude ID or will Amplitude be able to stitch new data to old data?

For new users it is not a problem but for existing users I would like to make sure, that our identification and therefore calculation of unique users remains unaffected. 

Best answer by Denis Holmes

If you create a new Device ID and the User does not have a user ID, Amplitude might have difficulty linking the user to their previous device ID and may indeed create a new Amplitude ID/User. However, if you set a new Device ID with the same User ID, then Amplitude will be bale to merge the user ID to the correct user, assuming they already had a User ID set before this. It is best to pass the User ID with the event the device ID changes so that Amplitude will know the user to merge on. 

 

I hope this helps! Let me know !

View original
Did this topic help you find an answer to your question?

3 replies

Denis Holmes
Team Member
Forum|alt.badge.img+8
  • Team Member
  • 448 replies
  • Answer
  • October 11, 2021

If you create a new Device ID and the User does not have a user ID, Amplitude might have difficulty linking the user to their previous device ID and may indeed create a new Amplitude ID/User. However, if you set a new Device ID with the same User ID, then Amplitude will be bale to merge the user ID to the correct user, assuming they already had a User ID set before this. It is best to pass the User ID with the event the device ID changes so that Amplitude will know the user to merge on. 

 

I hope this helps! Let me know !


Forum|alt.badge.img

Hello again,

I have a question considering the device ID on Android :Based on this article

https://help.amplitude.com/hc/en-us/articles/115003135607-Track-unique-users-in-Amplitude#h_7cf7c47f-ec71-4e15-8c47-a2bda5d84186 “Device ID: Amplitude pulls the IDFV or generates a random alphanumeric string for the device ID;”

I assume that so far Amplitude always generates a random device ID for Android Users as there is no equivalent to the iOS IDFV. So Android 12 should not have any implications for the Device ID at all?

 

 

 

 


Denis Holmes
Team Member
Forum|alt.badge.img+8
  • Team Member
  • 448 replies
  • October 26, 2021

Hi @Carolin Kobelt ,

 

In this case, you could set the App ID as the Device ID as described here. You can regenerate a device ID here. I would reach through our android documentation in full and then you should be able to make the best decision given your context.

 

Hope this helps!


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings