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