Loading...

1952 / 2002 Release - 2020-01-28

AreaAgilOne JIRADescription of functionality after the fix
ActionsAGO-12457, AGO-12826When adding Content to an Actions Campaign users were previously prevented from adding two attributes with the same name, for example customer address1 and closest store address1. This was because in the backend we identified these two items with the label ‘address1’. We have improved this behavior so that you can now add two attributes with same name. Attributes are now identified by the source entity name and column name, so in the previous example the new labels are customer_addres1 and organization_address1. You still cannot combine two content models from the same source, for example closest store address1 and primary store address1.
ActionsAGO-12630For clients that ingest payment method (i.e. tender type) information into AgilOne you can now use the ‘Purchased a Product’ Actions filter to refine by details of both the payment method and payment method to transaction cross-reference. We plan to add these refinement options to other filters and content models once we can prove success with ‘Purchased a Product’ first.
ActionsAGO-12759, AGO-12767

To help delineate campaign activity filters, and better enable the use of both filters in a single Campaign+, we have renamed the following filters:

  • Were included in AgilOne audience to Were included in an AgilOne Campaign+ audience
  • Were included in an AgilOne campaign to Were included in an AgilOne legacy Campaign
  • Were included in an AgilOne campaign and variant to Were included in an AgilOne legacy Campaign and variant

Furthermore, we have disabled the Were included in AgilOne audience and segment filter as it is duplicative with the Were included in an AgilOne Campaign+ audience filter.

ActionsAGO-12837In 1950 we accidentally introduced a bug to Actions Campaigns that caused the SFTP output folder path to be ignored after a user saves the campaign if multiple destinations has not been enabled for the tenant. This has been fixed.
Actions Campaigns+AGO-12824Previously a Campaign+ could become corrupted if an attribute used in Segment Builder was removed from Segment Criteria. We no longer allow you to do this behavior. You must first remove attributes from Segment Builder before you can remove them from Segment Criteria.
Actions Campaigns+: Complex Segmentation CriteriaAGO-12157, AGO-12779, AGO-12809, AGO-12814, AGO-12815, AGO-12822A significant amount of time was spent this release enabling Campaign+ segmentation by attributes that do not exist in customer summary. This enhancement will enable you to use Segment Builder to segment by machine learning segments, household attributes, closest store details, primary store details, and on-demand aggregations (i.e. calculated content) such as ‘Revenue in a time frame’. For now we are only enabling segmentation by machine learning segments. Once we have proved efficacy we will enable segmentation by the additional options listed above. Please let your Customer Success Manager know how you would like to segment your audience in Segment Builder.
Actions legacy CampaignsAGO-12843With the previous release we accidentally introduced a bug for legacy campaigns. If you changed the channel of the campaign it would not be pushed to the new channel, but the old one. This has been fixed.
DW Tracker APIAGO-12634With this release we are introducing new beta functionality within our DW Tracker API. If you have first party customer data without a source system, and therefore cannot build a Source Customer Number to uniquely identify the record, you can now ask AgilOne to generate a Source Customer Number for you. If you pass an event of type ‘a1CreateCustomer’ the DW Tracker API will respond with a UUID that you can use as the Source Customer Number to uniquely identify the individual customer. Please do not use this functionality without first speaking with the AgilOne Product and Services teams.
EuroMessage Input ConnectorAGO-12770We have improved our Euromessage Input Connector to be more robust in how it handles bad or corrupt data. Instead of bad data causing the whole process to fail, we now skip/ignore records with corrupt data.
Interactive QueriesAGO-11544AgilOne can now push custom tables, not owned by the platform, to Metrics and Interactive Queries for analytics use cases. This enables us to push intermediate machine learning and IRE tables to snowflake for further analysis.
PlatformAGO-12836Stub parent product category records were being created with an incorrect Source Category Number. This has been fixed, so that auto-generated parent product category records now have the correct Source Category Number.

In addition, we have made several behind the scenes enhancements that may include improvements to stability, performance, and/or internal or unreleased features.

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.

Acquia CDP Support
Back to Section navigation
Back to Site navigation