Unclear how to use with cross-app tracking.

[MattAndDev]

Hi, I would like to have clarified how to use this SDK in the context of a cross-app tracking (web-views/trusted web activities).
We need this SDK to be able to reference unique IOS or Android users to guarantee solid tracking of installs vs. events.

With this current implementation it's not clear how to instruct the sdk to map a given session/event to a given install (via device id).

Could you help me to find out how this can be achieved?

ATM we have our own small implementation of this SDK to achieve the above

[uerceg]

Hey @MattAndDev

Thanks for reaching out. Unfortunately this kinda goes out of scope of us devs who are keeping an eye on GitHub tickets. Either your dedicated account manager or firing email to support@adjust.com in case you don't have one is definitely best place to ask questions like this and get response from our support team who is definitely knowledgable on this topic and strategies how to implement this.

Sorry for not being able to provide any better answer in here, but in case you have any further questions on the topic, feel free to ping in here and comment/reopen.

Cheers!

[MattAndDev]

Hi there, thank you for the quick reply. I work for a large company and we do have our account manager.
Unluckily on that side I felt a lack of technical understanding that woudl not allow me to get my point over correctly.

So let me maybe rephrase my question: does this sdk offer a way to do provide native device ids instead of the generated web_uuid?

[uerceg]

At this moment, it doesn't. Only identifier which Web SDK knows about is our randomly generated UUID string (web_uuid) and that's pretty much it. SDK is not trying to generate or build any other kind of identifier. If you are interested in Web SDK using some identifiers for your Android or iOS users, in theory you would need to make sure to pass them to web world on your own and find a strategy how to have them in Web SDK traffic so that you can later match that with your native apps traffic (callback parameters might be one way where you can attach native identifiers to callbacks which you set to be fired on each session/event and then maybe later in your BI system handle mappings).

But on the other hand, maybe counter question - have you maybe considered using web bridges which we offer for native iOS and Android apps which offer possibility to use SDK inside of your web app which is being loaded inside of web views in native iOS / Android app and pretty much forward everything which happens in web part to native SDK which performs all the tracking? In this way you would have all the traffic generated from web page being tied to mobile device which it was made on. Of course, not sure if you have native apps for this setup, but in case you do, might be a thing to consider.

[MattAndDev]

in theory you would need to make sure to pass them to web world on your own and find a strategy how to have them in Web SDK traffic so that you can later match that with your native apps traffic

We do this already (and have been doing it for a while). Actually your SDK at version 4.1 was allowing for this behaviour too.

not sure if you have native apps for this setup

Unluckily web bridges only work in very specific scenarios, depending on the technology used to serve web apps in a native wrapper that feature will not be usable, either to for security reasons (trusted web activities) or for particular web view implementation (some legacy cordova stuff).

TL;DR;
Cross-app tracking actually works, as we have it working.
It would just be nice to have it either as feat of this SDK or documented somewhere else, so we don't need to hack ourselves around it.

Thanks!