Welcome to the Adobe Audience Manager Community! Connect with peers to ask questions, share best practices, explore release updates, and contribute ideas that shape the future of Adobe Audience Manager.
Récent
Currently AAM - attempts to set a 3rd party cookie for mobile devices. Most mobile devices including all iOS reject 3rd party cookies. Adobe offer the current work arounds to this issues :- 1) Client can set their own ID for those using mobile devices (requires authentication). For many websites including publishers this solution does not scale. 2) Work with a thrid party e.g Tapad or Drawbridge to establish links from your AAM desktop traffic to mobile devices mapped in their data set and target them via their services. For publishers neither solution works well. Publishers have up to 50%+ of their web traffic on mobile devices and they need to be able to identify those users across multiple domains and target those users within that session on their 1st party media. I believe this is only possible if Adobe deploy their own finger printing solution to achieve this. Currently Adobe are behind compared to other DMP's and mobile detection and targeting in this area.
The primary means of controlling the data modelling function is via data sources label for traits. However this is quite inflexible when creating multiple models that should run against different sub sets's of data since a trait can only belong to 1 data source.
Vous avez déjà un compte d'utilisateur ? Connexion
Pas encore de compte ? Créer un compte
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.