-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose Adjust Id #51
Comments
@Disturbing We will internally discuss this request and will let you know as soon as possible. |
@uerceg Thanks :)! A bit more info on why I'm asking for this. Right now the System.deviceUniqueIdentifier in Unity: http://docs.unity3d.com/ScriptReference/SystemInfo-deviceUniqueIdentifier.html Does not return a consistent ID for us to map adjust data on our backend. We'll have to code some native plugin to get the ids sent from adjust as well such as the gps_android_id or idfa, or whatever you guys actually decide to use. At the end of the day, goal is to use your callbacks system and have us register accounts on our backend with some sort of id to cross-map everything. Even so, this request for the adjust id does not exactly solve 100% use cases for everyone. People who really care about the click callbacks for instance won't be able to use adjust id to help since adjust id does not exist with those. Long story short, exposing 'some' or all of the ids you guys use in the placeholders: https://partners.adjust.com/placeholders/ so that we can have our data backend work well with your callbacks would be greatly appreciated. Thanks for reading! |
Just a short update on this issue. We're preparing native SDK updates in beginning of 2016 which will enable us to provide you this info. As soon as we update native ones, we'll start with updating non-native SDKs and bring that functionality to Unity SDK as well. Cheers |
Thanks for the update @uerceg - Do we have an ETA ( maybe a month ) I can depend on? I'm still looking forward to seeing this ticket come to fruition. |
Hi @Disturbing Unfortunately not any accurate ETA. You can follow our native SDKs PRs for iOS and Android: adjust/ios_sdk#150 Once those are merged, we'll start with Unity SDK upgrade. We're aiming to have native SDKs updated this week, hopefully at latest point next week. So, maybe a month is kinda realistic ETA for Unity SDK update, but not a promise. We'll give our best to update it as soon as possible. :) |
Cool, An easier request would be to expose the GPS and IDFA that you guys are getting / storing in the callbacks of installs / clicks, etc. Reason being is all the methods I've tried to map my database -> callbacks coming from adjust, i could not get exact ID's to match for both google and apple. That's all I need to solve, simply exposing all ids that you guys store for external use / us to reference would be great so we're all on the same page, literally :). |
To match our data to yours you should use our |
Agreed - just waiting for the merge so the Unity SDK can expose the adid unless it's hidden somewhere already :)? Got tons of data waiting to be linked! |
At the moment, it's actually hidden, except of course in verbose logs. :) As soon as we update native SDKs, we'll update Unity SDK with those changes. |
Otay.. waiting on it! 👍 |
Thanks for the reminder. You can check in the guide how to access the device ids https://github.com/adjust/unity_sdk#12-device-ids |
Works, thanks a ton folks! |
Can you expose the adjust id so we can manually map our players to callback data?
The text was updated successfully, but these errors were encountered: