Identifiers on AAM

[franciscor54562]

I've been reading this article Index of IDs in Audience Manager and I have some doubts about how a device is identified in an APP within AAM.

When someone is browsing the web the main identifier is demdex cookie where AAM UUID is storaged

What is the main identifier of a device in an APP?

Thank you all

[Andrey_Osadchuk]

I think the answer is in this KB article >> Visitor Tracking Between an App and Mobile Web

Visitor IDs in apps

[shweta_singh]

Hi there,

Mobile App users can be identified using DAID.

DAID is the Device Advertiser ID: this is a device ID that is provided by the device manufacturer. This is usually related to mobile IDs. 2 such DAIDs are

• IDFA: these are device IDs for iOS devices. All these IDs are name-spaced in AAM under the 20915 DataSource.
• GAID: these are device IDs for Android devices. All these IDs are name-spaced in AAM under the 20914 DataSource.

In some way, DAIDs are similar with AAM_IDs(UUID) in the sense that a certain device will expose the same DAID for all the customers (all the apps) that are running on that device. If available, the app must send the DAID to AAM as a declared ID. When such an ID is being received, AAM will generate an AAM_ID based on the received DAID and will keep a link between this DAID and the AAM_ID. Any profile data will be associated with the AAM ID that was generated out of the DAID.

Regards,

Shweta

[franciscor54562]

Hi there,

Thank you for your answer!

Please could you clarify me following point?  Is DAID only used for advertising purposes or is it used to identify the device for instance to personalizing an experience through an A/B Testing tool as well?

Im really confused because I know AAM UUID is assigned by demdex servers to a browser, and it stays there unless user deletes browser cookie. Marketing Cloud ID gets generated from AAM UUID and the Partner ID of that AAM account but for Mobile devices how is generated this AAM UUID? Is DAID the main key that is share with destination for sync?

[franciscor54562]

Thank you for your answer!

What do you think about shweta_singh's response?

[shweta_singh · Accepted solution]

Hi franciscor54562584 ,

DAIDs are used to identify mobile devices and they are different from audience manager UUIDs. In case of mobile implementation,we need to explicitly implement device Id sync in order to associate aam UUID with DAID(IDFA/GAID).E.g.

Device ID sync (IDFA ID) is done using the “setAdvertisingIdentifier” method outlined here:

Syntax:

+ (void) setAdvertisingIdentifier:(NSString *)identifier;

Example:

NSString *idfa = [[[ASIdentifierManager sharedManager] advertisingIdentifier] UUIDString];

      [ADBMobile setAdvertisingIdentifier:idfa];

Once we have successful device Id sync implemented,we have an associated UUID with a device ID.

In case of sending data to a destination,when it comes to mobile data we have mobile destinations specifically setup to send that data and data usually sent is DAIDs.

Regards,

Shweta