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