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:

A bug that caused some Source and Destination configurations to experience infinite loading when attempting to retrieve a list of available fields from the schema has been addressed. This issue was initially identified in the Pinterest CAPI integration.

Previously in the app, certain functionalities were completely hidden or depended on the API to provide error messages when actions like Audience creation were not permitted. Now, the UI has been updated to clearly indicate when users lack the necessary access rights before they attempt to make requests related to Audiences, Sources, Destinations, Fields, Mappings, etc.

When a user is removed from a Lytics account, it's typical for the tasks or audiences they created to remain active. Previously, this situation led to errors across the interface, particularly when reviewing a Source or Destination in Conductor. A warning would appear with minimal details following the user's removal. This behavior has now been amended, and the interface will display "Removed User" in the "created by" field to clarify the status.