Documentation Updates 2019 documentation-updates

Topic

Description

The California Consumer Privacy Act (CCPA), going into effect on January 1st, 2020, will provide California residents new rights regarding their personal information and will impose data protection responsibilities on certain entities that conduct business in California.

Audience Manager helps you comply with your obligations under privacy regulations, through privacy tools like the Adobe Experience Platform Privacy Service for data access and delete requests.

We have updated the current opt-out management process to include opting out of any declared ID (e.g. CRM ID). In case of opt-out by declared ID, the declared ID and the last linked device will be opted out of Audience Manager data collection. Opt-out requests now also send unsegment requests to destination partners who support this feature, both in batch and real time.

Additionally, we’ve redesigned our Data Security, Data Privacy, and Data Governance documentation, to make it easier for you to find the information required to comply with the aforementioned regulations.

Topic

Description

With Trait Recommendations, when you build or edit a segment in Segment Builder, you now get recommendations on additional traits that you can include, from Audience Marketplace data feeds that you are not subscribed to. Add the recommended traits to your segment to increase your target audience.
Additionally, we’ve redesigned the Marketplace page to make it easier for you to find similar traits and filter data feeds.

We released a new version of the Bulk Management worksheet that works on MacOS and Microsoft Windows operating systems and supports Experience Cloud login.

We’ve released a series of enhancements for Profile Merge Rules:

• Segment evaluation is now supported in batch, for up to 100 devices.
• We’ve improved the reporting accuracy for trait and segment populations.
• We’ve improved the accuracy of batch files generated using cross-device IDs.
• We’ve updates the documentation with more detailed use cases for each rule. See General Use Cases for Profile Merge Rules, External Device Graph Use Cases, and Profile Link Device Graph Use Cases.

Topic

Description

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.

• Segment Builder
• Segment-level Reporting in Audience Marketplace
• Audience Identity Reporting in the Trait Summary view
• Audience Identity Reporting in the Segment Summary view
• How to Create Conversion Traits
• Trait Recommendations

We added tutorial videos to multiple pages in the Audience Manager documentation.

Topic

Description

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.

Topic

Description

The destinations landing page has a new look. Read this page for information about the new layout.

Topic

Description

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:

• Algorithmic Models API
• Derived Signals API

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).

Topic

Description

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.

Topic

Description

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:

• 100 device IDs per cross-device ID
• 10 cross-device IDs per device ID
• 1000 device IDs to 1 device ID

Topic

Description

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.

Topic

Description

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.