Customer Data Platform (CDP) relies on the data sent through the DW Tracker API to identify mobile app visitors. The WebTag library uses the DW Tracker API. Acquia does not recommend using 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, which hampers a visitor’s interaction with your mobile app.

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 expected values are A or B.
   • DeviceType: Tracks the type of device that visitors use to access your mobile app. The expected values are MOBILE or TABLET.
   • OperatingSystem: Tracks the operating system of the visitor’s mobile device. The expected values are ANDROID or IOS.
3. Send the following details to CDP:
   • Customer.MobileAdvertisingId: The unique advertising identifier for the customer’s mobile device. For example, iOS IDFA or Android’s Google Advertising Id.
   • Customer.MobileDeviceId: 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

Customer Data Platform (CDP) relies on the data sent through the DW Tracker API to identify mobile app visitors. The WebTag library uses the DW Tracker API. Acquia does not recommend using 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, which hampers a visitor’s interaction with your mobile app.

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 expected values are A or B.
   • DeviceType: Tracks the type of device that visitors use to access your mobile app. The expected values are MOBILE or TABLET.
   • OperatingSystem: Tracks the operating system of the visitor’s mobile device. The expected values are ANDROID or IOS.
3. Send the following details to CDP:
   • Customer.MobileAdvertisingId: The unique advertising identifier for the customer’s mobile device. For example, iOS IDFA or Android’s Google Advertising Id.
   • Customer.MobileDeviceId: 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

For more information about the events that CDP tracks, see List of tracked events.