Release Notes - May 2025 Follow

Thursday 01 May

Fixes & Improvements

Fix for Campaign - Tracking > Events Publisher dropdown

We have fixed an issue where, in a Campaign under Tracking > Events, the Publisher dropdown in the Add / Edit Event modal failed to display any options, even when publishers were correctly assigned to the campaign. This prevented users from creating or editing events. The issue has now been resolved, and the dropdown correctly displays the assigned publishers as expected.

 

 

Thursday 08 May

Improvement

Improved Ease of Use for HTTP Integration Processr job

As part of improving the ease of use in Campaign configuration, we’re streamlining the HTTP integration processr job setup to reduce clutter. One such improvement involves dynamically displaying the appropriate configuration section based on the ‘Send Body’ selection. When ‘Send Body’ is set to ‘Yes’, the Body Content section is shown and the Mapping section is hidden. Conversely, if it’s set to ‘No’, the Mapping section is shown while the Body Content section is hidden.

 

 

Friday 09 May

Improvement

Universal Connector now supports ZoomInfo

We’ve added new enhancements to the Universal Connector, enabling integration with ZoomInfo for lead enrichment.

Below is a sample of how enriched data appears in the lead view — this is just an example; the integration supports the full range of ZoomInfo fields:

Example of lead data enriched with Zoominfo.png

Enriched data can be delivered to your end platform just like any other lead data.
Here is an example of how the data is delivered to Marketo:

Example of Zoominfo data in Marketo.png

For more details, please contact our support team.

 

 

Tuesday 13 May

Improvement

New Feature: Auto-Disable Inactive Users

You can now automatically disable users who haven’t logged in for a set number of days.

To enable:

  1. Go to Enterprise > Configuration > Other Configuration

  2. In System Settings, set ‘Days until user is disabled due to inactivity’ to the number of inactive days you prefer (minimum 30) or 0 to disable the feature

This example will disable users after 90 days of inactivity:

Screenshot of the Configuration to Automatically Revoke Access for Inactive Users - Feature Enabled for 90 days.png

Set to 0 to disable the feature:

Screenshot of the Configuration to Automatically Revoke Access for Inactive Users - Feature Disabled.png

Please note: This feature is disabled by default (value set to 0). Contact your admin or our support team to enable it.

 

 

Thursday 22 May

Fixes & Improvements

Fix for Batch CSV Integration job configuration

We’ve resolved an issue with the Batch CSV Integration job connection. Previously, when the connection was changed, the data fields were not automatically populated based on the selected connection. This issue has now been fixed, and the fields will update correctly to reflect the new connection details.

Simplified HTTP Integration Processr Configuration with Advanced Settings Section & Improved email Input

The HTTP Integration Processr job configuration screen has been redesigned for a cleaner and more focused user experience. Essential sections such as API, Mappings / Body Content, and Recipients are now prominently displayed, while optional settings like OAuth and Headers have been moved to a collapsible “Advanced Settings” section. This change reduces clutter and allows users to access advanced options only when needed. Additionally, the “Recipients” section has been upgraded to a new textarea input, enabling users to efficiently add multiple email addresses in bulk. Users can paste or type addresses separated by commas, spaces, quotes, semicolons, or newlines, with valid emails displayed as capsules for easy management.

Dynamic File Format-Based Configuration for Batch CSV Job

The Batch CSV job configuration screen now dynamically updates fields and options based on the selected File Format, making the setup process more intuitive and streamlined. Format-specific settings such as XLSX Password, CSV Delimiter, and Encapsulation appear only when relevant, reducing visual clutter.

Handling Non-UTF-8 Characters in Uploaded Files

We’ve released an update to improve the stability of our platform by enhancing the file import process. Previously, files containing hidden non-UTF-8 characters—such as invalid byte sequences, control characters, or special symbols—could not be processed, leading to import errors. With this release, the platform now automatically detects these non-UTF-8 characters during file upload. Users are prompted with two options:

  • Manually clean the file before proceeding
  • Authorize the system to automatically strip and convert the invalid characters during the upload process.

This enhancement reduces import-related issues and ensures a smoother, more reliable user experience.

Non-UTF 8 Characters.png

Articles in this section

See more

Related articles