--- title: "2010 / 2012 Release - 2020-04-03" date: "2025-09-12T05:57:24+00:00" summary: "Discover AgilOne's latest updates: enhanced Actions, Campaigns+, connectors, and platform improvements for better customer data management." image: type: "announcement" url: "/customer-data-platform/release/2020-04-03/79711-2010-2012-release-2020-04-03" id: "d199e2b4-a23c-406d-b71e-64d4a0c5d235" --- **Area** **AgilOne JIRA** **Description of functionality after the fix** Actions AGO-12601, AGO-13037 In Actions we have added an is empty operator for numbers and dates so that you can filter on empty (i.e. null or blank) numbers and dates. For example, filter out an audience whose first transaction date is empty. Actions AGO-12801 With this release we have added the payment method and transaction payment method cross-reference entities as refinement options for all transaction-based filters. As long as the data is available, now you can refine your audience filter based on whether a private label credit card or gift card was used. Actions Campaigns+ AGO-12852, AGO-12853, AGO-12898 In Actions Campaigns+ we have designed the functionality to rename (i.e. relabel) the output column headers of any given campaign output file. At this point this functionality has only been implemented for the S3 output connector, but it will soon be implemented for the SFTP output connector as well. Actions Campaigns+ AGO-12858 We have added a couple of validations to the Campaigns+ user interface to prevent user-input labels for calculated content from causing campaigns to fail. Actions Campaigns+ AGO-12910 The lookup for ‘Were included in an AgilOne legacy campaign’ filter no longer returns Campaigns+ campaigns that are functionally irrelevant in this context. Actions Campaigns+ AGO-12966 We have fixed a bug with the ‘in the next’ operator that was preventing its use. Actions Campaigns+ AGO-12981 When using Campaigns+ Segments and Variants you can now divide the same upstream segment by multiple downstream splits (e.g. the segment ‘Male Jeans Buyers’ can be divided by both ‘Lifetime Revenue’ and ‘Recency’.) Actions Campaigns+ AGO-13032 We’ve patched a bug in the Campaigns+ destination page that was allowing users to re-order segment-specific echo content without propagating the re-sequencing to the other segments. Now the reordering of segment-specific echo content is no longer allowed. Bronto Input Connector AGO-12623 For clients that ingest data from Bronto, we have increased our daily look back window to account for processing lag within Bronto. This should insure that we do not miss any campaign and message data. Facebook Custom Audience Output Connector AGO-12968, AGO-12969 With this release we have updated our Facebook Output Connector to account for recent changes with Facebook APIs. Platform AGO-10250 With the winning address we are now promoting the United States Postal Service (USPS) National Change of Address (NCOA) match flag to the master customer record. This will be particularly useful for direct mail campaigns. Platform AGO-12480 We have enhanced our real time data ingestion API (i.e. DW Tracker API) to be more scalable for peak loads, especially as we onboard additional customers. Platform AGO-12921 For clients with physical retail stores, AgilOne by default calculates a ‘Primary Store’ which is the physical store that the customer has purchased at most frequently. Previously this calculation did not have a tie breaker implemented. For the scenario where a customer has purchased at two different stores an equal number of times we previously chose one of the two stores at random. Now we break ties by choosing the store that was transacted at most recently as the primary store. Platform AGO-12925 Before this release we promoted to the master customer record a mailing address country that was not standardized by AgilOne. It matched the raw data that we received. Now we are promoting and making available the mailing address country standardized in the 2-character ISO format, called ‘Country Code’. S3 Output Connector AGO-12832, AGO-12899 We have improved our AWS S3 output connector so that an Actions user can provide a campaign-specific file name, and a Config App user can customize the field delimiter. In addition, we have made several behind the scenes enhancements that may include improvements to stability, performance, and/or internal or unreleased features.