Audience Manager source
namespaceCode={VALUE} does not exist. Note: In the back end, namespaceCode is used to refer to identity symbol. To complete your integration, you must:- Create a custom namespace in Identity Service with the specified identity symbol (
VALUE) . - Re-ingest your data.
The ÃÛ¶¹ÊÓƵ Audience Manager source streams first-party data collected in ÃÛ¶¹ÊÓƵ Audience Manager for activation in ÃÛ¶¹ÊÓƵ Experience Platform. The Audience Manager source ingests two types of data to Platform:
- Real-time data: Data captured in real time on Audience Manager’s data collection server. This data is used in Audience Manager to populate rule-based traits and will surface in Platform in the shortest latency time.
- Profile data: Audience Manager uses real-time and onboarded data to derive customer profiles. These profiles are used to populate identity graphs and traits on segment realizations.
The Audience Manager source maps these data types to an Experience Data Model (XDM) schema and then sends them to Platform. Real-time data is sent as XDM ExperienceEvent data, while Profile data are sent as XDM Individual Profile data.
For more information, read the guide on creating an Audience Manager source connection in the UI.
What is Experience Data Model (XDM)?
XDM is a publicly documented specification that provides a standardized framework by which Platform organizes customer experience data.
Adhering to XDM standards allows customer experience data to be uniformly incorporated, making it easier to deliver data and gather information.
For more information about how XDM is used in Experience Platform, read the XDM System overview. To learn more about how XDM schemas are structured between profiles and events are structured, read the basics of schema composition.
XDM schemas examples
Below are examples of the Audience Manager structure mapped to XDM ExperienceEvent and XDM Individual Profile in Platform.
ExperienceEvent - for real-time data and onboarded data
XDM Individual Profile - for profile data
For information on how fields are mapped from Audience Manager to XDM, read the documentation on Audience Manager mapping fields.
Data management on Platform
Datasets
A dataset is a storage and management construct for a collection of data, typically a table, that contains a schema (columns) and fields (rows) and is made available by a data connection. Audience Manager data consists of real-time data, inbound data, and Profile data. To locate your Audience Manager datasets, use the search function in the UI with the provided naming conventions for each type of data.
Audience Manager datasets are disabled for Profile by default and users have the ability to enable or disable datasets based on their use cases. It is not recommended to disable datasets that will be used for segment membership in Profile.
Connections
ÃÛ¶¹ÊÓƵ Audience Manager creates one connection in Catalog: Audience Manager Connection. Catalog is the system of the records for data location and lineage within ÃÛ¶¹ÊÓƵ Experience Platform. A connection is a Catalog object that is a customer-specific instance of connectors. Please read the Catalog Service overview for more information on Catalog, connections, and connectors.
Segment population to Profile impact
Segment population sizes have a direct impact on Profile numbers when you first send an Audience Manager segment to Platform. This means that selecting all segments can potentially cause Profile overages that exceeds your license usage entitlement. Platform also distinguishes new data from historical data for Profile ingestion. A segment with 100 first-party based identities will create 100 profiles. However, if the population of that same segment was raised to 150 and was ingested to Platform, the number of profiles will only increase by 50, as there are only 50 new profiles.
You can also check the profile usage your account has available through the License Usage Dashboard.