Closed prookiee closed 2 months ago
Hi @prookiee,
Steps you said you did sound good. However there are still some steps down the road:
deep_link
parameter inside of it?When you run this test, test install that you track should be attributed to click on your test URL. When SDK's attribution callback is being triggered, do you see that attribution data from there (tracker token, tracker name at least) belong to things from your URL?
Yeah, it's ending up being organic (meaning the install you're making is not getting attributed to your click). At this point, I am not sure why, client support teams who are able to debug this are not the ones who are replying in GitHub issues.
Only thing that comes to my mind which you can maybe try is to check SDK verbose logs, see what's your test device Google Advertising ID (called gps_adid
in the logs that our SDK prints) and then just append it to the test URL (&gps_adid=XXXXXX). This should trigger device ID matching on our end and if everything else during the test has been done correctly, hopefully install should get attributed to the click you make on that URL.
Yeah, I hava solved this problem by replacing the branded domain xxx.go.link with app.adjust.com. And now I can recieve deferred deeplink information normaly.
Thank you for your help.
I believe that branded links should be no different from app.adjust.com ones when it comes to this case, but I personally am not sure what might have caused this behavior that you've seen. If you are interested in finding out what has happened and to continue to use branded links, feel free to contact your dedicated account manager if you have one, or simply fire an email to support@adjust.com and reference this GitHub issue.
Nonetheless, glad to hear that it worked. Cheers!
SDK version 5.0 Deeplink work's fine. But when I test Deferred deeplink, it doesn't word, I can't get any callback from setOnDeferredDeeplinkResponseListener .
I removed APP from device and forgot device from adjust console ,but deferred deeplink still doesn't work.