This webpage describes the updates Acquia made to CDP in 2020. For the latest updates, see Release notes.
2044.1 and 2044.2 Release Notes - 2020-12-14
| Area | Type | Description |
|---|---|---|
| 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, their data wasn’t purged from internal tables, such as DW Transaction tables. |
| GDPR | Fix | For a few customers, GDPR workflow failed without displaying any errors. |
| SFMC Output Connector | Fix | SFMC connector with SFMC (Exacttarget) campaigns failed. |
2044 Release Notes - 2020-11-11
| Area | Type | Description |
|---|---|---|
| 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 has now been enhanced to have multiple user interface improvements on the segment counts window. |
| Campaigns+ | Change | CDP now allows you to view clone history of all cloned campaigns. |
| Campaigns+ | Change | CDP has now been enhanced to have improved performance during campaign execution. |
| Campaigns+ | Change | CDP now maintains order for filters, refinements, segment criteria, and content and displays them as they were added to a campaign. |
| Core | Change | Help links in the CDP user interface have now been updated from agilonev6.zendesk.com to docs.acquia.com. |
| GDPR | Fix | Old and incorrect data resurfaced due to GDPR purge. |
| SFMC Output Connector | Fix | FTP URL updates by SFMC caused an issue with FTP credentials for SFMC output connector. |
2042 Release Notes - 2020-11-05
| Area | Type | Description |
|---|---|---|
| Campaigns+ | Change | You can now select Facebook output connectors even if the campaign has content. This is useful in multiple destination scenarios. |
| Campaigns+ | Change | CDP has now been enhanced to have improved performance during campaign execution. |
| Campaigns+ | Fix | Content was skipped for campaigns with 1:N content models. |
| Campaigns+ | Fix | Global content echo header validation didn’t work for duplicate headers with segment echo headers. |
| Campaigns+ | Fix | Deleted content echos were not deleted correctly. |
| Campaigns+ | Fix | Duplicate sequence numbers were displayed for segments on the content page. |
| Campaigns+ | Fix | Text overlapped while displaying long filter names. |
| 360 Profiles | Change | CDP has now been updated to display MasterCustomerID on top of the Profile Details page as well as UDM+ descriptions, when you hover over the “i” icon. |
| UDM | Change | CampaignID and CampaignName columns are now available for marketing performance reporting of Promotiontypesummary. |
| WebTag | Change | CDP has now enabled gzip encryption for CDP WebTag hosted on Google Cloud Platform. |
2040 Release Notes - 2020-10-26
| 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:
|
| 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. |
2038 Release Notes - 2020-09-30
| Area | Acquia JIRA | Description of functionality after the fix |
|---|---|---|
| 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-4199 | For segment-specific content, we fixed an issue with the ordering of content. Previously the sequence of segment-specific content was not consistently maintained. Segment-specific content is now sequenced in the order in which it was created. |
| 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. |
| AWS S3 Output Connector | A1DEV-2543 | Updated a key dependency to support AWS4-HMAC-SHA256 encryption. This allows our S3 output connector to be used across AWS regions, including EU Central. |
| 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. |
| UDM+ | A1DEV-2972 | We have added new calculations to our business intelligence workflow that indicate whether a customer is an omni-channel shopper, Physical-only shopper, or Digital-only shopper. The attribute will consist of the following values:
To support migration analysis, this attribute is available for three different time frames:
|
In addition, we have made several behind the scenes enhancements that may include improvements to stability, performance, and/or internal or unreleased features.
2036 Release Notes - 2020-09-16
| Area | Acquia JIRA | Description of functionality after the fix |
|---|---|---|
| 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-2482 | We are introducing a new calculated content model: Event count in a time frame (Email Clicks, Email Open and Email Sent). Actions users can now split customers based on behavior with specific emails (e.g. opened email X or clicked on email Y), or included an aggregate count of email events in the content of their campaign’s output file. This feature is in beta currently as we slowly roll it out, so please ask your Customer Success Manager if you’d like it enabled for your account. |
| 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-4172 | Fixed an issue with the echo content for segments & variants in the Campaigns+ content page. Previously the segment-specific output (i.e. echo) headers could swap with the other headers in the list leading to output values being swapped across column headers depending upon the segment. This could only occur when re-saving a previously saved Campaign + with Segments and segment-specific content, and can now be fixed by re-saving those campaigns. Note: Campaigns updated prior to this fix with mismatch of echo headers will need to be corrected manually. |
| Actions Campaigns+ | A1DEV-4214 | Fixed an issue where Campaign+ segments could disappear after saving a campaign under certain conditions. |
| Bronto Output Connector | A1DEV-4168 | Fixed an issue in the Bronto Output Connector where some special characters like ampersands (&) were being double escaped to prevent an improperly formed XML payload. We are now properly escaping these special characters so that they can be transferred in an XML and un-escaped in Bronto. |
| 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. |
In addition, we have made several behind the scenes enhancements that may include improvements to stability, performance, and/or internal or unreleased features.
2032 / 2034 Release - 2020-08-27
| Area | Acquia JIRA | Description of functionality after the fix |
|---|---|---|
| 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. |
| 360 Profiles | A1DEV-4088 | Fixed an issue where certain customizations to the 360 Profiles UI could cause the Profile tab to break. |
| 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-2869, A1DEV-4096 | We’ve added four new operators for text-based (i.e. String) filters and refinements: Begins With - value starts with the user’s input (case insensitive) Ends With - value ceases with the user’s input (case insensitive) Matches Regex - matches regex defined by Syntax. Does Not Match Regex - does not match regex defined by Syntax. |
| 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-2942 | Made performance improvements by introducing lazy loading to Segments & Variants in Campaigns+. |
| 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-4142 | Fixed an issue in Campaigns+ segments where a user input value of ‘days’ incorrectly changed to ‘weeks’ when the lower offset of a relative time frame was 0. |
| Actions Campaigns+ | A1DEV-4156 | Fixed an issue with template reports where last execution date on the listing page was stored and displayed incorrectly. |
| Bronto Output Connector | A1DEV-4144 | Fixed an issue with the Bronto Output Connector where one-to-many content models could push incomplete data, because the ordering of API calls could result in incorrectly overwriting previously pushed data with NULL. We also added additional logging to make future troubleshooting easier. |
| Facebook Output Connector | A1DEV-4138 | Updated Facebook API version to 8.0. |
| Hub UI | A1DEV-3528 | We are replacing helpdesk@agilone.com with the Acquia Support Portal. This should make logging and reviewing Support tickets much easier. In this effort we have added links for Acquia Help Center in the Hub UI. |
| 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. |
| Workflows | A1DEV-4113 | We improved the workflow failure notification alerts in order to reduce Support response times. |
In addition, we have made several behind the scenes enhancements that may include improvements to stability, performance, and/or internal or unreleased features.
2030 Release - 2020-08-13
| Area | Acquia JIRA | Description of functionality after the fix |
|---|---|---|
| Actions | A1DEV-1278 | Improved the performance of the Campaigns listing page when loading a large number of campaigns. |
| Actions | A1DEV-2589 | Fixed an issue where campaigns could fail due to conflicting output column names across different types of content models (e.g. product_name and campaign_name). The system now properly aliases the output headers to ensure there is no conflict. |
| 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-3504 | Fixed an issue where the Campaign History UI did not refresh the export status to ‘Success’, and instead displayed ‘Running’ after an export. This blocked subsequent exports. |
| Actions | A1DEV-3529 | Added a validation to the UI when content output attributes are empty and Send Now action is performed. |
| Actions Campaigns+ | A1DEV-2913 | Fixed an issue where users were not able to update the ‘Revenue in a time frame’ calculated content model in Segment Criteria. The issue occurred when saving segments built from the segment criteria ‘Revenue in a time frame’ after the segment criteria was named, saved, and renamed. |
| 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. |
| Facebook Offline Conversions Output Connector | A1DEV-3476 | Fixed the invalid parameter issue due to which Facebook Offline Conversions Output Connector were failing after Facebook introduced the Limited Data Use (LDU) feature: Limiting how data is used for people in California. |
| 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. |
| Responsys Output Connector | A1DEV-4123 | Fixed an issue where the Responsys Output Connector could start to fail after the 2028 release. The issue occurred when there was a mismatch of character-casing (lowercase vs. uppercase) between the Actions Campaign content headers and the Responsys supplemental table. |
In addition, we have made several behind the scenes enhancements that may include improvements to stability, performance, and/or internal or unreleased features.
2028 Release - 2020-08-03
| Area | Acquia JIRA | Description of functionality after the fix |
|---|---|---|
| Actions | A1DEV-2881 | Improved some Actions error messages to make them more user friendly and actionable. |
| Actions Campaigns+ | A1DEV-2852 | Fixed an issue in Segments & Variants where removing a segment did not result in the complete removal of the segment’s elements from the user interface. |
| 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-2926, A1DEV-3521 | Fixed a couple of issues with the campaign history reporting of the campaign status. In certain situations the campaign execution status was either not being reported, or was getting stuck in the ‘Running’ state. |
| Actions Campaigns+ | A1DEV-2930 | Made significant performance optimizations that make reading and updating segments faster. |
| Actions Campaigns+ | A1DEV-3501 | Fixed an issue in Campaigns+ where combining a segmented campaign with an audience filter that uses a relative time frame (e.g. in the last, in the next, in the range of, in the future range of) would cause the relative time frame to be incorrectly calculated for campaign executions after the first execution. The relative time frames are supposed to be calculated relative to the campaign start time, but if the campaign was segmented then they were calculated relative to the campaign first execution date time. |
| 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. |
| Hub | A1DEV-2282 | Made performance optimizations that should improve the load times of many pages in Hub. |
| Input Connectors | A1DEV-3510 | Fixed an issue with record count alerts that was preventing their modification once set. |
| Privacy API | A1DEV-2932 | Made performance optimizations to the purge of Campaign History during the execution of data erasure requests for GDPR and CCPA compliance. |
| 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). |
In addition, we have made several behind the scenes enhancements that may include improvements to stability, performance, and/or internal or unreleased features.
2026 Release - 2020-07-21
| Area | Acquia JIRA | Description of functionality after the fix |
|---|---|---|
| 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 | A1DEV-2872 | Fixed a bug where removing Segment Criteria was not always successful. |
| 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. |
| Actions: Campaigns+ | A1DEV-3156 | Fixed an issue where the campaign history pop-up was not loading for recently executed campaigns. |
| 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. |
| AIF: SFMC Connectors | A1DEV-3489 | Fixed an issue with the SFMC input and output connectors so that they now support strong FTP ciphers. The previously supported FTP ciphers have now been deprecated by SFMC. |
| 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-2849 | Fixed a bug where Metrics email is now scheduled and delivered using the tenant timezone. |
| Metrics | A1DEV-2905 | Made UI enhancements to Metrics Email Delivery. |
| Platform: UDM+ | A1DEV-2710, A1DEV-2900 | Introduced multiple performance optimizations to our Data Warehousing workflow. |
| Platform: UDM+ | A1DEV-2773 | Updated the data model to accommodate a new machine learning model: Predictive Sends. |
| Platform: UDM+ | A1DEV-2858 | Updated the data model to accommodate a new machine learning model: Likelihood to Pay Full Price. |
In addition, we have made several behind the scenes enhancements that may include improvements to stability, performance, and/or internal or unreleased features.
2024 Release - 2020-07-09
| Area | Acquia JIRA | Description of functionality after the fix |
|---|---|---|
| Actions | A1DEV-2856, A1DEV-2887 | Improved performance of Campaign ‘Send Now’ execution. |
| Actions Campaigns+ | A1DEV-2514, A1DEV-2888 | Improved performance of updating a campaign’s execution status (e.g. running, success, failed, etc.), thereby improving stability. |
| 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. |
| AgilOne | A1DEV-2734 | 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. |
| 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-2843 | The performance of the Privacy API (used to execute GDPR & CCPA data erasure requests) has been improved when purging from the data store that serves 360 Profiles. |
| 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-2028 | We are working hard to make failure messages more informative and actionable. In this effort the focus was on internal failure messages during the nightly refresh pipeline. |
| Platform | A1DEV-2045 | Logging optimizations done to improve ease of troubleshooting. |
| Platform | A1DEV-2853 | Improved the performance of one bottleneck step during our Data Warehousing workflow, which is part of our nightly refresh pipeline. |
| Silverpop Output Connector | A1DEV-2415 | Silverpop URLs were migrated to Acoustic URLs since the former are no longer supported. |
2022 Release - 2020-06-16
| Area | Acquia JIRA | Description of functionality after the fix |
|---|---|---|
| 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-2642 | Fixed the bug where ‘Revenue in a time frame’ calculated content model suppressed the audience when the customer did not qualify for the content model (e.g. had zero transactions within the bounds of the content model). This now defaults to $0 revenue if there are no transactions. |
| Actions | A1DEV-2647 | Campaign history and audience history errors now throw warnings instead of failures. |
| Actions | A1DEV-2681 | Fixed a bug where campaigns were failing when the Audience exclusion criteria started with a custom attribute filter. Metadata for the custom attribute was causing the audience to be parsed incorrectly. |
| 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 | A1DEV-2815 | An alert has been added to prevent you from clicking the Save button a second time before the earlier Save request finishes. |
| 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: DW Tracker API | A1DEV-2816 | Improved the performance of our inbound DW Tracker API. |
| Platform: Security Service | A1DEV-2471 | Improved stability and performance of our login service. |
| Platform: UDM+ | A1DEV-2678 | First & Last Transaction date attributes added to Customer summary for both Digital and Physical channels. This will help with omnichannel behavior analysis. |
| Salesforce Marketing Cloud Output Connector | A1DEV-2705 | Support for FTP connections was removed from our SFMC connectors. |
In addition, we have made several behind the scenes enhancements that may include improvements to stability, performance, and/or internal or unreleased features.
2020 Release - 2020-06-02
| Area | Acquia JIRA | Description of functionality after the fix |
|---|---|---|
| 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-2638 | In the Segmentation Criteria screen we have added some additional guardrails to prevent users from adding the same ‘Calculated Revenue in a time frame’ header twice. |
| 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:
|
| Cohort Analysis | A1DEV-2342 | Cohorts can now be deleted from Metrics and Interactive Queries by going to the Campaigns+ Destination screen. |
| Execution Calendar | A1DEV-2656 | We have fixed a bug in the Execution Calendar that was introduced by a recent change to an upstream dependency. |
| Metrics | A1DEV-1224 | In this release we have patched a bug that was preventing a look from being moved from its current space (i.e. folder) to a sub-space (i.e. descendent folder) of its current space. |
| Platform | A1DEV-1816 | We have removed a bottleneck in our Data Warehousing workflow that was caused by a data skew when validating customer records. |
| Reports, Exports | A1DEV-2654 | Clicking the ‘Save’ button twice in quick succession for a template report, legacy dashboard, and data export will no longer produce two duplicate entries. |
| 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. |
2018 Release - 2020-05-19
| Area | AgilOne JIRA | Description of functionality after the fix |
|---|---|---|
| Actions | A1DEV-2598 | The Actions train icons have been fixed for all major browsers and operating systems. |
| Actions | A1DEV-2658 | We patched a bug that was preventing two campaigns with the same name from being usable in the ‘Were included in an AgilOne Campaign+ audience’ lookup. |
| Actions Campaigns+ | A1DEV-2072, A1DEV-2528 | We have added lookups for segments and variants to the ‘Were included in an AgilOne Campaign+ audience’ filter. |
| Actions Campaigns+ | A1DEV-2399, A1DEV-2487 | Recently we introduced the functionality to rename (i.e. alias) output attributes sent to SFTP or an S3 bucket. We have improved this functionality to work for additional content models and be more extensible in the future. |
| Hub | A1DEV-2601 | Now when you clone a campaign, report, look, and/or export a default name will be populated. |
| Platform | A1DEV-2520 | In this release we have fixed a bug that was preventing certain functionality within our Identity Resolution Engine, Data Warehousing workflow, and Business Intelligence workflows from being UTF-8 compliant. Turkish characters should now be fully supported during these steps. |
| 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. |
| Settings: User List | A1DEV-2412, A1DEV-2413 | For admin users of AgilOne Hub, the User List page has been enhanced to surface the last login date of each user. |
In addition, we have made several behind the scenes enhancements that may include improvements to stability, performance, and/or internal or unreleased features.
2016 Release - 2020-05-05
| Area | AgilOne JIRA | Description of functionality after the fix |
|---|---|---|
| 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-2488 | Campaigns that used ‘variantname’ as a segment or variant-level output column used to fail due to an internal conflict. We have updated all internal column headers so that they cannot conflict with segment and variant-level output headers. |
| 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. |
| Actions Campaigns+ | A1DEV-2699 | In the 2014 release the ability to define a single segment with two segmentation rules that are OR’ed, caused campaign segmentation to fail. We have reverted this functionality for now. |
| 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: Data Warehouse Workflow | A1DEV-2519 | We have removed a bottleneck in our Data Warehousing workflow that occurred when processing large transaction volumes. |
| 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. |
In addition, we have made several behind the scenes enhancements that may include improvements to stability, performance, and/or internal or unreleased features.
2014 Release - 2020-04-21
| Area | AgilOne JIRA | Description of functionality after the fix |
|---|---|---|
| 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-13172 | We have patched a bug that was causing Actions filters and content that use the SQL count() function to fail. This included the ‘Transaction count in a time frame’ and ‘Event count in a time frame’ filters. Using these filters will no longer cause your campaign execution to fail. |
| 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+ | A1DEV-12797 | Actions Campaigns+ segment execution now performs faster than before. |
| 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-12995 | In the Actions Campaigns+ Segment Builder the undo button has been fixed. |
| 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. |
| Actions | AGO-13063, AGO-13074 | We have improved the edit and save performance of the Campaigns+ Segment Builder UI. |
| 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. |
In addition, we have made several behind the scenes enhancements that may include improvements to stability, performance, and/or internal or unreleased features.
2010 / 2012 Release - 2020-04-03
| 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.
2008 Release - 2020-03-16
| Area | AgilOne JIRA | Description of functionality after the fix |
|---|---|---|
| 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-12960 | We fixed a bug that was causing the ‘Redistribute existing coupons’ content model to fail when combined with another content model that outputs ‘email’. |
| 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-12872 | Sometimes when closing a Campaign+ that had not been edited a pop-up was incorrectly being surfaced asking if you would like to save changes. This has been fixed. |
| 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. |
| Mautic Input Connector | AGO-12802 | For clients that use or would like to use Acquia Mautic for marketing automation we have now built an input connector that can pull updated contacts and campaigns from Mautic daily. |
| 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! |
In addition, we have made several behind the scenes enhancements that may include improvements to stability, performance, and/or internal or unreleased features.
2006 Release - 2020-02-24
| Area | AgilOne JIRA | Description of functionality after the fix |
|---|---|---|
| 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-12858 | Header names for calculated content are now limited to alpha-numeric characters to prevent campaign failures. |
| 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-12232 | The Segment Counts pop-up now includes the campaign’s name at the top of the pop-up to reduce user confusion. |
| Actions Campaigns+ | AGO-12867 | We fixed a regression that allowed mandatory output attributes to be removed from a campaign, causing the campaign to fail. |
| Actions Campaigns+ | AGO-12782, AGO-12784 | In Campaigns+ you can now choose whether each content model is required and therefore suppresses audience members that do not qualify, or not-required so that all audience members are included in the output irregardless of whether they qualify for the content model. For example, ‘Last Abandoned Products’ should probably be required so that you do not send an ‘Abandoned Cart’ campaign to someone without abandoned products, but ‘Primary Store Details’ may not be critical to the message and therefore not required in the output. |
| 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). |
In addition, we have made several behind the scenes enhancements that may include improvements to stability, performance, and/or internal or unreleased features.
2004 Release - 2020-02-10
| Area | AgilOne JIRA | Description of functionality after the fix |
|---|---|---|
| 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. |
| Acquia Mautic Output Connector | AGO-12803, AGO-12834 | In this release we are introducing a brand-new integration with Acquia Mautic. This Mautic Contact Profile Output Connector will allow you to use AgilOne Actions to push any one-to-one output attributes (e.g. customer attributes, machine learning segments, and primary store details) to upsert Contact Profiles in Mautic. In Mautic you can then use AgilOne data to drive Mautic multi-destination drip campaigns (i.e. journeys). By default AgilOne upserts Mautic Contact Profiles by email address. One-to-many datasets (e.g. last products abandoned/browsed/ purchased, latest events, latest transactions, etc.) are not supported. |
| 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. |
| Actions Campaigns+ | AGO-12868 | In Campaigns+ Segment Builder we have fixed the ‘Click to add default segments’ button. |
| AGO-12840 | We have reviewed and updated our Facebook integrations to comply with upcoming changes to Facebook APIs. |
In addition, we have made several behind the scenes enhancements that may include improvements to stability, performance, and/or internal or unreleased features.
1952 / 2002 Release - 2020-01-28
| Area | AgilOne JIRA | Description of functionality after the fix |
|---|---|---|
| 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-12630 | For clients that ingest payment method (i.e. tender type) information into AgilOne you can now use the ‘Purchased a Product’ Actions filter to refine by details of both the payment method and payment method to transaction cross-reference. We plan to add these refinement options to other filters and content models once we can prove success with ‘Purchased a Product’ first. |
| 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:
Furthermore, we have disabled the |
| Actions | AGO-12837 | In 1950 we accidentally introduced a bug to Actions Campaigns that caused the SFTP output folder path to be ignored after a user saves the campaign if multiple destinations has not been enabled for the tenant. This has been fixed. |
| 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 Campaigns+: Complex Segmentation Criteria | AGO-12157, AGO-12779, AGO-12809, AGO-12814, AGO-12815, AGO-12822 | A significant amount of time was spent this release enabling Campaign+ segmentation by attributes that do not exist in customer summary. This enhancement will enable you to use Segment Builder to segment by machine learning segments, household attributes, closest store details, primary store details, and on-demand aggregations (i.e. calculated content) such as ‘Revenue in a time frame’. For now we are only enabling segmentation by machine learning segments. Once we have proved efficacy we will enable segmentation by the additional options listed above. Please let your Customer Success Manager know how you would like to segment your audience in Segment Builder. |
| 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. |
| DW Tracker API | AGO-12634 | With this release we are introducing new beta functionality within our DW Tracker API. If you have first party customer data without a source system, and therefore cannot build a Source Customer Number to uniquely identify the record, you can now ask AgilOne to generate a Source Customer Number for you. If you pass an event of type ‘a1CreateCustomer’ the DW Tracker API will respond with a UUID that you can use as the Source Customer Number to uniquely identify the individual customer. Please do not use this functionality without first speaking with the AgilOne Product and Services teams. |
| 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. |
| Interactive Queries | AGO-11544 | AgilOne can now push custom tables, not owned by the platform, to Metrics and Interactive Queries for analytics use cases. This enables us to push intermediate machine learning and IRE tables to snowflake for further analysis. |
| 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. |
In addition, we have made several behind the scenes enhancements that may include improvements to stability, performance, and/or internal or unreleased features.
1946 / 1948 / 1950 Release - 2020-01-08
| Area | AgilOne JIRA | Description of functionality after the fix |
|---|---|---|
| 360 Profiles | AGO-12697 | The 360 Profiles API now only returns a 404 error if the source customer number does not exist. |
| 360 Search | AGO-12668, AGO-12721, AGO-12816 | The 360 Search page can now be customized per tenant. Any customer-level and/or attribute-level attribute can be added custom to the 360 Search application. |
| Actions | AGO-12094 | In Actions we now hide previously selected values from the lookup dropdown. |
| Actions | AGO-12720 | When using Actions to push an audience to an SFTP, you can now specify both a relative and full output folder path (i.e. directory structure). To specify a full folder path, begin the path with a ‘/’. To specify a relative folder path, do not begin the folder path with a ‘/’. |
| 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+ | AGO-12604, AGO-12657, AGO-12672 | With this release we introduced several UI/UX improvements to Campaigns+. |
| 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. |
| Coupons | AGO-11814, AGO-11995, AGO-12520, AGO-12603, AGO-12635, AGO-12636, AGO-12637, AGO-12642, AGO-12643, AGO-12651, AGO-12653, AGO-12653, AGO-12677, AGO-12694, AGO-12703, AGO-12705, AGO-12709, AGO-12719, AGO-12724, AGO-12731, AGO-12756, AGO-12757, AGO-12769 | In addition to multiple destinations, significant effort was spent over code freeze adding our coupon distribution features to Campaigns+. If you use coupons in your marketing efforts, you can now use AgilOne Actions to assign individualized, single-use coupons to customers and then distribute the coupons to those customers. Once AgilOne has a detailed history of coupon distribution, you can use Actions to remind customers about outstanding coupons, or retarget them with the same coupon across engagement channels. |
| 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. |
| SFMC Input Connector | AGO-12768 | We fixed a bug in the SFMC input connector that was causing unsubscribed emails to not properly map to an unsubscribed (DNE=Y) status in AgilOne. This occurred because SFMC’s data and their documentation were not in sync. |
In addition, we have made several behind the scenes enhancements that may include improvements to stability, performance, and/or internal or unreleased features.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you encounter any errors, contact Acquia Support.