| 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.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Fri Sep 12 2025 14:31:48 GMT+0000 (Coordinated Universal Time)