Our May 10th 2023 release, v2023.09, introduces a number of usability and Event changes. Regarding usability, customers that have been sent a Landing Page and visited it more than 90 days later will now be met with an expired Landing Page screen. This was done for performance and as a safeguard in the scenario they visit it when the context has likely been lost. We have also disabled the modification of the same attribute from multiple places in a Landing Page using Forms or Modify Input Blocks. This has been done because it's illogical to have a particular customer attribute given two values at the same time. We have also disabled the ability to select a date range older than 31 days in Customer Trail, as the Customer Trail does not keep data older than 31 days. Lastly, we have disabled the ability to have duplicated names for Export Column Headers. This is to avoid any potential complications or confusion that could occur as a result of having two values with the same label. Regarding Events, which are what feed your Exports and Customer Trail, we have deprecated the "Bounce Type" Property of the "Email Bounced" Event. This is because it wasn't being populated in the first place, and additionally , it wouldn't provide additional clarity. The coverage of other email Events will inform you of the type of bounce. This has only been deprecated , not deleted, so any existing Exports that utilize it will not be impacted.

Next, we have added the "Failure Reason" Property to the "SMS Rejected" and "Email Rejected" Events to give clarity on why the failure occurred. Lastly, we have added a "Replied to Email" Event, which will allow you to see the contents of the customer's reply. In a future release, this will utilize sentiment analysis. This will require manual configuration to capture the replies, so you may not immediately see the replies.

See the Landing Pages, Customer Trail, Exports, or Events sections of this article for additional information.

See the Bug Fixes section of this article for any additional changes.

Landing Pages

Learn more - Landing Pages

As you have seen based on our recent focus on system performance, it is critical for us to handle the scale that your business brings. Because of this, Landing Pages will now expire if 90 days or more have elapsed since they were sent to a customer. We did not make this decision without deliberation. After analysis, we found that less than 0.02% of customers will access a Landing Page after 90 days.

Additionally, it can act as a secondary guardrail in the event that your page eligibility segment is lenient enough for 90 days to elapse. The other change is that multiple modifications of the same attribute using a Form or Modify Attribute Block are no longer able to be configured. This is to prevent attempting to set an attribute to two different values at the same time.

Accessing the Landing Page after expiration will result in seeing the following page:

Customer Trail

Learn more - Customer Trail

Customer Trail is intended more of an individual diagnostic tool, rather than a complete historical view of customer interactions . Therefore in the February 15th release, we limited it to 31 days of data for the sake of performance. We did not make this change in the date selector, and for the sake of clarity, you will now no longer be able to select a date range going 32 days or more into the past.

Exports

Learn more - Export

Settings Exports are how you move your information out of the platform. To avoid potential confusion, we have now restricted the ability to give two Column Headings the same name. The error you will receive if this is attempted can be seen in the following image:

Events

Learn more - Events

Events feed into your Exports and Customer Trail, to which there have been several changes. The first is the deprecation of the "Bounce Type" Property present in the "Email Bounced" Event. This was not being populated, and wouldn't have provided additional clarity even if it were, as there is no further distinction to be made due to the coverage of other Events. If you did happen to be utilizing this property, it has not been deleted, you will just not be able to select it moving forward. This will have no impact on your existing configuration. Second, is the addition of the "Failure Reason" Property to the "SMS Rejected" and "Email Rejected" Events, which will provide additional clarity on the reason that a provider has rejected to send your outreach. Lastly, we have added a "Replied to Email" Event, which will allow you to see the contents of the customer's reply. In a future release, this will utilize sentiment analysis for big-picture statistics on the type of response that your customers are eliciting. This currently requires manual configuration, so you may not immediately be capturing your customer responses

Bug Fixes