Soomla SDK provides 3 alternatives to handle User-ID:
- Developers can initialize Soomal SDK with their own User-ID
- Changing the User-ID, after soomla SDK was initialized
- In case Soomla SDK was initialized without User-ID, Soomla will set default User-ID
Starting version 5.18.0 we made a change so that:
Soomla will use a Soomla User-ID to mark the user, this is an identifier that is not persistent across apps and can’t be used for profiling. In earlier versions, the default behaviour was to set the IDFA/GAID as the User-ID
This means that if you do already set the User-ID - the change will not apply
Q - Why do it's important to set User-ID?
A - We are taking steps to limit the use of IDFA/GAID only to publishers who knowingly choose to.
Q - What apps are impacted by this change
A - Your app will only be impacted by this change if you never set the User-ID when you initialize the Soomla SDK
Q - How is the User-ID used in SOOMLA
A - There are two features that rely on User-ID in Soomla:
the data dumps - if you account is configured to send data to a bucket and you are ingesting the data from there - the User-ID that is being used in the data dumps is the User-ID mentioned above
User journey - this is a premium feature allowing you to use the dashboard to follow a specific user and see his entire ad experience - the User-ID is used to identify the users in this screen
Q - Can I avoid this change
A - Yes!
If you have been using the IDFA/GAID as the User-ID in your system and wish to keep doing so you can simply read the IDFA/GAID and use it to populate the User-ID using soomlaConfigBuilder.setUserId(userId) or SoomlaTraceback.getInstance().changeUserId(userId);