Show Menu

Release Notes - May 2018

New features and fixes in the Adobe Experience Cloud.
Subscribe to the Adobe Priority Product Update to be notified via email about upcoming releases. You will receive the notice three to five business days in advance of the release. New information published after the release will be marked with the publication date.

General Data Protection Regulation API

Update Description
May 25, 2018
>[!IMPORTANT] >With GDPR becoming effective 25 May 2018, Adobe will implement automated deletion of files left in FTP accounts managed by Data Connector (previously Genesis) partners. (This does NOT apply to all FTP accounts belonging to Analytics customers.) Currently, data in FTP folders is retained indefinitely, which may put companies at risk of not being GDPR ready. Starting 25 May 2018, Adobe will delete all files on Data Connector Partner-managed FTP servers 30 days after their arrival on the server.
May 24, 2018
New version of the AdobePrivacy.js library
  • Added a new config to make it easier to set the "key" property, which is a data subject ID that is required by the GDPR API .
  • Updated the "retrieveIdentities" and "removeIdentities" APIs to set the "action" property to "access" and "delete" , respectively.
  • Added a new API: "retrieveThenRemoveIdentities" which should be used in cases where you want to submit a GDPR request to access and delete the data. This API will set the action property to ["access", "delete"]
During the week of May 7, 2018, Adobe released product updates to support the General Data Protection Regulation (GDPR). The following information is available to help you understand and implement these enhancements, as well as update any necessary policies and procedures.
Resource Description
Learn what GDPR means to you as an Adobe customer.
Developer documentation for implementing the GDPR API.
The Adobe Privacy JavaScript Library and GDPR.
How to configure Identity Namespaces for GDPR compliance.
Mobile SDK - Android and iOS
GDPR-ready APIs for Controllers. The APIs allow users to retrieve locally stored identities and set opt status flags for data collection and transmission.
Documentation and procedures for the customer privacy administrator or AEM administrator to handle GDPR requests.
What you need to do in Adobe Analytics to support your data subjects' GDPR access and delete rights.
How to submit GDPR requests to Audience Manager , and answers to common questions about how Audience Manager addresses GDPR requirements.
Data Workbench supports GDPR processes to anonymize personal identification information.
How to prevent Adobe tags from firing until consent is acquired.
How developers can use extensions and the rule builder to define opt-in and opt-out solutions.
How to enable customers to delete data in their Target Visitor Profile.
How to use the GDPR request form to access or delete data collected in your use of Adobe Social.
How to complete access and deletion requests permitted under GDPR.
Learn about new functionality in Adobe Campaign for GDPR.
Release notes for the core services interface, including Assets, Feed, Notifications, People, Mobile Services, Launch, and Dynamic Tag Management. Also includes release information for Experience Cloud ID Service (formerly known as Visitor ID service and Visitor API in Analytics, and Marketing Cloud ID service ).

Experience Cloud and Core Services

Experience Cloud Interface

New features and fixes in the Adobe Experience Cloud interface.
Feature Description
New administration landing page
When you sign in to the Experience Cloud and navigate to the Administration page, a new intuitive interface is available to help you quickly access your Experience Cloud solutions and Core Services.
  • Fixed an issue where the image upload failed due to a Scene7 update. (CORE-12746)
  • Made updates to drop support for TLS 1.0 protocol, as mandated by PCI to eliminate security vulnerability. (CORE-7695)


Important Notices for Analytics Administrators

Review the following table for important Analytics notices that may affect data collection, processing, APIs, product end-of-life, and so on.
Notice Date Added or Updated Description
New help for the Analytics user migration
May 10, 2018
We updated the Analytics user ID migration help with information about migrating Enterprise and Federated IDs to the Admin Console.
Upcoming removal of Account Activity Report
May 10, 2018
The Account Activity Report will be replaced by the Server Call Usage feature in the Adobe Analytics Summer Release. The Account Activity Report will be permanently removed on August 9, 2018. To view summary data about report suite traffic after August 9, 2018, use the Server Call Usage feature.
Update Adobe Report Builder due to end of support for TLS 1.0
May 10, 2018
Due to the end of support for TLS 1.0, we recommended that Adobe Report Builder (ARB) users download ARB v5.6.21 prior to September 13, 2018. After that date, prior versions of ARB will not be supported.
Changes to linear allocation models in Calculated Metrics
May 10, 2018
Effective July 19, 2018
On July 19th, Adobe Analytics will revise the way allocation models in calculated metrics are evaluated. As part of this change, calculated metrics that use a non-default allocation model will be migrated to new and improved attribution models.
Marketing Channel Last Touch and Marketing Channel First Touch allocation models will be migrated to new Last Touch and First Touch attribution models respectively. (Marketing Channels are not being deprecated, only the two allocation models that appear in calculated metrics).
Additionally, we will correct the way linear allocation is calculated. If you use calculated metrics with linear allocation models, the reports may change slightly to reflect the new, corrected attribution model.
This change to calculated metrics will be reflected in Analysis Workspace , Reports & Analytics , the Reporting API, Report Builder , and Ad Hoc Analysis.
See the Calculated Metrics documentation for more information about this change.
Anomaly Detection and Contribution Analysis functionality removed from Reports & Analytics
April 10, 2018
Anomaly Detection and Contribution Analysis have been removed from the Reports & Analytics feature set and are now available only via Analysis Workspace .
Adobe Analytics Select and Foundation customers have access only to “daily-granularity” Anomaly Detection in Workspace.
Adobe no longer issuing 3rd-party s_vi cookies for Safari
April 05, 2018
On March 20, 2018, Adobe stopped issuing third-party s_vi cookies for the Safari browser. This change does not impact customers using first-party data collection cookies. This change also removes the visit and visitor inflation experienced by some customers, resulting from Safari ITP.
Update Report Builder before you migrate user IDs to the Admin Console
March 17, 2018
>[!IMPORTANT] >Update your installation of Report Builder to the latest version. This update is a pre-requisite for running the Analytics user ID migration to the Admin Console, beginning in April 2018.
Back-end changes that affect reporting
April 11, 2018
A change to the (back-end) lookup mechanism is going to impact reporting in several ways. Please be aware that these changes went into effect around the end of February, 2018 :
  • Page renaming will no longer be allowed. Going forward, you will need to use classifications to rename pages. Until the May 10, 2018 release, the system will continue to process the renamed pages as they are currently configured. Adobe is asking all customers to migrate to classifications by that date. After the May release, existing renames will no longer be honored and can change, retroactively, without notice.
  • The URL replacement methodology is different. Previously, Adobe Analytics would store (mostly) the first URL associated with each page name each month. Going forward, we will store the most recent URL for each page name.
  • ( Updated April 11, 2018 ) Category reports for roll-ups and current data in [!UICONTROL Reports & Analytics] are no longer provided. Deprecating category roll-up reports in the Web Service API is effective with the May 10, 2018, Adobe Analytics maintenance release.
  • There is no longer any support for page/prop data from before approximately January 2007 (in some cases, 2006). This only impacts pages, props and page events (i.e. custom links, exit links, download links).
    Note: This change does not impact reporting in Analysis Workspace or Data Warehouse.
    If you have data preceding these dates, expect the following:
    • Data will not combine correctly across the pre/post January 2007 boundary.
    • Searches will not work against data before approximately Jan. 2007.
End of Support for TLS 1.0
May 4, 2018
  • Starting July 19, 2018, Adobe Analytics Reporting will no longer support TLS (Transport Layer Security) 1.0 encryption. This change is part of our ongoing efforts to maintain the highest security standards and promote the safety of customer data. Because the Analytics reporting interface already requires a modern web browser, we do not anticipate issues. If you are unable to connect to Adobe Analytics reporting after July 19, you should upgrade your browser to the latest version .
  • Starting September 13, 2018, Adobe Analytics Reporting API will no longer support TLS 1.0 encryption. Customers who access the API should verify that they will not be impacted.
    • API clients using Java 7 with default settings will need modifications to support TLS 1.2 . (Refer to “Changing default TLS protocol version for client end points: TLS 1.0 to TLS 1.2”.)
    • API clients using Java 8 should not be impacted because the default setting is TLS 1.2.
    • API clients using other frameworks will need to contact their vendors for details on TLS 1.2 support.
  • Starting September 13, 2018, Adobe Analytics Data Collection will no longer support TLS 1.0. With this change, we will no longer collect Analytics data from end users with older devices or web browsers that do not support TLS 1.1 or later.
    Note: If your web site does not support TLS 1.0, you will not be impacted by the collection change.
Upcoming support changes for Date-Enabled and Numeric Classifications
May 7, 2018
In the May 10, 2018 Maintenance release, we will begin limiting the functionality of date-enabled and numeric classifications. These classification types will be removed from the Admin and Classification Importer interfaces.
From that date on, no new date-enabled and numeric classifications can be added. Existing classifications can still be managed (uploaded to, deleted) through the standard classification workflow, and will continue to be available in reporting.
Upcoming support changes for Marketing Channel Cost and Budget
February 28, 2018
In the April maintenance release, we will remove Marketing Channel Cost and Budget from the Admin > Marketing Channel menu. No new cost and budget data can be added. Existing cost and budget data will continue to be available in reporting, but cannot be updated.
Code Manager - Legacy H Code
February 8, 2018
Downloading legacy JavaScript (H code) from the Code Manager is no longer supported.
Data retention: Check and set your data retention policy for Adobe Analytics
February 1, 2018
The European Union’s General Data Protection Regulation (GDPR), which applies as from May 25, 2018, provides that Adobe, in its role as your data processor, must take appropriate measures to assist its customers in fulfilling access, deletion, and other requests from individuals. Applying appropriate, secure, and timely deletion policies is an important part of complying with this obligation. As a result, Adobe would like to work with you to implement a data retention policy before GDPR takes effect on May 25, 2018.
What to expect
Unless you already have an Adobe Analytics data retention policy in place, Adobe will begin applying data retention as currently specified in customer contracts for Adobe Analytics, unless other arrangements are made.
Most Adobe Analytics contracts state that Adobe may delete data after 25 months. Once a data retention policy is in place for your organization, it is enforced on a rolling monthly basis. Data retention for longer periods than 25 months is available for an additional fee. Data retention periods for shorter periods can also be configured by contacting Customer Care.
You will soon receive an email with additional details for your organization.
Data retention impacts all methods for accessing historical Adobe Analytics data, including but not limited to Reports & Analytics , Analysis Workspace , Report Builder , the Web Services Reporting APIs, data warehouse, and data feeds.
Next steps
Identify stakeholders within your organization responsible for making decisions about data retention. Your organization is best placed to know the appropriate period for which Adobe Analytics data should be retained.
Contact your Adobe Customer Success Manager if you have questions regarding data retention for Adobe Analytics.
User account linking
October 26, 2017
Analytics users no longer need to manually link their accounts between the Experience Cloud and Analytics. Users can contact their Admin Console administrator to request Analytics access.
The Analytics user ID migration enables administrators to easily migrate user accounts from Analytics User Management to the Adobe Admin Console. After your users are migrated, they will have access to the purchased solutions and core services available in the Experience Cloud.
Notice for API Methods affected by the migration to the Admin Console.
September 21, 2017
Adobe will phase out the Permissions and Company.GetLoginKey API methods as part of our effort to migrate user access and management to the Admin Console.
All Analytics companies that currently use these methods will receive a pre-migration notification beginning March 31, 2018 . After receiving this notification, administrators will have 30 days before their migration starts, and these methods will cease to work for your company.
To prepare for this event, view the list of affected APIs, and learn what Adobe recommends, see Analytics Administration API 1.4 .
Bot Rules
Sept. 21, 2017
We recommend defining no more than 500 bot rules per report suite.
The user interface allows for 500 rules to be manually defined. After this limit is reached, rules need to be managed in bulk through the Import File and Export Bot Rules options.
Calendar Events: Displaying top 20 most recent events
September 21, 2017
To ensure optimal reporting performance, the 20 most recent calendar events will be displayed on trended and overtime graphs.
August 23, 2017
As of August 22, Adobe Analytics started determining geo_zip on all hits received during data collection. This update increases data accuracy, particularly for mobile devices. Previously, the geo_zip was set once per visit. Now, geo_zip can correctly change during a visitor's visit. The geo_zip field is not used in reporting, but surfaces in Data Feeds.
Geo Segmentation
August 21, 2017
On August 22, Adobe Analytics enabled Geo Segmentation reports for all customers. This change is in anticipation of the upcoming removal of the geo segmentation settings in the Admin Console.

New Features in Adobe Analytics

Enhancements and new features released in Adobe Analytics.
Feature Name Description
Advertising Analytics lets you pass your search engine data into Adobe Analytics from Google AdWords, Yahoo! and Bing.
You have the following metrics available to do side-by-side reporting with the rest of your Analytics data:
  • Clicks
  • Costs
  • Impression
  • Quality Score
  • Average Position
Additionally, you have the following dimensions available in Analytics:
  • Keyword MatchType (AMO ID)
  • Ad Platform (AMO ID)
  • Account (AMO ID)
  • Campaign (AMO ID)
  • Ad Group (AMO ID)
  • Ad (AMO ID)
Note: Advertising Analytics is available for customers on the Select, Prime or Ultimate SKUs.
Legacy OAuth Application
Admin > User Management > Legacy OAuth Application
This feature replaces the Application section in the Developer Connection. Legacy OAuth enables you to create and manage OAuth applications to get authenticated to use the Reporting API.
More details about OAuth authentication flow can be found here. See OAuth2 Process for information about the OAuth authentication flow.
The Ad Hoc Analysis Project Converter converts your Ad Hoc projects to Analysis Workspace , with the click of button.
Copied projects can then be used, modified, and scheduled as needed in Analysis Workspace .
Adobe Analytics Connector (in the Microsoft Power BI desktop)
The Adobe Analytics Connector is available as a native data connector in the Power BI desktop experience. When launched, you can authenticate using your existing Adobe ID. You can then access an easy-to-use navigator to the report suite data elements and build data requests.
Context-aware sessions allow mobile analysts and product managers to define how they would like to treat a visit for their mobile application retroactively. It adds the ability to process background hits outside of a visit and to start visits on app launch.
Analysis Workspace enhancements
  • Tips of the Day : Tips will generate on a regular basis and will (along with a short video) display in the bottom right corner of the interface. They are meant to familiarize you with [!UICONTROL Analysis Workspace] features. You can dismiss Tips by clicking the X close to the tip or disable them by clicking Help > Disable Tip of the Day .
  • Segment templates and calculates metrics templates : The left rail now shows segment templates and calculated metrics templates.
  • Ability to scroll while dragging components : You can now scroll up and down while dragging components to a new location.
  • Additional information on anomalies : When hovering over an anomaly in a line chart, the information now shows the date and the raw value of the anomaly.
Reporting: Change to Visitor Zip/Postal Codes dimension
We updated the Visitor Zip/Postal Codes dimension to bring it in line with other geo variables so that the first value of a hit receives credit for that hit.
For example, if you run a Cities report and break it down by Visitor Zip/Postal Codes, only the first value for each hit is shown in the breakdown.
Change to Classifications
The Classifications UI has been updated to end support for numeric and data-enabled classification types.
The following changes were made to the Data Governance Labeling UI in Analytics:
  • The ACC-DEVICE label is now called ACC-ALL .
  • Field values labeled DEL-DEVICE will be anonymized only where a specified ID-DEVICE is present on the event. Other instances of these values, which occur in events that are not being deleted, will not be changed. As a result, reports that calculate unique counts on the field may change. On shared devices, identifiers for other individuals beyond the data subject may be removed.
  • The Do Not Delete label has been removed.
  • Added the ability to export the Data Governance labels on your variables to a .csv file. This facilitates sharing the labels with your Legal team.
  • Added sample values for dimensions, will make it easier to see what type of data each variable contains and how it should be labeled.
In addition,
  • A new GDPR API parameter is available for use in GDPR requests to Analytics, expandIds , which can be set to true or false . It defaults to false if not specified.
In-product feedback option for supported users
Customer Care-supported users have a new option under Help where they can submit Analytics product feedback. Select the menu option Submit Support Ticket and provide feedback or submit bugs directly from the UI.
LiveStream enhancement
Planned release effective May 15, 2018
mc_audiences column has been added. mc_audiences is the Audience Analytics segment ID list from Adobe Audience Manager .
Note: This does not include friendly names because they are a classification of the ID.
Countries report in Ad Hoc Analysis
The Countries report in Ad Hoc Analysis has been renamed to Countries/Regions.
Video Analytics
Media Collection API
Media publishers that have not been able to fully measure their video views, either due to VA SDK restrictions or lack of Video Analytics (VA) SDK support, can apply the Media Collection API to these devices. This enables clients to have transparency against all the devices that their users view videos on, including devices like VR headsets, gaming consoles, and more. The Media Collection API provides the granular, standardized metrics through your heartbeat VA SDK collection. Now you can combine those metrics to see the full customer journey.
  • Measure Video On Any Device: Apply the Media Collection API across any device that does not currently have SDK support, including gaming consoles and VR devices.
  • RESTful API to Compliment the VA SDK: The Media Collection API is built to provide a streamlined, efficient measurement mechanism to achieve the same granular results and metrics available via the SDK.
  • Holistic Audience Measurement: The Media Collection API can now provide a holistic view of all customer engagements with video to gain a more accurate perspective on your full customer reach.

Analytics - Fixes and Updates

Fixes and minor updates applied to Adobe Analytics interface tools and components (Analysis Workspace, Reports & Analytics, Report Builder, and so on).
Product Component/Tool Fix or Update
Analysis Workspace
  • Fixed an issue that occurred when opening the Calculated Metric Builder from [!UICONTROL Analysis Workspace]. This caused the Function drop-down list to display no options. (AN-160698)
  • Fixed multiple issues with the Search function in Freeform tables. The result is an improved editing experience for basic and advanced filter queries. (AN-159843)
  • Fixed an issue that prevented the creation of tags if the text matched an already existing tag. (AN-159363)
  • Fixed an issue that caused text visualizations to default to the top of the page and prevented them from being placed in the desired location. (AN-159148)
  • Fixed an issue that caused a Japanese and Korean character input problem in the Search field in Freeform tables. (AN-158778)
  • Fixed an issue that caused changes to project modification dates when non-admins favored, applied tags to, or approved projects. (AN-157398)
Other Analytics Issues
  • Fixed an issue in the Segment Builder, where the labeling on the Only Before Sequence and Only After Sequence options was switched and has now been restored. (AN-160747)
  • Fixed an issue that caused non-admin users to have access to some report suite tools. (AN-159451)
  • Fixed an issue with [!DNL Analytics] for [!DNL Target] classifications: going forward, when you create a report suite by copying its settings from another report suite that has [!DNL Target] classifications set up, the Target classifications will be mapped to the new report suite. (AN-156702)
  • Fixed an issue with the password expiration feature under Company Settings. (AN-154927)
  • Fixed an issue that prevented the Transfer Assets functionality from working if the user whose assets were to be transferred was listed as the owner of alerts. (AN-160747)
  • Fixed an issue that occurred when logging in to Analytics through the Experience Cloud: when multiple login companies were associated with a user name, sometimes an incorrect login company was selected. (AN-160880)
Data Workbench

Analytics - Developer, Administration, Data Collection, and Implementation

Fixes and updates applied to Analytics administration tools, including implementation and developer (Web Services and SDKs).
Product / Feature Update
Web Services Reporting API
  • Removed support in the Reporting API for Category reports when currentData=true or when a virtual report suite is used. (AN-156724)
  • Fixed issue that prevented you from adding 1000 items to the reportDescriptions element.selected field. (AN-158943)
AppMeasurement (Legacy and Mobile SDKs)
See AppMeasurement Release History the following for a release history of AppMeasurement on the following platforms:
  • JavaScript
  • iOS
  • Android
  • Flash-Flex
  • OSX
  • Windows Phone, XBOX, Silverlight, and .NET
  • BlackBerry
  • Java
  • PHP
  • Symbian

Audience Manager

Feature Description
We released DIL version 7.0, which includes the following upgrades and fixes:
  • Fixed a race condition in Launch with the DIL SiteCatalyst Module . (CORE-10266)
  • Implemented UX reviews of the DIL Launch extension. (CORE-8143)
Contact your Adobe consultant or customer care for the latest version, or get it from Digital Tag Management (DTM) or Adobe Launch .
GDPR Readiness
As we approach the May 25th, 2018 date at which the European General Data Protection Regulation (GDPR) comes into law, we have prepared documentation to assist you in managing consumer data in Audience Manager to meet GDPR obligations. Read on:
Fixes, Enhancements, and Deprecations
  • Fixed a bug where customers couldn't retrieve a list of all traits through API calls. (AAM-36824)
  • Fixed a bug in the Segment Builder code view where expressions containing parentheses would drop the parentheses if customers would edit the segment again. (AAM-36393)
Known Issues


Refer to the Adobe Target Release Notes for the latest release information about the following products:
  • Target Standard and Premium
  • Recommendations Classic


Adobe Primetime is a multiscreen TV platform that helps media companies create and monetize engaging, personalized viewing experiences.


Adobe Campaign provides an intuitive, automated way to deliver one-to-one messages across online and offline marketing channels. You can now anticipate what your clients want using experiences determined by their habits and preferences.
For product documentation, see:

AEM release notes

Adobe recommends customers with on-premise deployments to deploy the latest patches to ensure higher stability, security, and performance.
Title Description
Product Releases
AEM Smart Custom Tags 2.1
Latest Enhanced Smart Tags release delivers key improvements such as the following:
  • Algorithm optimizations to further improve model precision, recall values.
  • Support for resetting model training for all tags at tenant level.
  • Support for Enhanced Smart Tags namespaces to avoid conflicts.
  • New model replacement policy to avoid any degradation due to retraining.
  • Monitoring for service usage per tenant.
  • Clustering, connection specific issues resolved to improve service robustness.
Product maintenance
AEM 6.2 Service Pack 1-Cumulative Fix Pack 14
AEM 6.2 SP1-CFP14 (, released April 10, 2018, is an important update that includes key customer fixes released since the general availability AEM 6.2 SP1, December 2016.
The European Union's GDPR (General Data Protection Regulation) on data privacy rights takes effect May 2018. Learn more about AEM and GDPR compliance .
Repository restructuring in AEM 6.4
AEM Developer Reference Material
AEM 6.4 Developer Reference Materials are now available .
The annual virtual global conference provides in-depth sessions for enterprise developers, architects, and data scientists at all experience levels. Live sessions are held in India Standard, British Summer and Pacific time zones. Ticket holders also have unlimited access to all recordings for one year.
Adobe IMMERSE is the annual virtual global conference for any developer who is building solutions on Adobe Experience Manager. We also have additional sessions this year on Adobe Cloud Platform, Adobe I/O, Adobe Sensei, ColdFusion, and FrameMaker.
Get in-depth product introductions, "how to" recipes, best practices and code examples from experts within Adobe and the broader developer community. Live sessions will be broadcast across three time zones:
  • Americas (Pacific Standard Time)
  • Europe (British Summer Time)
  • APAC (India Standard Time)
Check out the agenda, then register-using discount code MR765z for a $25.00 USD discount-at the following: . Do not miss out on the largest developer conference hosted by Adobe!
AEM Technologist Meetup Group
This virtual group provides you with notifications for AEM GEMs, Ask the AEM Community Expert webinars as soon as they are scheduled. You also get notified of in-person events and regional user group meetings.
Join at the following:
This webinar series is focused on the newest innovations and best practices for working with the latest release of AEM.
Sessions are presented by Adobe Experts on Wednesdays. You can access all our sessions on-demand here .
Ask the AEM Community Expert
This webinar series is focused on top topics of discussion in the AEM HelpX Forum.
Sessions are presented by Adobe Community Experts. You can access all our sessions on-demand here .


See Livefyre Release Notes for the latest information.

Advertising Cloud (formerly Advertising Cloud)

Updated: May 2, 2018 for the May 12 release:
Feature Description
Integration with Adobe Analytics
To support expanded/extended text ads, the "Ad Headline 2" field is now included in the "Ad Title" and "Ad" classifications that are pushed to Analytics.
Search Campaigns
The following support is available for Bing Ads dynamic search ads (DSAs) and for Google AdWords DSAs in the new AdWords experience. These ad types are referred to as "expanded dynamic search ads (eDSAs)."
  • Your existing DSAs are included in the Ads tab and in the Ad Variation Report and other aggregated reports. eDSAs have a creative type of “Expanded Dynamic Search Ad.”
  • You can create AdWords ad groups for DSA ads in existing new-format DSA campaigns, using the new Ad Group Type “Search Dynamic.” You can’t yet create DSA ad groups for Bing Ads, nor DSA campaigns for AdWords or Bing Ads.
  • You can create Bing Ads and Google AdWords eDSAs in DSA ad groups.
The Labels Classification Beta view within the Search Advertising > Campaigns menu includes Classifications and Label Values sub-views. The Label Values view shows data for your label classification values. By default, data is shown for your keyword-level label values, but you can optionally view data for your ad-level label values.
Search Constraints
(Beta) Your existing constraints will be migrated to the label classification architecture. Your account manager will let you know the migration will occur. With the new architecture, only one constraint or one bid rule can be assigned per bid unit (keyword, placement, or product group). If you previously assigned multiple constraints to a bid unit, only the one with the highest priority will be retained. Only active constraints will be migrated.
When constraints are migrated, their settings, conditions, and entity assignments remain intact. Migrated constraints will behave exactly like the legacy versions, so there will be no impact on how they perform. Once your constraints are migrated:
  • You can create and manage your constraint rules from Search Advertising > Optimization > Constraints Beta. The following constraint types are supported: Bid & Position, Bid Shift, and Search Engine Minimum Bid. When other constraints types are migrated, they will remain intact but can't be edited.
  • You can assign constraints to bid units, and unassign them, from the toolbar in the Campaigns views.
  • A "Constraints" column, available in the Search > Campaigns views, report columns, and downloaded bulksheets, includes the existing constraint for each row. The column is available in the "Label Classification" columns for the relevant entity types.
Search Bid Rules
A "Bid Rule" column, available in the Search > Campaigns views, report columns, and downloaded bulksheets, includes the existing bid rule for each row. The column is available in the "Label Classification" columns for the relevant entity types.
You can unassign bid rules using a new Unassign option in the toolbar in the Campaigns Beta views.
Search Bulksheets
(Google AdWords accounts) Bulksheets now support remarketing list (RLSA) exclusions for campaigns and ad groups. The Download Bulksheet dialog for AdWords campaigns includes the new optional entity sections "Ad Group RLSA Negative" and "Campaign RLSA Negative," with the fields "Campaign Name" (for campaign-level negatives), "Ad Group Name," "Audience," "Target Type" (with the value exclusion ), and "RLSA Target Status." In addition, the "RLSA Target" section was renamed "Ad Group RLSA Target" and now includes the "Target Type" column (with the value inclusion ).
Search Advanced Campaign Management
For new advertiser accounts, the missing line items in a manually uploaded feed or in an FTP feed/GMC account aren't changed by default. The settings can optionally be changed to delete or pause the missing line items. The settings haven't changed for existing advertiser accounts.
Feed filters in text ad and shopping ad templates now include the operators not in , less than , and greater than .
Legacy label values in text ad and shopping ad templates are now read-only.
When legacy constrained labels and plain labels are migrated to the new label classification structure in the coming weeks, your existing labels will be automatically replaced with the label classification values and constraint values (when applicable) that are mapped to them. However, if your templates include labels using dynamic values from a feed file, modifiers, or legacy labels that aren't mapped to label classifications, then those values won't be automatically added to the Label Classifications tab. Once your account manager informs you that your legacy labels have been migrated, check the values in the Label Classifications tab and edit them if necessary. The dynamic values will continue to work until the legacy label infrastructure is disabled.
In the Keywords tab, you can now filter the "Match Type" column to include Negative Broad , Negative Exact , Negative Phrase , and Product Group .
Advertising Cloud help is available in the product under the Help ? menu.