Show Menu
TOPICS×

Mobile app acquisition

Acquisition links with unique tracking codes can be generated in Adobe Mobile services. When a user downloads and runs an app from the App store after clicking on the generated link, the SDK automatically collects and sends the acquisition data to Adobe Mobile services.

New Adobe Experience Platform Mobile SDK Release

Looking for information and documentation related to the Adobe Experience Platform Mobile SDK? Click here for our latest documentation.
As of September 2018, we released a new, major version of the SDK. These new Adobe Experience Platform Mobile SDKs are configurable through Experience Platform Launch .
To use Acquisition, you must have SDK version 4.1 or later.
Acquisition links must be created in Adobe Mobile services. For more information, see Acquisition .
In SDK versions 4.13.1 and later :
If you cannot use the acquisition links that are created in Adobe Mobile Services, the acquisition data can still be collected and sent by the SDK by using Google Play Acquisition.
To collect acquisition data from a standard Google Play Acquisition campaign:
  • Use the standard Google Play Store acquisition method.
    Custom acquisition data can be used with the standard Google Play Acquisition key value pairs.
  • When the user downloads and runs an app as the result of a Google Play store acquisition, the data from the referrer will be collected and sent to Adobe Mobile Services.
    • The data is stored and available in the AdobeDataCallback instance that was registered earlier with the SDK.
      For more information, see Configuration Methods .
    • The MobileDataEvent.MOBILE_EVENT_ACQUISITION_INSTALL or the MobileDataEvent.MOBILE_EVENT_ACQUISITION_LAUNCH event type are used.
    • Custom keys that were part of the acquisition data from Google Play will be name-spaced with " a.acquisition.custom. "
If you are using the Acquisition links that were created on Adobe Mobile Services, add custom data to the acquisition link by completing the following tasks:
  1. Prefix an acquisition variable with " adb ".
    When the SDK receives the acquisition data from Adobe Mobile Services (on first launch), that data will be stored and also available in the AdobeDataCallback instance registered earlier with the SDK, as mentioned in Configuration Methods .
  2. The MobileDataEvent.MOBILE_EVENT_ACQUISITION_INSTALL or the MobileDataEvent.MOBILE_EVENT_ACQUISITION_LAUNCH event type will be used.
  3. The custom data keys are prefixed with " a.acquisition.custom. "
If you are sending data to multiple report suites, use the acquisition data from the app that is associated with the first report suite in your list of report suite IDs.
The updates in this section enable the SDK to send acquisition data from an acquisition link.

Tracking mobile acquisition

  1. Add the library [to your project and implement lifecycle.
    For more information, see Add the SDK and Config File to your IntelliJ IDEA or Eclipse Project in Core implementation and lifecycle .
  2. Import the library:
    import com.adobe.mobile.*;
    
    
  3. Implement the BroadcastReceiver for the referrer:
    package com.your.package.name;  // replace with your app package name 
    
    import android.content.BroadcastReceiver; 
    import android.content.Context; 
    import android.content.Intent; 
    
    public class GPBroadcastReceiver extends BroadcastReceiver { 
      @Override 
      public void onReceive(Context c, Intent i) { 
       com.adobe.mobile.Analytics.processReferrer(c, i); 
      } 
    }
    
    
  4. Update AndroidManifest.xml to enable the BroadcastReceiver that was created in the previous step:
    <receiver android:name="com.your.package.name.GPBroadcastReceiver" android:exported="true"> 
     <intent-filter> 
      <action android:name="com.android.vending.INSTALL_REFERRER" /> 
     </intent-filter> 
    </receiver>
    
    
  5. Verify that the ADBMobileConfig.json file contains the required acquisition settings:
    "acquisition": { 
       "server": "c00.adobe.com", 
       "appid": "0652024f-adcd-49f9-9bd7-2552a4565d2f" 
    }, 
    "analytics": { 
      "referrerTimeout": 5, 
      ...
    
    
    If you are sending data to multiple report suites, use the acquisition settings (acquisition server and appid) from the app that is associated with the first report suite in your list of report suite IDs.
    The acquisition settings are generated by Adobe Mobile services and should not be changed. For more information about how to download a customized ADBMobileConfig.json file with the acquisition settings pre-configured, see Before You Start .
After these settings are enabled, after the initial launch of the app, acquisition data is sent automatically with the initial lifecycle call.
referrerTimeout must be set to a value higher than 0 to enable app acquisition.