Feature request: separate AdId obtaining from Init

[Remstam]

To organize some analytics on my custom server and Adjust reports I want to do two things:

1. Send Adjust AdId to my custom server to connect server player profile with Adjust reports later
2. Send server player profile id to Adjust SDK to find out later that player in Adjust reports with it's server player profile id (This can be done via ExternalDeviceId property)

However, this leads to a sort of deadlock: I need AdId to authorize at custom server first (I'd like to have AdId right here - I can send AdId later, but some info may be lost because player is not paired with AdId yet), but at the same time I need ExternalDeviceId (which is what my custom server returns) to be set for Adjust SDK before Adjust init call.

I used to work with AppsFlyer SDK before that, and it has separated "start" and "init" calls - that helps break the deadlock like this:

• call AppsFlyer's start
• AppsFlyer's ID is available
• call auth with AppsFlyer's ID on custom server
• custom server returns player's server id
• set player's server id to AppsFlyer configuration
• call AppsFlyer's init

I thought that maybe sort of equivalent of this can be done for Adjust: a separate SDK call to just get AdId and another call for init (which is current Init call)

I have read the discussion related to this question in #274 , so just wondering if there are some new ideas about it and whether this can be technically done at least.

[uerceg]

Hey @Remstam,

Thanks for the detailed question.

Unfortunately, what you are looking for in the current state of things is not doable on our end. Semantically on Adjust SDK side we also do distinguish under the hood between init phase (where we are pretty much setting stuff in memory, but are not transmitting anything to our backend) and actual (let's call it) started phase where session tracking and rest of things start (and where we are starting to communicate with our backend).

But as you have probably seen in the linked ticket, the Adjust ID (adid) is something that is being generated on our backend and is something that SDK must ping the backend in order to get it. And for our SDK, there is no dedicated request for such thing, but rather whatever request is to be sent first when SDK is about to start to transmit data, in the response to that request, we're gonna get information about the adid from the backend.

So yeah, for the time being, this indeed is kind of a deadlock situation. If we would look into solving this, it would indeed be like you stated in your issue title - a feature request. Having in mind that adid must be generated server side, it appears that some kind of an on demand request to get adid should exist in some form in the flow, but there's probably quite a few things we would need to take care into consideration next to the implementation flow itself, such as privacy - can this be achieved in a reliable way on our end with respect to all privacy constraints.

I'll raise this topic on our end and we'll definitely discuss it and keep you posted.

In case you have any further questions / ideas on this topic, feel free to ping.