Delayed onAttributionChanged callback after upgrading to Adjust 4.38.3

[zxq126]

After upgrading the Adjust SDK from 4.33.0 to 4.38.3, I noticed a significant increase in the time between calling Adjust.onResume and receiving the first onAttributionChanged callback. Based on tracking data, the percentage of users receiving the callback within 20 seconds dropped by approximately 9%.

Steps to Reproduce Using Adjust version 4.33.0, track the time between calling Adjust.onResume and receiving the first onAttributionChanged callback for new users. Upgrade to Adjust 4.38.3 and repeat the tracking. Compare the results, noting that the callback time has increased after the upgrade.

Expected Behavior The callback time should remain consistent with the previous version or not exhibit a significant delay.

Actual Behavior After upgrading to Adjust 4.38.3, the percentage of users receiving the callback within 20 seconds decreased by approximately 9%.

Environment Information Adjust SDK version: 4.38.3 Android project: no changes to Adjust API calls other than updating the SDK version Dependency: com.android.installreferrer:installreferrer:2.2

Code Snippet

config.setOnAttributionChangedListener(new OnAttributionChangedListener() {
    @Override
    public void onAttributionChanged(AdjustAttribution attribution) {
        // Attribution callback logic
    }
});

Additional Notes I understand that Adjust.onPause could potentially influence this timing. However, we have not modified the activity interaction flow during this Adjust version update, so we believe this API can be ruled out as the cause.

Analysis Please help verify whether this behavior is expected and assist in identifying potential causes for the delay. Could this issue impact attribution timing or other functionality?

[shashanksu]

Hi @zxq126 ,

Thank you for reaching out and for your patience.

In version 4.35.0, we have added setFinalAttributionEnabled(boolean) method to AdjustConfig to indicate if only final attribution is needed in attribution callback. By any chance did you enabled this?

Other than this, there's no related changes in the SDK behaviour. Also, to rule out any changes beyond SDK, please get in touch with your dedicated account manager if you have one, otherwise write an email to [email protected].

Thanks

[shashanksu]

Hi @zxq126 ,

I hope your issue has been resolved, as we haven’t received any further updates. I’ll go ahead and close this ticket for now. If you still have concerns or need assistance, please feel free to reopen it at any time.

Thanks