| Area | AgilOne JIRA | Description of functionality after the fix |
|---|---|---|
| Metrics | AGO-9070, AGO-9106, AGO-8858, AGO-8913, AGO-8977 | New Cube UI |
| Actions | AGO-9007 | Actions SFTP campaign now allow you to pick the exported file name ! In the “Destination” step of your campaign setup, you will see that any new campaign will have the field “File name” populated with the name of the campaign 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 campaign runs, but feel free to uncheck it if not required. Note that if you or your team export(s) multiple campaigns (or the same campaign 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 campaign. |
| Actions | AGO-6266, AGO-9087, AGO-8833 | We expanded the capabilities of our “Distance to store” computations. You can now use the filter “Distance to a store” to select any customer living within [N] miles of store [ABC], e.g. : select all customers with distance to store [San Francisco store] is less than [20] miles, to send them an email about an event going on in that specific store. This has a few limitations for obvious reasons : we support distances of up to 40 miles (greater distances are considered useless by most retailers, since not a lot of people would make such a long trip), and we compute the distance to the 20 closest stores for each customers, so if there are more than 20 stores within a 40 miles radius around a given customer, we will only compute the distance to the closest 20. |
| Platform, Actions | AGO-8283 | UK clients : we partnered with a zipcode data provider for the UK, which enables us to now support the “Closest Store”, “Distance to closest store” and “Distance to a store” filters and dimensions in Actions and Metrics for UK addresses. Note that you need to send those addresses to AgilOne with the CountryCode column set to “GB” (the standard ISO Alpha-2 code), otherwise we will default them to US/CA. |
| Actions | AGO-8738 | The Actions filter “Performed a campaign activity” was renamed to “Performed an activity with message” to more explicitly the fact that it will only include customers who performed an event tied to a marketing campaign. See documentation for “Performed a campaign activity”, this doesn’t change the behavior of the filter itself. We also added a lookup on that filter, to make it easier to pick the “Type” of event without having to remember the existing types by heart. |
| Platform | AGO-9004 | We now support PGP/GPG encryption on top of ZIP/GZ compressed files. |
| Metrics, Actions, 360 Profiles | AGO-8967 | AgilOne clients can now request a specific landing page for their tenant. For instance, if you have a dashboard that your time should always check, AgilOne can make it the default landing page for your tenant ! Note that this is tenant-level, not user-specific so your entire team will get the same landing page. Please contact your AgilOne team to set this up. |
| Platform | AGO-8961 | AgilOne now supports configuring standard timezones for the data ingested via SFTP/S3 connectors, so that your data can be fully converted to UTC for our platform calculations. The standard timezones are the same as what Java 1.8 supports. |
| 360 Profiles | AGO-8948 | We made the product attribute ImageURL available in 360 Profiles, under the Transaction card : when you expand a transaction, under each item you will now see a “Product Image” attribute with the URL surfaced as a link (you can click on it and get the image of the product that you sent to us). This change also applies to the 360 Profiles API, so you can start leveraging this image as part of any application you build on top of that API. |
| Actions | AGO-8852 | We added the attributes “SourceProductNumber” and “SourceProductCategoryNumber” to the available refinements on any event-related filter in Actions (e.g. “Performed an event in a time period”, “Performed an activity with message”, etc…). |
| Machine Learning Models | AGO-8376, AGO-8468, AGO-8675, AGO-8680, AGO-9071 | AgilOne’s Behavioral Clustering model is now available to all clients ! This model enables you to get customer segments generated by our machine-learning algorithms based on patterns found in your customer’s behavior. Using a clustering model running on 30+ behavioral features computed by AgilOne (e.g. AOV, tenure, recency, frequency, etc…), the algorithm groups together customers which have shown the same purchasing behavior. It produces between 3 and 8 such clusters (depending on your data), which your AgilOne team will then review with you the results to ensure that they make sense for your business and for you to name them for easier use later. Those clusters are available via Metrics (for reporting), Actions (for executing campaigns based on that information) and 360 Profiles (to see which type of customer you are looking at). |
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)