Documentation Updates 2019
A list of new or revised documentation released in 2019. Includes minor updates to the Audience Manager documentation that might not be covered in the Experience Cloud release notes.
See the Experience Cloud Release Notes for changes to Audience Manager and other Experience Cloud solutions. See the Previous Years section for older release notes.
We've released a series of enhancements for Profile Merge Rules:
We've added support for HTTP Strict-Transport-Security, a web security policy that protects against cookie hijacking and protocol downgrade attacks.
We updated the frequency capping examples in the article and added examples for how recency works.
We added tutorial videos to multiple pages in the Audience Manager documentation.
People-Based Destinations is a paid Audience Manager add-on that helps you activate first-party audience segments across people-based environments, like Facebook, using hashed identifiers, such as email addresses.
We're migrating Twitter destinations to a self-service configuration model. This article explains what you need to do for existing Twitter integrations to continue working after the migration.
We added a new example, Case 3, where we detail how billing works for segments with activation and modeling use cases.
There are no major documentation updates to announce for July.
We are in the process of migrating all our APIs from the product documentation into Swagger API. The latest two API we've migrated are:
We have improved the documentation around second-party data sharing by using private data feeds. See the new section, How to set up the Sharing Relationship between Data Provider and Data Buyer.
We introduced a new control in the workflow to create or edit a cross-device data source, Data Retention for inactive Customer IDs . You can now set the data retention period for inactive Customer IDs, determining how long Audience Manager keeps Customer IDs in our database after they were last seen on the Audience Manager platform.
We have updated the way Audience Manager treats the algorithmic models limit. Audience Manager now only counts active algorithmic models against the limit.
This page lists custom integrations between Audience Manager and data partners.
Oracle Data Cloud - Audience Manager ingests cookie and mobile ID data from the Oracle Data Cloud for Audience Marketplace via inbound data files. The custom integration specifications described in this page refer only to inbound data files that contain mobile IDs (IDFA and Android Device IDs).
Your company may desire to obfuscate IP address in many countries due to global privacy regulations. Audience Manager allows you to obfuscate visitor IP addresses on a global or country-by-country basis.
This page illustrates the process of creating Facebook Website Custom Audiences (WCA) pixels for the purposes of sending web-based Audience Manager audience segments to Facebook, for online ad targeting with improved transparency.
An important aspect in the privacy obligations you have towards your users is the acquisition and conveyance of user choices over how their personal data may be used (i.e., “purposes”) and by whom (i.e., “companies”). Adobe provides you with the means to manage and communicate your users' privacy choices through the Opt-in functionality and through IAB Transparency and Consent Framework (TCF) support.
This article describes the Audience Manager use cases that support the IAB TCF and how to implement IAB TCF support in Audience Manager.
Global data sources are accessible by all Audience Manager customers and contain device advertising IDs generated by device manufacturers such as Apple, Samsung, Microsoft, Roku, and Android device manufacturers. These IDs are made available by manufacturers for advertising purposes. You can use global data sources to synchronize device IDs and import or export data keyed off of those mappings. Audience Manager validates the device advertising IDs (DAID) imported by customers, based on their format, to ensure they match the standard format outlined by device manufacturers.
We have improved segmentation, reporting, and exporting of segments by limiting the number of cross-device ID mappings associated to a device ID. The newly imposed limits help us mitigate the impact that incorrect integrations and inaccurate data sets may have on ingestion and downstream processing.
The new limits are:
With Trait Recommendations, when you build or edit a segment in Segment Builder , you get recommendations on additional traits you can include, that are similar to the traits in the segment rule. Add the recommended traits to your segment to increase your target audience.
With the upgrade to a new version of Tableau , we have changed the data visualization method for overlap reports. See the screenshot in the Trait-to-Trait Overlap Report.
With the upgrade to a new version of Tableau , we have changed the data visualization method for overlap reports. See the screenshot in the Segment-to-Trait Overlap Report.
With the upgrade to a new version of Tableau , we have changed the data visualization method for overlap reports. See the screenshot in the Segment-to-Segment Overlap Report.