Tuesday 02 June

Fixes

Resolved Lead Processing Issues for Pending Batch and Publisher Over-Delivery Workflows

We have released a fix addressing scenarios where leads could become stuck in ON_HOLD_PENDING_BATCH or ON HOLD - Publisher Over Delivery statuses. The update ensures that lead statuses, pending batch counts, billing flags, and campaign overview metrics are correctly recalculated when Batch CSV jobs are deleted, disabled, or modified during processing. Leads now transition appropriately to COMPLETE once processing requirements are met, while pending batch queues are automatically updated to reflect active jobs only. The fix also improves handling of publisher over-delivery scenarios by correctly re-evaluating held leads when publisher allocations are increased and contracts are signed. Additionally, campaign reporting widgets now accurately reflect billable, delivered, and fulfilled lead counts across both standalone and combined batch-processing workflows.

Thursday 11 June

Improvements

AI Assistant Enhancement: Full Processr Job Creation Support

The AI Assistant now supports the creation of all Processr job types, enabling users to configure QA, Enrichment, and Integration jobs through a guided conversational experience. This release expands support to include Convertr Connect (V1 & V2), Soft Validation Check, Convertr Connect Simple Conditional Validation, and Convertr Connect Validation List Check jobs. Users can now create any supported Processr job type more efficiently, reducing manual setup effort and simplifying onboarding for complex configurations. The enhancement improves consistency, accuracy, and speed when configuring jobs across the platform. This milestone represents a significant step toward making Processr job creation more accessible and streamlined for users.

Thursday 18 June

New Feature

Campaign Requirements Summary

Convertr Intelligence now generates a plain-English summary of your campaign configuration! 

The Campaign Requirements Summary analyses your QA jobs, validation rules, value transforms, form setup and suppression logic, then presents a structured overview of required lead attributes, field-level validation requirements and derived field behaviour without the need to manually review individual configuration screens.

The summary includes configuration risk alerts, colour-coded to highlight critical issues likely to cause lead rejection and warnings flagging potential inconsistencies worth reviewing before launch. Users can refresh the summary at any time to reflect the latest saved configuration and copy the full output to share campaign requirements directly with suppliers and operational teams.

This feature reduces the time and effort required to understand, validate and communicate campaign setup. Teams can onboard campaigns faster, identify configuration issues earlier and deliver clearer requirements to partners. Campaign Summaries is currently available in Beta.
Read more: For full setup instructions and guidance on using the Campaign Requirements Summary, visit the Campaign Requirements Summary Help Guide.

Thursday 25 June

Fix:

Web-hook Appended Lead Data Now Available for Reporting

We have fixed an issue where lead data appended via web-hooks was not available for reporting.

With this update, any new lead data received through web-hooks will now be available in both Report Builder and Lead Export, allowing it to be included in reports and exports as expected.

The below screenshots show lead data appended via the web-hook being available in the 'lead view' and the 'lead export' sections.

Note: This update applies to new web-hook data going forward. A separate update to make previously appended web-hook data reportable is already planned and will be available shortly.