Tracking App ID in MobileSDK

[user79428]

Hi, 

We migrated our iOS app to the MobileSDK recently and experienced a drop in iOS visits in Adobe Analytics. We believe the drop is caused by a bug with App Id not being captured correctly in the Lifecycle Metrics when the app launches. We use Lifecycle metrics in our Mobile Launch property and in the iOS code.

How do we make sure that App Id is captured on every visit in the MobileSDK?

Is there any other reason that the migration to the MobileSDK could trigger a drop in iOS visits specifically?

Thank you if you have any insights!

[igupta]

Hey @user79428 ,

We had a similar issue in past. That was because there was Environment ID mismatch between the latest app version and mobilesdk code. Couple of things to check here -

1. Do you have some data coming from the latest app version of is it none at all? You can look at the app version visits to verify this.

2. If you have some data, then you would need to verify what all data points are missing and then would need to debug from app if it is sending correct data. Also, you would need to check processing rules for context variables if anything is amiss in the configuration.

Do you have a debugging set up such as AEP Assurance? If not, you may need to use MITM proxy tools like Fiddler Everywhere, Charles debugger to check the incoming data from your latest app release.

Best,

Isha

[Jennifer_Dungan]

To check if your App ID is being set properly, in AEP Assurance, it will be listed in the "Request Details"

I agree with an in-depth testing session... AEP Assurance will make this much easier, but if you don't have it, then using Proxy Testing might be your only option... you can also use Browser Stack (if your company has an account) for testing without a proxy... most of the devices have a request log you can monitor.