When existing users access your app, they can do so by directly opening the app (e.g. by selecting the app's icon from their home screen) or by clicking on a so-called deeplink which opens the app and brings the user to a particular location within the app.
If you use deeplinks to bring users back into your app (e.g. in email campaigns, on your website, in a companion app, etc.), it can be useful to track when users arrive in the app via a deep link. To achieve this, we recommend setting up an 'App Launch' Event which is activated when the app is launched and then assigning Even Attributes to that Event which record the context in which the app was opened. For example, an Attribute called 'Source' could take values of: Direct, Deep Link, or Push. Additional Attributes could capture additional details.
To achieve this, your developers should configure the app to appropriately handle URI parameters and then use those to assign Event Attribute values. For example, the workflow would work like this:
A traditional deeplink typically looks something like
myapp://homepage. In this case, you would append referrer information, e.g.
source=deeplink so that the final deeplink looks like
When users click the deeplink, your app should be instrumented to collect the referrer information, i.e.
When the app is opened, this
source=deeplink information should be communicated to Localytics either as an Event Attribute or a Custom Dimension. For more on Event Attributes and Custom Dimensions, see Data Types in our User Guide.
To illustrate how this will be reportable in Localytics, the screenshot below shows an Event called "App Launch" with an Event Attribute called "Mechanism". The app has been instrumented as described above to communicate how the app was opened - either directly, via an opened push message, or via a deeplink: