- Audience Manager tutorials
- Intro to Audience Manager
- Industry news and trends
- Setup and admin
- Web implementation
- Integrating offline data
- Mobile implementation
- Audience Marketplace
- Build and manage audiences
- Data explorer
- Use the Signals Dashboard to quickly view top available signals
- Use Data Explorer to search for used and unused key/value pairs
- Save searches in Data Explorer for convenient re-use
- Use Data Explorer to create retroactive traits and segments
- Use Data Explorer to validate trait creation for on-boarded data
- Use Data Explorer to work with signals coming from Adobe Analytics
- Traits and segments
- Plan trait creation from Analytics data
- Create a trait taxonomy
- Create a rule-based trait
- Create onboarded traits
- Create a conversion trait
- Choose a data source when creating traits
- Configure trait expiration with the Time to Live (TTL) setting
- Use code view to create and edit traits
- Introduction to Bulk Management (BAAAM)
- Create and manage traits in bulk with BAAAM
- The basics of creating segments
- Create a segment taxonomy
- Practical segment definition and creation
- Create segments from multiple data sources
- Choose a data source when creating a segment
- Enhance your segments with trait recommendations
- Trait recommendation enhancements in segmentation
- Use Recency and Frequency in segments
- Use code view when building segments
- Import segments from Adobe Analytics into Audience Manager
- Build a segment to suppress ads to customers
- Map Audience Manager segments to destinations
- Map segments to a device-based destination
- Understand numbers in the Trait graph
- Understand numbers in the Segment graph
- Customer tips - trait and segment best practices
- Algorithmic models
- Profile merge
- Profile Merge Rules
- Overview of Profile Merge Rules
- Profile merge rule examples and use cases
- Choose the right profile merge rule
- Create and use simple Profile Merge Rules
- Use Profile Merge Rules to personalize in an authenticated state
- Use Profile Merge Rules for device extension and increased reach
- Overview of Profile Merge Rule enhancements
- Profile Merge Rule enhancements - prerequisites
- How Profile Merge Rule enhancements impact segmentation, activation, and reporting
- Interpret audience identity reporting
- Understand cross-device metrics in Audience Manager
- Customer tips - getting the most out of Profile Merge Rules
- Data explorer
- Data activation
- Destinations basics
- Audience Lab
- People-based Destinations
- People-based Destinations videos and tutorials
- People-based Destinations data flow
- Create a data source for People-based Destinations
- Understand Hashed PII data ingestion for People-based Destinations
- Ingest Hashed PII for People-based Destinations
- Use setCustomerIDs() to ingest and hash PII as a declared ID
- Configure Profile Merge Rules for People-based Destinations
- Create segments for People-based Destinations
- Create and Configure People-based Destinations
- Understand and configure the LinkedIn People-based destination
- Understand and configure the Google customer-match People-based destination
- Reports
- Other integrations
- Integrate with Real-time Customer Data Platform
- Ingest data using the Adobe Audience Manager data connector
- Understand first-party data ingestion in Real-time CDP
- Understand Web data ingestion in Real-time CDP
- Understand schemas and XDM in Real-time CDP
- Understand traits in Real-time CDP
- Understand signals in Real-time CDP
- Understand segments in Real-time CDP
- Understand destinations in Real-time CDP
- Understand access control in Real-time CDP
- Understand data governance in Real-time CDP
- Integrating with Ad Cloud
- Integrate with Real-time Customer Data Platform
- API
Global device ID validation
Device Advertising Identifiers (i.e. iDFA, GAID, Roku ID) have formatting standards that must be met in order to be usable in the digital advertising ecosystem. Today, customers and partners can upload IDs to our Global data sources in any format without being notified of whether the ID is properly formatted. This feature will introduce validation of device IDs sent to the Global data sources for proper formatting and will provide error messaging when IDs are incorrectly formatted. We will support validation for iDFA, Google Advertising and Roku IDs at launch.
Overview of format standards
The following are the global Device Advertising ID pools that are currently recognized and supported by AAM. These are implemented as shared Data Sources that can be used by any customer or data partner that works with data tied to users of these platforms.
| Platform | AAM Data Source ID | ID Format | AAM PID | Notes |
| Google Android (GAID) | 20914 | 32 hex numbers, generally presented as 8-4-4-4-12example, 97987bca-ae59-4c7d-94ba-ee4f19ab8c21 |
1352 | This ID must be collected in a raw/unhashed/unaltered form Reference - https://play.google.com/about/monetization-ads/ads/ad-id/ |
| Apple iOS (IDFA) | 20915 | 32 hex numbers, generally presented as 8-4-4-4-12 example, 6D92078A-8246-4BA4-AE5B-76104861E7DC |
3560 | This ID must be collected in a raw/unhashed/unaltered form Reference - https://support.apple.com/en-us/HT205223 |
| Roku (RIDA) | 121963 | 32 hex numbers, generally presented as 8-4-4-4-12 example, fcb2a29c-315a-5e6b-bcfd-d889ba19aada | 11536 | This ID must be collected in a raw/unhashed/unaltered form Reference - https://sdkdocs.roku.com/display/sdkdoc/Roku+Advertising+Framework |
| Microsoft Advertising ID (MAID) | 389146 | Alpha numeric string | 14593 | This ID must be collected in a raw/unhashed/unaltered form Reference - https://docs.microsoft.com/en-us/uwp/api/windows.system.userprofile.advertisingmanager.advertisingid https://msdn.microsoft.com/en-us/library/windows/apps/windows.system.userprofile.advertisingmanager.advertisingid.aspx |
| Samsung DUID | 404660 | Alpha numeric string example, 7XCBNROQJQPYW | 15950 | This ID must be collected in a raw/unhashed/unaltered form Reference - https://developer.samsung.com/tv/develop/api-references/samsung-product-api-references/productinfo-api |
Setting an Advertising Identifier in the App
Setting the advertiser ID in the app is really a two step process, first retrieving the advertiser ID, and then sending it to the Experience Cloud. Links are found below for performing these steps.
- Retrieve the ID
- Send it into the Experience Cloud using the setAdvertisingIdentifier method in the SDK
- Information for using
setAdvertisingIdentifieris in the documentation for both iOS and Android.
- Information for using
// iOS (Swift) example for using setAdvertisingIdentifier:
ACPCore.setAdvertisingIdentifier([AdvertisingId]) // ...where [AdvertisingId] is replaced by the actual advertising ID
DCS Error Messaging for Incorrect IDs
When an incorrect Global Device ID (IDFA, GAID, etc) is submitted in realtime to Audience Manager, an error code will be returned on the hit. Following is an example of an error returned because the ID is sent in as an Apple IDFA, which should only contain upper case letters, and yet there is a lower case ‘x’ in the ID.
Please see the documentation for the list of error codes.
Onboarding Global Device IDs
In addition to realtime submission of Global Device IDs, you are also able to “onboard” (upload) data against the IDs as well. This process is the same as when you are onboarding data against your customer IDs (typically via key/value pairs), but you would simply use the proper Data Source IDs, so that the data is assigned to the global device ID. Documentation about the onboarding process can be found in the documentation. Just remember to use the global data source ID, depending on the platform that you are using.
If incorrect Global Device IDs are submitted through the onboarding process, the errors will show in the Onboarding Status Report.
Following is a sample of an error that would come through that report:
Resources
Adobe Account
