We have squashed a bug that broke the functionality of the following audience filters:

• Purchased a Number of Products
• Made a Number of Transactions in a Timeframe

These filters should now work as expected. Please work with Support to recreate any campaigns that were created over the last two weeks with these audience filters.

We have created two new Actions audience filters:

• Performed an event with a campaign - allows an Actions user to segment an audience by any behavior linked to a marketing campaign. Previously only message-level metadata was available for refinement, now campaign and dispatch level metadata is available for refinement.
• Performed an event with a product category - allows an Actions user to segment an audience by any behavior linked to a product category, such as product category browse or like events.

To support AGO-11120 we have added two new customer summary attributes:

• Closest Store ID
• Primary Store ID

While Primary Store ID is available out of the box for existing clients, Closest Store ID requires that AgilOne reset an incremental cache within our data processing pipeline. Resetting this cache could cause the subsequent nightly refresh to run longer than normal and thereby impact morning campaigns. Therefore, this effort will be performed on an ‘as needed’ basis. If you would like to utilitze Closest Store ID, please reach out to the AgilOne help desk or your Customer Success Manager to schedule an appropriate time to reset this cache, causing a slightly delayed refresh, but resulting in a Closest Store ID being properly calculated and exposed. Thank you!

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:

• Placed first transaction
• Placed last transaction
• Customers who spent certain amount in a timeframe
• Made a Number of Transactions in a Timeframe
• Purchased a Number of Products

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.

AgilOne now supports for real-time data flows. As you already know, the WebTag data (and any data sent to the underlying Tracker API) gets to our system in real-time. We now added the following functionality (requires a setup for each tenant, please check with your CSM) :

• 360 Profiles and 360 API : any event or transaction that happens for a known customer will now be displayed/served in real-time by 360 Profiles/360 API. The application will automatically update itself to show those events/transactions as they come under that customer’s profile in 360 Profile.
• Actions campaigns with SendGrid or SFTP integration : with a small additional setup, certain campaigns in Actions (based on events or transactions) can now be executed as frequently as every 15 minutes. This is interesting in particular for near-real-time campaigns like Abandoned Cart or Follow-up after purchase, etc… Note that this is available only with SendGrid or SFTP execution channels because other channels do not guarantee the immediate loading of the data we would send to them (SLAs are usually around the hour), defeating the purpose of this new capability.
• Important note : this capability only supports “pass-through” data with very minimal processing (to be as fast as possible). Processing like DQE (deduping, validation, etc..) and computations like “lifetime value” (and any other KPI/metric, including ML models) will not happen as part of this “real-time” flow. They will be executed as usual, during the next regular data flow. In particular, this means that any customer, product, address and message not already processed (e.g. new customers) by AgilOne in the previous batch cannot be displayed/served in real-time.