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.

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.

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.

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

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.

360 Profiles

AGO-9674, AGO-9838

360 Profiles used to duplicate the first data elements of certain collections (addresses, transaction items) on certain tenants, instead of rendering each element separately. This was a bug in the way the UI rendered repeating child elements (the structure you can see on addresses in the Identities tab, or on the Transaction items in the Transactions tab). We fixed it and all elements are now rendered as expected.

Metrics, Reports

AGO-9750, AGO-9749, AGO-9550, AGO-9471, AGO-9359, AGO-9358, AGO-9357, AGO-9476, AGO-9475

You can now email yourself and your collaborators a visualization of Cube or Template Reports you created ! The feature can send an email with report details to multiple users on a schedule. This functionality can be accessed via the “Delivery” tab for Cube Reports or “Summary” step for Template Reports. Please reach out to your AgilOne CSM to enable this feature.

360 Profiles

AGO-9676

A batch of small improvements to clarify the new 360 Profiles UI.

Actions

AGO-9704

We updated the lookup on the filter AOV to be dynamic instead of static (like it used to be). This way, any configuration that was done on the AOV bucketization for your tenant will automatically be reflected there.

Platform

AGO-9683

For clients that have a tenant configured to compute customer summaries by including only Demand/Cancel/Returned transaction items (for instance, or other similar configuration), we fixed an issue where some of the computations were not honoring the configuration (they were still computing only on Shipped/Returned items).

Metrics, Cube reports

AGO-9638

We added an option in the drop-down menu (on the reports listing page), called “Report Details” : this will show you all the measures, dimensions and filters used by your report without trying to load it (thus, saving a lot of time). It enables you to quickly find the report you were looking for.

Actions, Platform, NCOA

AGO-9579

This applies only to clients that have NCOA enabled for their tenant (US and Canada only) We are now surfacing NCOA processing attributes as part of Actions filters (under the “Customer Summary” folder in Audience filters). This enables you to easily select all customers who have recently been processed through NCOA, and select only the ones who moved recently (for instance), or by move type as well. Here are the new filters, and their capabilities :

• NCOADateUpdate : this is the date at which the record last went through NCOA processing. This is currently in a UNIX epoch format (e. g. “1507060487001”), but we will soon release a “human-readable” translation (e.g. YYYYMMDD format) of that filter.

• MoveType : this is the type of move that was registered within the USPS NCOA database. The possible values are : I for Individual Match, F for Family Match, B for Business Name Match.

• MoveDate : this is the date at which the move was registered with USPS in the NCOA database. This is in the format “YYYYMM”, e.g. “201401” is a move that was registered on January 2014 (the actual move could have happened earlier or later, the NCOA database cannot provide that information).

Actions

AGO-8639

The filters “Placed first order” and “Placed last order” were not working correctly : they were looking at the first/last transactions of customers prior to deduping, instead of considering the master customer profile (ie after deduping). We had retired those filters while correcting this behavior, and we are slowly enabling those filters again for specific tenants (please contact our AgilOne CSM if you are looking to use those filters).

Actions

AGO-9493

When selecting an audience for your campaign, the “IN” operator was not working when the values had single quotes in them. This bug was fixed, and everything is now working as expected.

360 Profile

AGO-9540

The 360 Profiles Journey search functionality was unable to retrieve results whenever multiple words were entered in the Event Type field. This is now working as expected.

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

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.

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

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

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.

360 Profiles

AGO-9318, AGO-9319, AGO-9317, AGO-9315, AGO-9279, AGO-9385, AGO-9449, AGO-9463, AGO-9499, AGO-9194, AGO-9217, AGO-9418, AGO-9184, AGO-9186, AGO-9187, AGO-9188, AGO-9189, AGO-9190, AGO-9191, AGO-9192

We are releasing a completely redesigned UI for 360 Profiles ! The new UI will not only make browsing & finding information quicker and more intuitive, it will also provide more specific data points about your customers (e.g. the number of transactions per sales channel, the type of events they experienced in their customer journey, etc…). Additionally, it will support more configurations use cases. We will roll this out to all clients in phases, and your AgilOne CSM will be in touch with you when we are ready to deploy it for your tenant.

Actions

AGO-9313

Creating Actions campaigns with multiple values in a filter got much easier : we added a way to copy/paste a list of values from elsewhere into the UI for filters that support the “IN” comparison (ie the ones that accept list of values). On such a filter, when using “IN”, you will see a new button to the right of the entry field. Clicking on that button will pop-up a small window where you can copy/paste values (one value per line, no commas/quotes between the values), up to 50 values per filter. As usual with the filters, the UI will not validate the values you enter in that field, so please be careful when copy/pasting values to make sure they are all correct.

Facebook Integration

AGO-9049

We added retries to our Facebook integration, so that whenever the Facebook API returns errors, we now wait 10 min and retry sending the campaign. We will retry 10 times at most, after which the campaign will fail. This means that some campaigns will take more time, but will succeed instead of failing because of the Facebook API errors. Contact helpdesk@agilone.com if you still encounter failures in your Facebook campaigns.

Metrics

AGO-8855

Metrics cube reports can be sorted, and now the sorting will be saved along with the report if you hit “save”.

Actions, SFTP Extracts

AGO-9280

We now support spaces in folder and file names.

Integrations

AGO-9330

AgilOne now integrates with EuroMessage (ESP), to pull the email activity of your customers (sends, opens, clicks, bounces, etc…).

Actions, Facebook integration

AGO-9369

With some recent changes in the Facebook API’s authentication flow, we realized that newly created accounts (or accounts that had not yet linked their Ad Account with AgilOne) were not authorizing our integration. We fixed this, and the Faebook integration now works well with any account.

Platform, Data feeds

AGO-8944, AGO-9012, AGO-9168, AGO-9169

We made various improvements to the logic we used to pick the best attributes for mastercustomer records from each of their child records (from different source systems).

We also split the existing “Preferences” field into 4 different fields : DoNotEmail, DoNotCall, DoNotText, DoNotMail. Those represent the same type of “optin/optout” tracking for each customer, with the same allowed values, but splitting them makes it easier to manage complex use cases when merging records from different source systems. It also allows a much more granular control over how each customer’s preferences are surfaced at the mastercustomer level after deduping.

The documentation for the standard Customer feed has been updated to reflect this change. Along with that change, we are deprecating the “Preferences” field in the standard feed. However, you do not need to change your existing feeds, please review the feed documentation for more details.

Data Export

AGO-7856

Data exports that were already exported successfully would fail if you tried to change the columns you want to export. This is now fixed and columns can be modified even after the data has been exported.

Platform

AGO-8577

Various improvements to the way we tie transactions to the data we receive from our Google Analytics integration.

Metrics

AGO-9134, AGO-9301, AGO-8589

Various UI improvements for our template reports, so the reports look nicer and can be saved with the sorting/column dimensions that you setup.

Metrics

AGO-9193

Cube reports will now be saved with the latest sorting you picked. This way, you can open your reports in the future and they will display exactly what you wanted.

Actions

AGO-9022

Campaigns used to be marked as failed if there was no audience for that execution (ie no customer matching the criteria for that campaign). This was creating a lot of false-negatives, making it look like the campaigns indeed failed even though they actually succeeded. This has been fixed : campaigns that extract 0 records but were successfully processed will be marked as successful (and you can see in the History for that campaign that 0 records were extracted).

Actions

AGO-9255

BirthDate has been added as an available filter and personalization attribute in Actions.

Actions

AGO-8897

We added a lookup to the organization names fields in filters like “Closest store”, “Distance to a store”.

Platform, DQE

AGO-6973

We improved the way we treat secondary address information (the “Address2” field), to increase the accuracy of the address validation process and recognize better Unit/Suite numbers in the full address. This change will typically improve the percentage of validated addresses by 5 to 10% in the US/Canada for your data.

Actions

AGO-9129

In the past releases, we made performance improvements to all the underlying data processing of Actions. This release applies those enhancements to Audience Counts (the “refresh” button on the “Audience” step when creating/editing a campaign) so they became much faster to return counts for large campaigns.

Platform

AGO-7458

Performance improvements - do not load past data if nothing new happened

Metrics

AGO-9070, AGO-9106, AGO-8858, AGO-8913, AGO-8977

New Cube UI

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.

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.

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.

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.

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

Metrics

AGO-8813, AGO-8935, AGO-8936, AGO-8779, AGO-8801, AGO-8827, AGO-8839, AGO-8873, AGO-8883, AGO-8885, AGO-8895, AGO-8605, AGO-8959, AGO-8908, AGO-8870, AGO-8875, AGO-8912

AgilOne now supports Dashboards! Dashboards provide the ability to create a visual representation of a collection of reports. They can be accessed via the Metrics menu. To add a report to Dashboards, start by creating your Cube or Template Reports and configuring charts for your respective reports. After your reports are successfully executed, go to Dashboards via the menu to create a new dashboard. When creating a new dashboard, click on Add Tile followed by the + sign (within the tile) to add charts or grids from your previously executed reports. Each dashboard can have up to 10 tiles and each tile can represent the grid or chart from one report. You can also download PDF or PNG versions of your dashboards after saving them.

Integrations, Actions

AGO-8042

AgilOne now integrates with Oracle Bronto (ESP) for pulling email activity data, as well as pushing audiences & attributes to Selligent to enable campaigns leveraging AgilOne augmented data.

Platform, Actions, Metrics, 360 Profiles

AGO-8543

We identified and fixed a bug in the way PrimaryStore was computed.

Platform

AGO-8531, AGO-8773

We found a corner case where, if the Last Name of a customer was NULL and the First Name was not NULL, the validation & genrization code would output that record with a Last Name containing the First Name, a NULL First Name and a NULL Gender. This had a very small impact (small number of such records), yet the incorrect Gender could lead to missing certain customers when executing campaigns. We fixed this and our validation component now outputs the expected values, as well as the proper genderization.

Actions

AGO-8755

We exposed the DPV Confirmation results that we get from USPS for US addresses in Actions as a filter and content for your campaigns. The new filter is called “DPV Confirmed”, and can take the values “Y” (when the address is DPV confirmed) and “N” (when the address is not certified).

Actions

AGO-8605

The Actions campaign listing page now displays at a glance whether the campaign is scheduled as well as its last execution status and date/ time. The schedule will display “-” if no schedule exists on that campaign (either already went through that schedule, or never scheduled) , “ONCE” if it is scheduled to run once in the future, “DAILY”/”WEEKLY”/ “MONTHLY” based on the frequency of the schedule. The Last Execution Status will display the current/latest status of the campaign using icons (for failed, running, succeeded statuses), and the date/time is the date/time at which the campaign entered that status (e.g. the execution time if the campaign is currently running, or the processing end date/time if the campaign succeeded). For our SendGrid integration : note that this execution status and date/time does not cover any test that was run through the “Test Email” functionality.

Actions

AGO-8667

Minor reorganization of the event and campaign-based filters into specific folders.

Actions

AGO-8561

You can now refine the filters “Email Activity > Performed an event in a time period”, “Web Activity > Browsed a Product”, and “Web Activity > Abandoned their cart” by the following attributes :

1. UserClient : this is “A” for events that happened on your mobile application (if you are sending us such events), and “B” for events that happened on a regular browser.

2. Domain : this lists out the domain on which the specific event have happened, which can be useful for filtering the events if you use a lot of subdomains for marketing purposes or special sales and don’t want to target people that browsed on those websites.

3. OperatingSystem : as its name indicates, this is a high-level summary of the operating system of the visitor. It can help you seleect specific segments of users based on their device/OS.

4. DeviceType: as per its name, this is a very high-level summary of the device used by your visitors. It can help you segment further the people you want to target/avoid targeting for your campaigns, based on the device on which those events happened.

Data Export

AGO-8327

We found an issue where a recurring Data Export was not exporting the MasterCustomer entity. This was due to a timing issue, as well as an optimization on the modified date of each record in that entity. We fixed this, and all recurring Data Export will behave properly now.

Actions, SendGrid integration

AGO-8157

Some email contents & titles were incorrectly categorized as “spam” by our Spam Score functionality. This was due to a small glitch in the UI as well as some arbitrary stringent (provided by Spam Assassin) on the ratio of spaces to letters that made little sense to enforce. We reworked the rule and reviewed our Spam Scoring against the leading Email services (Litmus, Postmark, Spam Assassin, etc…) and confirmed that we are 100% aligned with them. THose issues are therefore fixed and you can use our Spam Score feature with confidence.

Actions

AGO-8529

When creating an audience, the “IN” operator was not working, we fixed that.

Data Export

AGO-8596

When running a new data export, the status was typically setting itself to “FAIL” even though the export was still running (and not failing at all). We fixed that and it now correctly displays the proper status : “RUNNING”.

Platform

AGO-8600 & associated

We added Silverpop as a PUSH and PULL connector capability in the standard AgilOne platform. Please check with your AgilOne Implementation team if you would like to take advantage of this.

Metrics

AGO-8316

The dimension “Customers - Days since last web visit” was indicating that all customers had browsed the website today, which is obviously incorrect. We fixed the computation.

360 Profiles

AGO-8475

On smaller screens (less than 960px wide), clicking on the profile of a customer in the 360 Profiles app didn’t do anything. This was caused by an incorrect frame size which was blocking any clicks on the bottom half of the page. We fixed this and any screen size is supported now.

Actions

AGO-8540 & associated

We improved the design of the Actions campaign listing page to make it easier to use. It now displays the latest status and execution of every campaign, as well as a quick reminder about what campaigns are scheduled and at what frequency. This is designed to get the most important information about a campaign at a glance but if you need more details, you can obviously open the campaign an navigate to see the full details of the setup.

Platform

AGO-8282

Our DQE (Data Quality Engine) now validates addresses from the UK, on top of the countries we already supported (US, CA). Please note that to leverage this capability, you need to make sure you provide a CountryCode value of “GB” for all your UK addresses (ISO Alpha-2 standard, like all other CountryCodes), otherwise they will be considered as US addresses by default and checked against the USPS database instead.

Actions, Metrics

AGO-8482

You can now search for reports/campaigns across folders (using the search bar) in Actions and Metrics. Please note however, that this change is not applicable if your tenant has specific folder-level access rights enforced. If you have a doubt, or would like to understand what this means please reach out to your AgilOne team.

Platform

AGO-8371

Data processing performance improvements

Metrics

AGO-8367, AGO-8382

Query-based reports can now be exported to an FTP or an S3 instance, in a CSV format. You can pick the destination in the Summary step when creating such a report. The destination has to be picked out of the list of destination configured for you by your AgilOne Client Success team, so if you don’t have the right destination in the list, please contact your AgilOne Client Success team.

Actions

AGO-8267, AGO-8265, AGO-8264

You can now include/exclude past audiences from your Actions campaigns by using the filter “Email Activity > Were included in a campaign”. The filter requires that you enter a campaign name (it provides a lookup for ease of use), as well as a timeframe in which you want the recipients to have been included in the campaign. Note that this feature is disabled by default, please open a request with your AgilOne Client Success team if you are interested.

Standard Feeds, 360 Profiles

AGO-8275, AGO-8340

We created a standard feed for sending Direct Mail information to AgilOne. In itself, this enables the support for Direct Mail events to be surfaced in 360 Profiles, as well as being used in Actions filters (using the “Performed a Campaign Activity” filter). This is also the first step in enabling future features related to Direct Mail, in particular Direct Mail matchback capabilities. Please contact your AgilOne Implementation Project Manager if you are interested for that feature.

Integrations

AGO-8252

This applies to the CheetahMail-AgilOne connector only. We fixed an issue where email events where duplicated. The data pull was looking at overlapping time windows and therefore pulling twice the same data during every run.

Metrics

AGO-8304

Cube data refresh status shows timestamp of when the cube was last refreshed with the latest data. Available options for the status are: - “Cube data refreshed on “: The cube & calculations have been refreshed with the latest data. - “Cube data refresh failed on “: Please reach out to the AgilOne Support team for further assistance if the refresh failed. - “Cube data refresh in progress”: Please run your report after the cube refresh is completed successfully - “Cube data refresh status not available” : Please reach out to the AgilOne Support team for further assistance.

Integrations, Actions

AGO-8207

AgilOne now integrates with Selligent (ESP) for pulling email activity data, as well as pushing audiences & attributes to Selligent to enable campaigns leveraging AgilOne augmented data.

Platform

AGO-8109

AgilOne has now released the latest version of the Likelihood to Buy model. It enables you to rank your existing buyers in order to know which are most likely to buy in the coming 30 days (based on their previous behavior and the overall behavior of all your customers). For more details, please discuss with your AgilOne Implementation Project Manager.

Data feeds

AGO-8160

The TransactionItem feed now support other types than “Purchase”. This is particularly useful for “Sample”/”Swatch” transaction items, which should not be considered as regular items (ie they should not be considered as a real purchase placed by customers) but you still want to track those to better understand your customers. Metrics and Actions will surface this information as well so you can filter/select customers in your reporting/campaigns based on this information. Be careful : any other type than “Purchase” will NOT be considered in the computation of a customer’s first order date, average order value, last order date, and other metrics.

360 Profiles

AGO-7890

The name and type of organization in which transactions are placed are now surfaced in both 360 Profiles UI and the 360 API. THis makes it easier for you to understand where each transaction was placed by the customer.

Actions

AGO-8263

The Actions UI for SendGrid Email campaigns was displaying a validation message that was unclear when the “Email Subject” field was not properly populated )in the case of A/B testing multiple variants). We fixed this and the message is now clearly stating which variant has the issue.

Actions

(Multiple)

AgilOne now supports audience splits for A/B testing. This applies to campaigns that run on the SFTP or SendGrid Email channels, and it enables you to decide how to randomly split your audience by picking the percentages and the number of variants to create. It also supports hold-outs. More information can be found in Actions’ documentation.

Actions

AGO-8105

The AgilOne Email channel has been renamed to “SendGrid Email”, and the branding has been changed accordingly. This is to reflect more accurately our capabilities and integrations.The features for this channel do not change.

Actions, Metrics

AGO-8070

When deleting a campaign/report in the main folder, users were sometimes seeing a 404 error when trying to add another folder. The UI was actually checking for the most recently created campaign/report when trying to add a folder, which returned the suppressed campaign and caused the error. This check has been removed and this issue is fixed.

Metrics, 360 Profiles, Actions

AGO-7979

The summary calculations for “Customer - Transaction Count - Last 12 Months” and “Customer - Transaction Count - 13-24 Months” were using an incremental logic and were not updating properly on a daily basis. The incremental logic has ben reworked, and the issue is now fixed.

Metrics

AGO-7968

“Customer - Months since last transaction” dimension in Metrics used to show duplicate values for “13 Months” and “24+ Months”. This was due to a labelling issue (display only), where the label was using a rounded-up version of the underlying calculation and the two didn’t match for values corresponding to each year. This has been fixed and no duplicate values are displayed anymore.

Actions

AGO-8121

The scrolling on the Design step was broken in the UI. This is now fixed.

Security

AGO-8119

Password reset had a bad redirection, which prevented users from resetting their passwords. This is now fixed and working as expected.

Actions

AGO-8081

When creating a campaign, saving it, then closing it and coming back to it, a confirmation dialog was popping up even when there were no changes to the campaign. This is fixed.

Actions

AGO-7800

Users were sometimes unable to expand the list of rules on the Audience step in Actions. This is fixed.

Actions

AGO-7991

On the Destination step of Actions, when clients have multiple channels of the same type configured, a default destination is now selected for ease of use.