Identifying your mobile app visitors

To identify mobile app visitors, CDP relies on the data sent through the DW Tracker API. The WebTag library uses the DW Tracker API. However, Acquia doesn’t recommend you to use JavaScript libraries, such as the Webtag library, within mobile apps. Using JavaScript limits access to certain inbuilt OS functionalities and invoking a JavaScript engine impacts performance. Thus, visitor’s interaction with your mobile app is hampered.

Mobile app implementation

  1. Share OS specific credentials to CDP. You must use separate authentication credentials for iOS and Android.
  2. Send the following mobile app parameters to CDP. These are the parameters that you want to track throughout your visitor’s interaction with your app.
    • UserClient: Tracks the interface used to access the website or mobile app. The expectetd values are A or B.
    • DeviceType: Tracks the type of device that visitors use to access your mobile app. The expectetd values are MOBILE or TABLET.
    • OperatingSystem: Tracks the operating system of the visitor’s mobile device. The expectetd values are ANDROID or IOS.
  3. Send the following details to CDP:
    • Customer.MobileAdvertisingId: This is the unique advertising identifier for the customer’s mobile device. For example, iOS IDFA or Android’s Google Advertising Id.
    • Customer.MobileDeviceId: This is the unique identifier for the customer’s mobile device. For example, iOS IDFV or Android Device Id.

Next Steps - List of events that CDP tracks

After understanding how to pass your visitor’s identification to CDP to tie them to existing contacts, you can proceed to the next article to review the mobile app events that CDP tracks: List of tracked events.