Mobile App - AEP SDK - Implementation of Acquisition & deeplinking & testing

[padmaa17619878]

Hi there,

We are trying to implement mobile marketing features such as acquisition and deeplinking. Need some clarification on the below:

1. are these features still available in AA (prime license)? 

2.  as per this article, it can be achieved through very manual way - is it still valid? any limitations?

Basically, Does Mobile (AEP) AA contain in-built features for marketing features? or do we need to rely on third party plug-ins?

[emdobrin · Accepted solution]

Hi @padmaa17619878 ,

The Adobe Analytics - Mobile Services extension provides the functionality you are looking for. For more details, see https://aep-sdks.gitbook.io/docs/using-mobile-extensions/adobe-analytics-mobile-services

For acquisition tracking you also need to configure the Launch hit delay in the Analytics extension so that it waits for the acquisition information before processing the launch hit: https://aep-sdks.gitbook.io/docs/using-mobile-extensions/adobe-analytics#launch-hit-delay

Thank you,

Emilia Dobrin

Adobe Experience Cloud

[padmaa17619878]

Thanks Emilia for the quick response, yes mobile service extn is already configured and launch it delay is set to 5. Code & config already have related initialization.

1. In adobe launch, most of times, i see this error, what could be the reason? 

2.How do we check acquisition /deeplinking parameters in test environment, ie, when app is not in app store. still these steps valid?

3. Is it necessary to have acquisitiontimeout is lesser than launchhitdelay?  can help to validate below settings? 

"analytics.launchHitDelay": 5,

"mobile.acquisitionTimeout": 30,

"lifecycle.sessionTimeout": 300,

[emdobrin]

Hi @padmaa17619878,

1. I am not sure what went wrong in the Adobe Analytics extension. Can you provide more details on what configuration you are using? Do you see any error when you open the developer console in your browser? Any specific browser/browser version where you are seeing this error? 

2. Yes, those steps should still work to validate the workflow on your local device.

3. We recommend a value of ~ 5 seconds for the mobile.acquisitionTimeout. This timeout is used as the network request timeout when communicating with the Adobe Mobile Services acquisition server to retrieve the referrer information. The analytics.launchHitDelay is the timeout for Adobe Analytics extension to hold onto the Launch hit before the referrer information is received. You may want to have the launchHitDelay equal or greater to the acquisitionTimeout to allow for the referrer info to be retrieved before the Lifecycle hit leaves the device, but there is no restriction there.

Emilia Dobrin

Adobe Experience Cloud

[padmaa17619878]

Thanks Emilia, it really helped