| Area | AgilOne JIRA | Description of functionality after the fix |
|---|---|---|
| Actions | AGO-8727 | We fixed a bug where some products from the “Last Purchased Products” content model (in Actions > Content) had the same rank (aka “pitem__limit_count”) when they were extracted to an ESP. The new ranking will not have those duplicate ranks, allowing you to construct unique keys on this data in your ESP (to ensure you never send duplicated products in an email). |
| Platform, SFTP integration | AGO-9405, AGO-9539 | We now support timezones along with custom date formats. Please check with your AgilOne implementation team to see the details of the formats we don’t support (note : we support all standard formats already, so you should be covered in 99/9% of the cases). |
| Actions, SendGrid campaigns | AGO-9417 | We solved a UI issue in Actions (only applicable to SendGrid campaigns), where the “Track with GA” functionality didn’t respect the ON/OFF switch and was always ON. This is now working as expected. |
| Metrics | AGO-9432 | When switching a report from columns to rows in Metrics, you would get an extra empty column. This was a UI issue and has been fixed in this release. |
| ActMetricsions | AGO-9551 | We improved the cube reports UI and fixed a batch of smaller UI issues (in particular with sorting values in the reports). |
| Metrics | AGO-9574, AGO-9469, AGO-9492 | Whenever someone gives you a report ID (or dashboard ID), you can go directly to that report (or dashboard) by following the URL [host]/ report/[putReportIDHere] ([host]/dashboard/[putReportIDHere]). This is designed to make it easier to find & share reports across team members. |
| Metrics, Template Reports | AGO-9622, AGO-9623, AGO-9211 | While the functionality to export Template Reports to an SFTP was released in 1713, it didn’t allow you to specific the name of the file you wanted to get so far. This has been improved, and the application now allows to specify the file name, as well as append the date if this is a recurring report (and you want to avoid overwriting past files). In the “Destination” setup of your report, you will see that any new report will have the field “File name” populated with the name of the report by default. You can change that to any name you prefer (or leave it as is). Note that certain special characters are to be avoided (list provided in the UI), and you can include a full UNIX-style path starting from the root of the SFTP that your user has access to (using slash /, e.g. File name = “MyFolder/MySecondFolder/ExportedFileName”). The “Append date” checkbox is checked by default to automatically append the date and time of the extract to the file name every time that report runs, but feel free to uncheck it if not required. Note that if you or your team export (s) multiple reports (or the same report multiple times) with the same file name, the last one will overwrite any previous execution so the file will contain only the extract for that last report. |
| Actions | AGO-8315 | We added two new filters in Actions, called “Customers who spent certain mount in a timeframe” and “Customers who spent certain amount in a transaction”. Those filters are useful to select people based on the amount of revenue they spent, respectively within a specific timeframe (e.g. “spent more than $300 in the last 30 days…”), and within a single transaction (e.g. “spent more than $500 in a single transaction in the last 30 days…”). This was not possible before, and will allow selections of VIP customers more easily (for instance). |
| 360 Profiles | AGO-9173 | Following the split of the “Preferences” field into DoNotEmail/DoNotCall/ DoNotText/DoNotMail (release 1731), we are now surfacing those fields instead in 360 Profiles (in the new UI, release 1733). |
| Metrics, Cube Reports | AGO-9175 | Following the split of the “Preferences” field into DoNotEmail/DoNotCall/ DoNotText/DoNotMail (release 1731), we are now surfacing those fields in their separate dimensions in Cube Reports within Metrics. This way, you can now report on the number of customers that you can contact via the various channels, giving you a more accurate view of the potential reach of your marketing campaigns in the future. |
| Platform, Google Analytics Integration | AGO-9553 | We changed the backtracking of our Google Analytics (GA) integration to pull the last 2 years of past data. |
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Fri Sep 12 2025 14:51:16 GMT+0000 (Coordinated Universal Time)