Documentation Updates 2018
A list of new or revised documentation released in 2018 and previous years. 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.
With Trait Exclusions, you can remove traits from modeling. This way, extremely common traits such as site visitor traits don't bias your model. This new capability also enables you to remove traits from third-party data feeds.
We updated the documentation to include the new search and filtering capabilities for test groups. See the Search and Filter Test Groups section.
See Segment Mapping Rules for more information on the set of rules that IRIS follows when sending segments to destinations.
We added definitions and examples for all the metrics in the General Reports.
We made some updates to clarify the difference between customer-level and segment-level metrics.
Starting with version 8.0, DIL has a hard dependency on the Experience Cloud ID Service , version 3.3 or higher.
Modified Getting and Implementing DIL Code to account for the fact that Adobe Launch is the preferred code deployment tool in the Experience Cloud .
The following elements are deprecated starting with DIL 8.0, released August 2018:
The Audience Lab overview page now includes a search field, allowing you to easily find any of your test groups.
Instant Cross-Device Suppression is the ability to suppress users across multiple devices connected to them when a particular experience occurs on any of these devices. Use the Instant Cross-Device Suppression capability to deliver a consistent experience across devices to your users. This experience is made possible by the real-time unsegment capabilities in Audience Manager.
Unsegmentation describes processes that disqualify and remove device profiles from segments. Your ability to remove a device profile from a segment depends on the device option used to create a Profile Merge Rule.
Answers to common Profile Merge Rules and device graph questions.
|Audience Optimization for Publishers|
Audience Optimization for Publishers can help you identify potential performance opportunities for Audience Manager segments on your owned and operated content. These reports combine log-level campaign performance data with Audience Manager metrics to inform audience optimizations and monetization opportunities.
Before Audience Manager can enable Audience Optimization for Publishers, you must ensure that all prerequisites outlined in this article are met. Contact Customer Care after checking off all prerequisites.
|DCS API Methods|
GET requests have a maximum content length of 8K. You can read more about GET and POST API methods by visiting this page.
In June 2018, Adobe is deprecating support for the TLS 1.0 protocol. Adobe Audience Manager functionality will not work for your end users that use browsers which only support TLS 1.0. We have collected for you a list of browsers, versions, and TLS support.
Before reading the Audience Manager specifics, we advise you go through the Experience Cloud material for the European General Data Protection Regulation (GDPR), linked from this page.
This document covers the technicalities related to the General Data Protection Regulation (GDPR) for Audience Manager and shows you how to submit GDPR requests to Audience Manager.
This material contains some of the most common questions asked by our customers and partners related to the European General Data Protection Regulation (GDPR), and how Adobe Audience Manager, as a Data Processor, addresses various GDPR requirements.
In order to help our customers automate GDPR requests, Audience Manager notifies our activation partners about deletion requests from Data Subjects by sending them unsegment (or remove segment) information.
Beginning March 29, 2018, all Audience Manager customers who are on Accelerated Mobile Pages (AMP) will need to leverage the server-side integration when sending audiences to Google’s DoubleClick for Publishers (DFP).
Added a new section to the Trait Qualification Reference, describing the differences between the Unique Trait Realizations and the Total Trait Population.
With the d_tdpid and d_tdpid_ic parameters, you can pass a data source for trait evaluation. Only traits from that data source will be evaluated.
You can use cross-account bucket permissions in Amazon S3 for delivering outbound data files, if you don't want to share Amazon S3 access keys and secret keys.
Added error 198: Requests from this country are blocked by partner
Your users will start qualifying for a rule-based trait approximately 4 hours after you create the trait in the UI. Read the document for more information on trait qualification.
We added a limit of 50,000 on the number of Derived Signals you can use.