We've officially launched our Drupal module, which brings many of the core personalization and content-related features from Lytics directly to your favorite content management system.

Fixed a bug preventing users from being able to right-click and open Data Models in a new window from the list view, as outlined in the attached screenshot below.

We've fixed a bug allowing users to delete their default content collections inadvertently. As per our documentation, those collections will not persist and will continue to facilitate default use cases.

We've officially launched a React Native version of our mobile SDK to support mobile development and use cases further. This SDK leverages both native SDKs (iOS and Android). Full documentation and implementation details can be found here.

A bug was fixed concerning the display of Source and Destination configurations in scenarios where all options were labeled as "Advanced." Specifically, this issue caused the Marketo Source option to appear without any configuration options, preventing the creation of that type of connection. Now, the configurations are correctly populated and capable of handling all edge cases.

We've corrected a bug causing some Source and Destination job configs to highlight optional fields in red and surface them as required when users press Complete. This bug has been fixed, and all Source & Destination configurations should handle required and optional parameters without issue.

Corrected a bug that would cause an "Invalid FilterQl Statement" error when attempting to manage Interest Engines of various types.

We've fixed a bug that prevented the interface from showing the correct count under the Times Seen in all cases within Conductor.

A Source or Destination job may fail for various reasons. Previously, a failed job necessitated a support ticket and manual intervention for a restart, significantly hindering daily workflow. We've recently introduced a feature that adds a "Retry" button directly in the user interface for failed jobs. This allows you, the end user, to attempt restarting a job that failed due to a temporary issue without having to contact support..

We've released several updates to the Interest Engines interface: