Currently a work in progress…
| Area | AgilOne JIRA | Description of functionality after the fix |
|---|---|---|
| Actions | AGO-10824 | For clients whose customers have favorite products that they buy multiple times (e.g. single-use items, food, etc.), we have built a new content model that exports each customer’s favorite products from Actions. This “favorite products” content model calculates and exports product details for each individual’s favorite 6 products. A ‘favorite product’ is a product that the customer has purchased more than five times and in greater quantity than any other product (we rank by highest quantity purchased). If an individual has purchased two products in the same quantity, the content model breaks ties by then ranking by sale revenue. This insures that higher value products will win over lower value products when purchased in similar quantities. |
| Actions | AGO-10895 | To improve campaign performance, better align Actions with Metrics, and to make available for use AgilOne calculated attributes/summaries at the transaction level (e.g. master customer transaction sequence), we have migrated most Actions audience filters and conent models from reading AgilOne’s data warehouse tables (transaction & transaction item) to reading AgilOne’s business intelligence table (transactionsummary). The filters and models affected are: - Purchased a product - Purchased a product in a category - Last Products Purchased Users should see improved performance with these filters and content models, however every transaction and transaction item attribute may not yet exist on transcationsummary. If you feel that you are missing a transaction or transaction item attribute in these filters, please reach out to your customer success manager to have the attribute promoted. Thank you! |
| Actions | AGO-10999 | As part of our continued efforts to make refining by product categories within Actions easier, we updated several Actions audience filters to include refinements on products, product categories, and the product category hierarchy. The product category hierarchy means that you no longer have to explicitly list every product category you would like to refine by. Where previously an Actions user who wanted to refine by Men’s products needed to include in the refinement: ‘Men’s tops knit’, ‘Men’s bottoms jeans’, ‘Men’s socks’, etc., now you need only to enter ‘Men’s’ and Actions will automatically traverse the product category hierarchy to grab and include every descendant category. The audience filters affected are:
While this effort makes including descendent categories significantly easier than before (you now only need to select one parent instead of all descendants), it does slightly complicate excluding descendent categories. To exclude a product category, please exclude the category on “product category hierarchy” instead of “product category”. If you exclude product categories on product category, then Actions will still traverse down the product category tree from a different parent (or grand parent) to grab the descendant category. Today’s behavior is now reversed from before, where excluding a single category does not exclude its descendant categories. You have to explicitly list every descendant category that you want to exclude. In summary, include categories using “”product category”” and exclude categories using “”product category hierarchy””. We hope to visualize the product category tree in the future so that including and excluding product categories is less confusing and easier to accomplish. |
Acquia CDP