Loading...

1727 Release - 2017-07-17

AreaAgilOne JIRADescription of functionality after the fix
ActionsAGO-8897We added a lookup to the organization names fields in filters like “Closest store”, “Distance to a store”.
ActionsAGO-7172, AGO-8314, AGO-9182Following popular demand, we added 3 new filters in Actions to make it easy to select certain audiences : “Performed a Number of Events in the Timeframe”, “Purchased a Number of Products in a category”, “Made a Number of Transactions in a Timeframe”. All of those filters work in a similar way as their existing counterparts without “a Number of” in the name. The added functionality is to allow you to enter a number of times such event/transaction/product happened/were purchased and filter based on that.
Platform, DQEAGO-6973We 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.
MetricsAGO-9208The functionality “Connect from Excel” used to pass the wrong OLAP cube connection parameters. We fixed it and the functionality now works again as expected.
ActionsAGO-9129In 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.
Metrics, DashboardsAGO-9090We fixed a small display issue which used to show a “chart not configured” image on top of the charts of a dashboard.
PlatformAGO-7458Performance improvements - do not load past data if nothing new happened

Did not find what you were looking for?

If this content did not answer your questions, try searching or contacting our support team for further assistance.

Back to Section navigation