Wednesday 02 April
Fixes & Improvements
Fix for Advertiser Selection in Forms (Dynamic Field Settings):
We have fixed an issue in Forms where the Advertiser selection within the Dynamic Input field’s settings under Custom Content Rules was not persisting after selection. This issue has now been resolved.
Fix for Campaign Leads Page Tooltip
We have fixed an issue on the Leads Page where tooltip information was not displayed when users quickly hovered over tooltips. This issue has now been resolved.
Fix for Leads page - Custom Table View issues
We have fixed an issue on the Leads Page related to the Custom Tables view, where search query results for field names were limited when there were numerous matches. This prevented users from finding the desired field. The issue has now been resolved, and the search query correctly returns all matching results.
Monday 07 April
New Feature
Fulfilment Risk Insights Powered by AI
We have today released, the Fulfilment Risk feature (updates hourly) to help identify publishers on a campaign level who might struggle to meet their lead goals for assigned campaigns by identifying trends and potential risks from past performance data.
This allows you to take action early, whether by offering support, adjusting expectations, or finding solutions.
Please note: Our predictions consider when the publisher signed their contract, the campaign end date, and the percentage of valid leads delivered.
Supporting Materials
Thursday 10 April
New Feature
Improved Processr Add Job Search Experience and Description Management
We’ve enhanced the Processr Add job search experience to make it more intuitive and user-friendly. The updated interface now features a sorted dropdown with clear Job descriptions, helping users better understand each job’s purpose. A new keyword-based search functionality allows for partial matches and supports custom keywords that could be configured in the Processr section in Enterprise Config (Admin access only), enabling quicker discovery of relevant jobs. We’ve streamlined description content by replacing the outdated long description field with a unified description used across dropdowns, info icons, and admin setup. Additionally, minor job name updates have been made for easier understanding.
Fixes & Improvements
Reserved names restriction in Forms
We have resolved an issue where Processr logs were not being generated for leads when reserved names were used in forms. These reserved names are now included in the restricted values list within the form validation logic. If a user attempts to use a restricted field name, an error message will be displayed, ensuring proper system functionality.
Performance improvement in Sent Batch page
Some customers experienced issues with the Sent Batch page not loading due to large data volumes, causing time-outs. This issue has now been resolved, and we have significantly improved the page’s performance to ensure faster load times.
Tuesday 15 April
Fixes
Email filter is now case-insensitive in Leads search
A bug was reported where clients were unable to filter leads by email address in both the Leads searchbar and the global Leads table filter. Upon investigation, we identified that the issue was due to casing, where email addresses with uppercase letters were not returning results, despite existing lead data. This issue has now been resolved, and email address filters will correctly return results, regardless of casing.
Thursday 17 April
Fixes
AI Fulfilment risk - Filtering not working on 'Campaign Manager' and 'Account Manager'
We have fixed an issue that prevented filtering by ‘Campaign Manager’ and ‘Account Manager’ in the Fulfilment Risk table, this now works as intended.
Thursday 24 April
Fixes & Improvements
Improved Label Readability in the Processr Job Interface
We’ve enhanced the readability of labels in the Key section across the Processr Job interface. Labels using camelCase (e.g., apiUrl) are now displayed in a clear, space-separated format with appropriate capitalization and standard abbreviation handling (e.g., API URL). Similarly, labels using snake_case (e.g., send_as_json) are now shown in a user-friendly format such as Send As JSON. These improvements ensure consistent formatting across all relevant UI sections. The changes are purely visual and do not affect the underlying key values or functionality.