Mobile SDK tracking FAQ

Is it possible to track an uninstall event if a user has deleted the app?

No, it is not possible to track any events if a user has uninstalled the app because SDK is not active during the uninstall.

If customer profiles identified with a cookie in mobile browser and customer profiles identified with cookie in mobile app will be merged?

Only if a user is also identified with the same hard or soft id both in mobile app and on a web page. A common value of id is a prerequisite. The same cookie will not be generated in both browser/app and must be synced between the sdk and a browser.

Is it possible to identify a user in a mobile app based on a cookie stored in a mobile browser?

It is generally not possible for a mobile app on either Android or iOS to directly access cookies stored in the mobile browser. This is due to security and privacy measures implemented by the operating systems to prevent unauthorised access to sensitive data. Cookies are typically managed at the browser level and are isolated from the app's storage and data. This segregation helps to maintain the security and privacy of the user's information.

The only exception is mobile app browser view, you can embed a web view within your mobile app, which essentially renders a web page inside the app. In this scenario, the web view can access cookies since it is running within the context of the browser. This cookie can be used by mobile SDK for identification, however it is app developer responsibility to implement tracking of this cookie.

Is timestamp populated to custom events tracked by mobile SDK by default?

No, timestamp value is not recorded for custom events. Developers must ensure that the timestamp attribute is populated in custom events. Otherwise timestamp will be assigned to events by the Engagement Platform on their arrival. Timestamp is in UNIX format in seconds.

What time is used by mobile SDK for timestamps tracking of system events?

System time provided by OS is used. If local device time is changed, this will affect the timestamp tracking of the system events.

What to do if there are no events tracked from mobile SDK?

The issue is likely in authentication data in configuration of the SDK. Check the following parts of the configuration:

  • The Public API Group used in the mobile SDK configuration has permission for tracking events. This setting is available in the Access management section of the Bloomreach Engagement Project Settings.
  • Check if the API key, API base url and Project token in the SDK configuration are correct. Those setting are available in the Access management section of the Bloomreach Engagement Project Settings.
  • Check if tracked event types are present in data manager, in case they are not present enable Allow tracking of events not defined in the Data manager (can be disabled later) or add those events manually.

I have tracked events from the mobile SDK, but they are tracked with a delay.

Events are tracked to the platform for mobile SDK periodically, depending on flush settings in the SDK config object.