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.

We've released an update regarding consent for the Lytics Google Customer Match Export, Google DV360 Audience Export, and Amazon DSP: Sync Cookies/Email Export. Here is an overview of what has changed and where improvements have been made.

The new Interest Engines tab within the Content section of the left-hand navigation menu surfaces different configurations for content taxonomies and their related Affinities. This concept is called Interest Engines, which is also the tab's name in the navigation.

When you create or edit Mappings the Stream field will show a dropdown of all the streams coming into your account and the list will narrow as you begin to type the stream name.

In addition to being able to discard unpublished Schema changes, the UI now supports the ability to revert the schema back to a previous version. Learn more in the Schema Versions documentation.

When creating new or editing existing fields you know have the option to identify what fields in your schema are to be considered personally identifiable information.

Previously when configuring jobs for importing or exporting CSV or JSON files or for setting up Lytics platform alerts the provider you would select was Custom Integration. The provider is now Lytics File Service for importing CSV or JSON files or Lytics Monitoring for setting up Lytics platform alerts.

We've introduced a feature to help you categorize fields and improve tracking against the C360 Readiness Index. When creating or editing a field, you can manually assign one of seven categories through the API or Field Wizard. These category tags are visible in the profile view and will play a crucial role in our future enhancements for better Readiness Index visibility within the Lytics UI.