---
title: "2040 Release Notes - 2020-10-26"
date: "2025-09-12T05:57:24+00:00"
summary: "Explore key updates in CDP, including improved campaign execution, enhanced FB connector, and GDPR changes for better performance."
image:
type: "announcement"
url: "/customer-data-platform/release/2020-10-26/79646-2040-release-notes-2020-10-26"
id: "575a5302-9f3e-448a-a224-e84603c04ab6"
---

**Area**

**Type**

**Description**

Campaigns+

Change

CDP is now updated to have improved performance in campaigns execution.

Campaigns+

Change

The multi-select option is now available for `IN` and `NOT IN` operators for audience and content filters so that you can easily select and add values.

Campaigns+

Fix

Content was skipped for campaigns with 1:N content models.

Campaigns+

Fix

CDP didn’t allow negative values in audience and content filters and hence, negative revenue couldn’t be tracked effectively as part of campaign filters

Campaigns+

Fix

Incorrect status was displayed under the Audience step in zero audience scenarios.

Campaigns+

Fix

In some cases, cloned segments and variants weren’t displayed on the Content page.

FB Output Connector

Change

FB connector is now enhanced to include the following additional fields for better match and targeting:

*   Names: `FirstName` and `LastName`
*   Phone numbers: `primaryphone`, `secondaryphone`, and `mobilephone`
*   Primary Address: `City`, `State`, `Zip`, and `Country`

FB Output Connector

Change

You can now use alias in output columns and hence, specify alias name to specific source name.

UDM+

Change

CDP is now enhanced to update the schema for the _udm\_p\_{tenant\_id}\_ml\_out\_mc\_summary_ table in order to store the output of the new ML model: Next Best Action.

UDM+

Change

CDP is now enhanced to update the schema for the _udm\_p\_{tenant\_id}\_ml\_out\_mc\_summary_ table in order to store the output of the new ML model: Predicted Life Time Value.

GDPR

Change

CDP has now excluded the `TransactionSummary` table from GDPR as TransactionSummary is recalculated every day.

GDPR

Fix

GDPR purge request didn’t proceed if the number of _customerIDs_ were greater than 1000.