Why are firstlauches in Visit Number 2,3 etc.?

[laetizia_w]

I am having an understanding question do to first launches.

First Launches get triggered when the user firstly opens the app. But what I see in my report is that in visit number 2,3 etc. there are also first launches. How could this happen? I would expect that first launches will only be in visit number 1

[PratheepArunRaj]

Dear Laetizia,

First Launches metric get triggered at the first run after installation or re-installation.

Wondering whether Adobe can identify the Visitor using Device UDID and assign Visit Number as 2,3 etc during re-installation.

Gigazelle​, Can you help?

Thank You

Arun

[laetizia_w]

Could be the case but in our data it doesnt seem like it. When deleting the app and reinstalling the user must be a new visitor plus also when deleting all Data within the app.

[jeff_bloomer]

Anecdotally, this anomaly also appears to happen primarily in Android.  It does not appear the same in iOS for the implementation I have.

[suneeshkachroo]

Can you check with the App ID and the sdk version to check if there was an upgrade of the app and the first launch?

Second would like to check if you have any custom visitor Identification implemented?

[jantzen_b]

Jen Andrews​ - Can you help clarify some of the questions here?

[Jen_Andrews · Accepted solution]

As suneeshkachroo stated, both items I would look at. Ideally in a perfect scenario, yes First Launch, and visit 1 should be the same.

In cases where you are using some sort of potential custom visitor ID implemented, there could be a scenario where the initial First Launch and then after 'authenticating' that there is a new visitor causing a discrepancy.  More investigation into exact implementation would need to be looked at.

As well a couple of additional items, if the user was potentially offline when the lifecycle hit occurred and the app is not offline enabled could be another reason.

[laetizia_w]

Both make sense but either options are the case. This occures only within ios on our side and lifecycle metrics get automatically triggered through ios.

But what if a user opens the app and no other servercall like state or action tracking accured because the app crashed?