| Area | AgilOne JIRA | Description of functionality after the fix |
|---|---|---|
| 360 Profiles | AGO-9923, AGO-9842, AGO-9827, AGO-9811, AGO-9810, OPS-34855, OPS-34617 | We improved the 360 Profiles UI to display information in a nicer, more organized fashion. You can see the same information in tabs and “cards” (under the Profile and Household tabs in particular). This new UI is even more modular, as it enables us to configure everything we need to support custom events, custom attributes on any standard entity, display images of the products that have been purchased, display Household-level information and members (this is turned off for most clients, please reach out to your CSM if you would like this functionality), etc… This new UI has been rolled-out and validated by each client during an “Early Adopter Program” (EAP) to ensure all tenant-specific configurations were working properly with the new layout. Note that from now on, the old 360 Profiles UI is considered deprecated and no existing nor new AgilOne tenant will get this deprecated UI. |
| Actions | AGO-9726, AGO-9725, OPS-35681 | In line with our recent 360 Profiles improvement to surface Household-level information, we have also added a new filter called “Belongs to a Household” in Actions (located under the “Household” folder in the filter list). This filter is a bit different from the existing ones : it enables you to select all customers that belong to a household that fulfills certain conditions. Those conditions are defined by you, using refinements on that filter (this filter doesn’t have any primary filtering value : it basically selects every customers unless you add refinements to filter on the household attributes, e.g. AOV of the entire household, Lifetime value of the entire household, etc…). For instance, you can now select customers who belong to a household where the (household) AOV is greater than “$500”. This is interesting when you want to target more broadly customers in certain households (e. g. low-spenders in a household of high-spenders could be an upsell opportunity). |
| Metrics, Reports | AGO-9860 | This is a security fix for emailable reports. Previously, users could actually send reports to recipients that were neither part of AgilOne nor had access to that specific tenant. This created a risk, in case a client’s employee emailed reports to personal addresses or other non-authorized recipients. This has been fixed : to be able to email a report to a recipient, that recipient needs to either be an AgilOne employee or have access to your tenant directly. Please request access to the tenant for those recipients if they do not have access already and should receive those reports. Please also note that we do not allow sending reports via email to any address on the following domains : Yahoo, Hotmail, Outlook. |
| Metrics, Reports | AGO-9788 | A small UI fix to enable emailed reports to render properly on mobile devices. We now have validated support for the following email clients and devices :
|
| Actions | AGO-9503 | The History UI allowed users to see the status of historical data exports run by other users. This is an inconvenience and we made sure it doesn’t happen anymore. |
| Data Export | AGO-9640 | We now allow users to re-order the attributes they are sending via Data Export (via drag & drop within the list of attributes in the “Content” step). For reference, this order used to be the order in which the attributes had been added in the Content step, and this was inconvenient for most clients so we changed that. |
| Actions | AGO-9779 | We fixed a small bug that made the Actions filters “Revenue Decile” unusable. You can now enter any decile number (i.e. any integer between 1 and 10) and select your audience this way. The reason for the bug was a discrepancy between the UI (groups of deciles had to be selected) and the actual values in the backend (pure integers, without groupings). |
| Metrics, Cube Reports | AGO-9791 | The UI to select values for filters in Cube Reports has been improved : it now allows you to select the top-level of a hierarchical dimension (and it will select all sub-levels automatically for you) instead of having to select all sub-levels individually. |
| Metrics, Template Reports | AGO-9793 | You can now easily enter multiple values in Template Reports filter, via copy/paste. For instance, if you have a list of values in an excel file that you would like to filter the report on, simply click the “hamburger” icon next to the filter input field in AgilOne, then copy paste those values into the pop-up. Note that you should ensure that you have one value per line (commas and other characters will be considered part of the value you are trying to filter, so be careful), and up to 50 values. |
| Actions | AGO-9818 | The Actions filter “Purchased a number of products” had an issue where it was not taking the date/time filter into account. We corrected that and it now behaves as expected. |
| Platform, Bronto integration | AGO-9872 | We reduced the timeframe for our Bronto integration : the historical data pull will now backtrack 30 days from the date the integration is created by your IPM. |
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)