Do the SDKs capture a device ID?

The SDKs store a TID against the application in which the SDK has been configured. This TID is linked to any customer keys the app sends to MXO .

If a device ID is available in the app, you can configure MXO to use this as an identifier. Caution should be exercised, however, before using device ID as a key.

Device identifiers are very likely to be determined using probabilistic, rather than deterministic techniques. This means that there is no unique device ID freely available to identify a user in the same way as a known identifier.

We recommend capturing advertising IDs and other identifiers, determined using probabilistic techniques, as simple attributes in MXO and linking those back to a user as an identifier in your CRM system rather than directly in MXO .

Use deterministic identifiers as customer keys in MXO , only to avoid creating multiple instances of the same customer.

How is lat/long and city/country information populated in the Device Data Adapter?

Latitude/longitude and city/country information is populated in the Device Data Adapter based on the device connecting to MXO . MXO resolves the device IP based on the connection made and maps this to the user's IP location.

Granular location information can be sent programmatically to MXO using the SDKs updateLocation method:

• iOS
• Android