Campaign Studio Webhook Connector

Fix

There was an issue that caused parsing errors on the Page Hits payload that Campaign Studio sends to CDP.

GDPR

Fix

For a few customers, GDPR workflow failed without displaying any errors.

Campaigns+

Feature

CDP now has a new content model: Transaction count in a time frame. This model helps you to output the total number of orders by a customer within the refinement conditions and a specific time frame, thereby allowing you to create more customer-focussed campaigns.

Campaigns+

Change

CDP now allows you to view clone history of all cloned campaigns.

Campaigns+

Change

CDP now maintains order for filters, refinements, segment criteria, and content and displays them as they were added to a campaign.

GDPR

Fix

Old and incorrect data resurfaced due to GDPR purge.

Campaigns+

Change

You can now select Facebook output connectors even if the campaign has content. This is useful in multiple destination scenarios.

Campaigns+

Fix

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

Campaigns+

Fix

Deleted content echos were not deleted correctly.

Campaigns+

Fix

Text overlapped while displaying long filter names.

UDM

Change

CampaignID and CampaignName columns are now available for marketing performance reporting of Promotiontypesummary.

Campaigns+

Change

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

Campaigns+

Fix

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

Campaigns+

Fix

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

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

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.

GDPR

Change

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

360 Profiles

A1DEV-4201

We fixed an issue with the 360 Profiles overview UI to prevent lengthy text from clipping with other values.

Actions Campaigns+

A1DEV-4154

We are introducing a new calculated content model: Event count in a time frame (Product or Product Category Browsed). Actions users can now split customers based on behavior with specific Product or Product Categories, or include an aggregate count of Product/Product Category browsed in the content of their campaign’s output file. This feature is in beta currently, so please ask your Customer Success Manager if you’d like it enabled for your account.

UDM+

A1DEV-4210

Fixed an issue with our Business Intelligence workflow that was causing it to fail when more than 200 attributes existed on our customer summary entity.

Actions

A1DEV-4117

Fixed an issue where users were able to move Actions and Reports folders to create folder hierarchies 4 or more levels deep. Folder hierarchies are supported only up to three levels deep. The user is now restricted from moving folders to more than three levels deep.

Actions Campaigns+

A1DEV-4109, A1DEV-4136

Actions users can now export distinct output attributes for one-to-many content models (e.g. ‘last products purchased’, ‘last products browsed’, ‘last abandoned products’, ‘latest transactions’, and ‘latest events’) by selecting the ‘Deduplicate’ option in the Content UI. If you select ‘Deduplicate’ the campaign executor will output only distinct values for the attributes you have selected. For example, if you’d like to output unique products browsed in the last 24 hours, under ‘Last Products Browsed’ you can output Product Name, Product URL, and Image URL to your email provider and select ‘Deduplicate’ so that only unique combinations of Product Name, Product URL, and Image URL are output.

Actions Campaigns+

A1DEV-4214

Fixed an issue where Campaign+ segments could disappear after saving a campaign under certain conditions.

Responsys Output Connector

A1DEV-2901

Improved the error reporting in our Responsys Output Connector so that it properly reports invalid counts for message and dispatch records.

360 Profiles

A1DEV-1242

Fixed an issue that could cause resetting the 360 data stores to fail when misconfigured but inactive columns exist in the 360 Profiles configuration.

Actions

A1DEV-3487

Improved the user experience of creating Campaigns with names that start with a period. When pushing to SFTP the output file name is defaulted to the campaign name. A period (.) is not allowed as the first character in a file name and therefore was causing the push to fail. We now remove leading period from file names when pushing to SFTP.

Actions Campaigns+

A1DEV-2903

Fixed an issue with the move folders UI that was preventing users from easily seeing which folders has sub-folders.

Actions Campaigns+

A1DEV-4090

Fixed an issue with timezone in the history dialog’s chart view. The history chart now converts the execution datetime to the tenant’s timezone.

Actions Campaigns+

A1DEV-4156

Fixed an issue with template reports where last execution date on the listing page was stored and displayed incorrectly.

Facebook Output Connector

A1DEV-4138

Updated Facebook API version to 8.0.

Privacy API

A1DEV-4101

Fixed an issue with the Privacy API that would result in the purging of Transaction Message Cross-Reference records during every data erasure request.

Actions

A1DEV-1278

Improved the performance of the Campaigns listing page when loading a large number of campaigns.

Actions

A1DEV-3481

Fixed an issue where campaign execution failed when two or more ‘Revenue in a time frame’ calculated content models were added as content to a single campaign.

Actions

A1DEV-3529

Added a validation to the UI when content output attributes are empty and Send Now action is performed.

Actions Campaigns+

A1DEV-3501, A1DEV-4116

Fixed an issue where Campaigns+ with segments would incorrectly calculate relative time frames (in the last, in the next, in the range of, in the future range of, & at least) in Audience filters/refinements for executions after the first execution. Instead of calculating relative time frames based on the campaign start date time, they were being calculated based on the campaign first execution date time. This has been fixed so that relative time frames are calculated correctly.

Privacy API

A1DEV-2932

Improved the performance of the Privacy API when deleting from campaign history. This should improve the performance of GDPR/CCPA data erasure requests.

Actions

A1DEV-2881

Improved some Actions error messages to make them more user friendly and actionable.

Actions Campaigns+

A1DEV-2911

Fixed an issue in Campaigns+ where combining A/B test variants with a one-to-many content model (e.g. last products browsed) could result in individual master customers existing in multiple variants.

Actions Campaigns+

A1DEV-2930

Made significant performance optimizations that make reading and updating segments faster.

Facebook Output Connector

A1DEV-2915

Fixed an issue with with how the Facebook Output Connector logs errors. This issue sometimes resulted in failures not being properly reported to the user.

Input Connectors

A1DEV-3510

Fixed an issue with record count alerts that was preventing their modification once set.

Responsys Output Connector

A1DEV-2924, A1DEV-2925

The Responsys Output Connector now supports the aliasing (i.e. renaming) of column names (i.e. supplemental table headers).

Actions

A1DEV-2868, A1DEV-2937

AgilOne has been rebranded as the Customer Data Platform. This a part of a much larger effort to make Acquia product names more descriptive. This should make learning about and onboarding to the other Acquia Marketing Cloud products much easier. With this effort the ‘AgilOne’ name should no longer appear in Actions.

Actions: Campaigns+

A1DEV-2882

Actions Campaigns+ users can now click on the last execution status in the campaign listing page to quickly open the campaign history pop-up to see details on the campaign’s sub-steps.

AIF: Bronto Input Connector

A1DEV-2250

Fixed a bug where the Bronto Input Connector was failing due to large size of some email’s HTML source code. We are no longer ingesting the HTML source code of email messages from Bronto.

Config App

A1DEV-3510

Fixed a bug that was preventing us from updating SFTP input connector settings when record count alerts were enabled.

Metrics

A1DEV-2905

Made UI enhancements to Metrics Email Delivery.

Platform: UDM+

A1DEV-2773

Updated the data model to accommodate a new machine learning model: Predictive Sends.

Actions

A1DEV-2856, A1DEV-2887

Improved performance of Campaign ‘Send Now’ execution.

Actions Campaigns+

A1DEV-2908, A1DEV-2917

Campaigns cannot be executed when segment counts are running. Trying to do so throws an error message. The previous error message was not helpful and therefore has been improved. The new message now displays: Segment count is currently in progress. Please try again in the future.

Config App

A1DEV-2608, A1DEV-2810

Added the ability to send customizable welcome email to new users. Now a custom welcome email can be applied for each client.

Platform

A1DEV-1499

Fixed a bug where soft deleted records were still appearing during new tenant provisioning and after truncating all data in a tenant. This was uncommon in production, but more common in lower environments (e.g pre-production and UAT environments).

Platform

A1DEV-2045

Logging optimizations done to improve ease of troubleshooting.

Silverpop Output Connector

A1DEV-2415

Silverpop URLs were migrated to Acoustic URLs since the former are no longer supported.

Actions

A1DEV-2619, A1DEV-2620, A1DEV-2621, A1DEV-2745

Actions Campaign errors were previously not surfaced to Hub users. When a campaign fails, you can now enter the campaign history user interface to see which sub-step failed and what was the failure reason.

Actions

A1DEV-2647

Campaign history and audience history errors now throw warnings instead of failures.

Actions

A1DEV-2717

Fixed the bug where any campaign created with a name containing plus (+) character broke the Lookup API for the ‘Were included in an AgilOne Campaigns+ audience’ filter.

Actions Campaigns+

A1DEV-2761

Fixed the bug which enforced variant names to be unqiue across all segments. Each variant under a single segment must still have a unique name.

Platform: Security Service

A1DEV-2471

Improved stability and performance of our login service.

Salesforce Marketing Cloud Output Connector

A1DEV-2705

Support for FTP connections was removed from our SFMC connectors.

Actions

A1DEV-2757

Recently a few campaigns with large segmentation trees have caused the success/failure reporting workflow (i.e. campaign status consumer) to start failing silently. This does not impact the execution of campaigns, but merely prevents the execution status from being reported to the Hub user. In this release we have made some improvements to reduce the chance of this happening. We are planning some further improvements.

Actions Campaigns+

A1DEV-2685, A1DEV-2728

In Segment Builder you can now build segments with OR logic. This is especially helpful if you need to build a segment using more than one operator. For example:

• First Transaction Date before 1/1/2020 OR after 2/1/2020

• First Transaction Date before 1/1/2020 OR is empty

Execution Calendar

A1DEV-2656

We have fixed a bug in the Execution Calendar that was introduced by a recent change to an upstream dependency.

Platform

A1DEV-1816

We have removed a bottleneck in our Data Warehousing workflow that was caused by a data skew when validating customer records.

SSO

A1DEV-2624

We have fixed a bug in our Single Sign-On (SSO) support (currently in beta) so that it no longer forwards server-based integrations to the SSO identity provider.

Actions

A1DEV-2598

The Actions train icons have been fixed for all major browsers and operating systems.

Actions Campaigns+

A1DEV-2072, A1DEV-2528

We have added lookups for segments and variants to the ‘Were included in an AgilOne Campaign+ audience’ filter.

Hub

A1DEV-2601

Now when you clone a campaign, report, look, and/or export a default name will be populated.

Platform: Webtag

A1DEV-2555

The AgilOne webtag has been improved to more strictly reference a core dependency, the a1.js file. Previously if any other javascript file ended in ‘a1.js’, then the AgilOne webtag would throw an error.

Actions

A1DEV-2475

Actions does not require or enforce that each and every campaign is provided a unique name. The intention behind this is that an existing campaign can be easily replaced with a new campaign of the same name. One side effect is that the ‘Were included in an AgilOne Campaign+ audience’ and ‘Were included in an AgilOne legacy Campaign audience’ filters only allow the user to select campaigns based on name. If two campaigns share the same name, then these filters used to randomly select one of the two campaigns. We have fixed this behavior by making sure that if two campaigns share the same name, you can select both campaigns based on campaign ID.

Actions Campaigns+

A1DEV-2567

The ability to clone segments and variants has been fixed. Previously, in some situations, cloning a segment or variant could corrupt the campaign definition.

AIF Output Connectors

A1DEV-2323

API-based output connectors could fail due to deprecated and invalid ASCII control characters in client data. We have patched this bug so that deprecated ASCII control characters that are known to fail API post payloads (by corrupting their JSON structure), are ignored and not pushed downstream of AgilOne.

Platform: Privacy API

A1DEV-2572

With this release we have significantly improved the performance of the Privacy API that purges data during GDPR/CCPA data erasure requests.

Acquia Mautic Input Connector

AGO-12881, AGO-13124

In this release we are making available the second half of our inbound integration for Acquia Mautic. Acquia AgilOne can now receive Mautic email send and open events in real time via a Mautic Webhook. This will enable shared Mautic and AgilOne clients to utilize these email events in AgilOne Actions Campaigns and 360 Profiles in near real time.

Actions: Campaigns+

AGO-12749, AGO-12750

Actions Campaigns+ users who push their campaigns to SFTP can now rename the output column headers at the top of the CSV file that the campaign produces. You may want to rename the default headers (e.g. customersummary_email) to be more user friendly (e.g. email) or to meet the needs of your downstream ingestion mapping.

Actions: Campaigns+

AGO-12980

Some Actions filters require that a lower boundary be input on the left and the upper boundary be input on the right. Previously there was no UI enforcement of this requirement. Now the Actions Campaigns+ UI will automatically flip boundaries that are input incorrectly.

Actions: Campaigns+

AGO-12998

In the Actions Campaigns+ Segment Builder the ‘add rule’ to segment button has been enhanced to enable OR conditions instead of AND conditions. This will allow you to build individual segments composed of many conditions. For example, a non-active segment could be defined as those who haven’t purchased in the last 2 years OR have never purchased at all.

Salesforce Marketing Cloud Output Connector

AGO-12997

With this release we have enhanced our Salesforce Marketing Cloud output connector to make sure that double-quotes () within data do not cause the push to SFMC to fail due to a poorly formed JSON payload.

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

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.

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

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.

Actions

AGO-12894

In this release we are performing a bit of Actions clean up: we have removed some now deprecated filters and content models. These filters and content models were made redundant and can now be removed.

Actions

AGO-12851

In Actions we performed some behind the scenes work that will enable us to add the payment method refinement options to many more filters and content models in the future.

Actions Campaigns+

AGO-11877, AGO-12827

For one-to-many content models in Actions Campaigns+, that output multiple products, transactions, coupons, child customer records, or events per master customer record (e.g. Last products purchased, Last products abandoned, Latest events, etc.) you can now input how many products/transactions/events are output per customer. As an example, for the Last products purchased content model, the number of products output per customer was previously fixed at 10, but now you can input the maximum number of products you would like to output per customer.

Platform: SSO

AGO-12523, AGO-12728

We’ve added support for single sign-on (SSO) in this release! This was a large project that once it exits an Early Adoption Program (EAP) will enable you to use your employers credentials to access AgilOne. Yay for no longer having to remember an AgilOne specific password!

Actions

AGO-12786

We have enhanced the ‘Revenue in a time frame’ content model to allow refinement by product and product category attributes. Furthermore, individuals without transactions are now defaulted to $0 revenue.

Actions

AGO-12866

We patched a bug that allowed duplicate campaigns to be created when the save button was clicked more than once before the original campaign save was complete.

Actions Campaigns+

AGO-12867

We fixed a regression that allowed mandatory output attributes to be removed from a campaign, causing the campaign to fail.

Machine Learning

AGO-12883

We patched a bug that was causing legacy machine learning models to fail after we upgraded a core dependency of our platform (Cloudera Hadoop).

360 Profiles

AGO-12825

We have fixed an issue with 360 Search by phone number that was preventing non-numeric characters (e.g. +, (, ), -) from being looked up correctly.

Actions Campaigns+

AGO-12729

For Campaigns+, we have fixed an issue where the Audience and Content were calculated and determined using two slightly different reference time frames. This could lead to individuals being dropped from your abandoned cart campaigns. This has been fixed, and is no longer an issue.

Facebook

AGO-12840

We have reviewed and updated our Facebook integrations to comply with upcoming changes to Facebook APIs.

Actions

AGO-12457, AGO-12826

When adding Content to an Actions Campaign users were previously prevented from adding two attributes with the same name, for example customer address1 and closest store address1. This was because in the backend we identified these two items with the label ‘address1’. We have improved this behavior so that you can now add two attributes with same name. Attributes are now identified by the source entity name and column name, so in the previous example the new labels are customer_addres1 and organization_address1. You still cannot combine two content models from the same source, for example closest store address1 and primary store address1.

Actions

AGO-12759, AGO-12767

To help delineate campaign activity filters, and better enable the use of both filters in a single Campaign+, we have renamed the following filters:

• Were included in AgilOne audience to Were included in an AgilOne Campaign+ audience

• Were included in an AgilOne campaign to Were included in an AgilOne legacy Campaign

• Were included in an AgilOne campaign and variant to Were included in an AgilOne legacy Campaign and variant

Furthermore, we have disabled the Were included in AgilOne audience and segment filter as it is duplicative with the Were included in an AgilOne Campaign+ audience filter.

Actions Campaigns+

AGO-12824

Previously a Campaign+ could become corrupted if an attribute used in Segment Builder was removed from Segment Criteria. We no longer allow you to do this behavior. You must first remove attributes from Segment Builder before you can remove them from Segment Criteria.

Actions legacy Campaigns

AGO-12843

With the previous release we accidentally introduced a bug for legacy campaigns. If you changed the channel of the campaign it would not be pushed to the new channel, but the old one. This has been fixed.

EuroMessage Input Connector

AGO-12770

We have improved our Euromessage Input Connector to be more robust in how it handles bad or corrupt data. Instead of bad data causing the whole process to fail, we now skip/ignore records with corrupt data.

Platform

AGO-12836

Stub parent product category records were being created with an incorrect Source Category Number. This has been fixed, so that auto-generated parent product category records now have the correct Source Category Number.

360 Profiles

AGO-12697

The 360 Profiles API now only returns a 404 error if the source customer number does not exist.

Actions

AGO-12094

In Actions we now hide previously selected values from the lookup dropdown.

Actions

AGO-12833

The 1950 release introduced a bug that caused campaigns that contain an OR condition within their Audience exclusion rule to fail. We patched this bug within 2 hours of the release.

Actions Campaigns+: multiple destinations

AGO-11686, AGO-12656, AGO-12656, AGO-12723, AGO-12740, AGO-12742, AGO-12752, AGO-12773, AGO-12774, AGO-12778, AGO-12792, AGO-12793

Significant effort was spent over the code freeze to add multiple destinations to Campaigns+. In Campaigns+ you can now push your audience and content to more than one destination. We will roll this feature out slowly as we gain confidence with it. To start you are limited to two destinations, and one of the destinations must be an SFTP.

Listrak Input Connector

AGO-12516, AGO-12621

Over the holidays we built a Listrak Input Connector. This enables the ingestion of contacts and email events (email send, open, click, bounce, etc.) via Listrak’s Data Export feature.