Monday 02 September

New & Improved

Campaign Lead Export: Allow Agency users to see all jobs in the flag filter dropdown

We have made an improvement to lead export at campaign level for Agency users. These users can now use the Flag Filter dropdown to filter on all applicable QA, Enrichment and Misc jobs configured on the campaign. Previously the dropdown only showed jobs that had failed at least once.

Fixes

Revenue Remaining column not reflecting the correct value in the dashboard

We have resolved an issue that caused the 'Revenue Remaining' column on the dashboard to display incorrect values for the campaign. The column now correctly reflects the 'Revenue Remaining' value generated by the campaign report builder.

Before	After

Tuesday 03 September

Fixes

New Processr: Placeholder text for Import from Settings dialog inputs

In the New Processr jobs for "Import from Settings," we have added placeholder text to provide better guidance to users when selecting campaigns and jobs.

New Processr: Removed up-down arrow key for integer field values

In the New Processr jobs, the up and down arrow keys were displayed in numeric input fields, which is a default behavior of HTML 5. This caused confusion among users, who mistakenly interpreted the arrow keys as controls for moving the position of fields. We have now resolved this issue by removing the default HTML 5 up and down arrow keys.

New Processr: Fix for Import from Settings Search

In the New Processr's "Import from Settings" section, the search was previously limited to the first 10 values, which sometimes prevented finding the correct results. This issue has now been fixed.

Wednesday 04 September

Fixes

Deleted Integrations Were Running for Pending Batches

Previously, when integration was removed while there was an active pending batch, we were still trying to run the integration for this batch. We have fixed it and won't run deleted integrations for pending batches anymore.

Friday 06 September

Fixes

Leads Tagged as On Hold Campaign Using Scheduled Delivery

We resolved an issue affecting campaigns using Scheduled Delivery, where leads incorrectly displayed an “On Hold - Pending Batch” status after Scheduled delivery was disabled and leads were reprocessed and integrated via Batch CSV.

The fix ensures that lead statuses now accurately reflect their correct state after the leads have been sent through Batch CSV.

Monday 09 September

New & Improved

User Permissions: Masked agency users to access lead reports

We have implemented an enhancement for masked agency users, granting them access to Leads Reports within the Report Builder. This update allows masked agency users to create, generate, and manage Leads Reports with all personally identifiable information (PII) securely masked.

They will be able to report exclusively on non-PII data and values that have been whitelisted at the agency level. This will have to be configured by Admin users 

Improved performance of duplication jobs

To improve query performance and optimise database usage, we have updated three duplication jobs to utilise the new 'shortValue' column where appropriate. This change specifically affects the following jobs:

• job.duplicate_email
• job.duplicate_publisher_email
• job.duplicate_field

Fixes

Revenue column on dashboard causing errors

We have now released a fix for an issue that caused errors when the custom column ‘Revenue’ is added to the dashboard.

Tuesday 10 September

New & Improved

New Processr - Re-ordering list and sub-list

We are introducing a new feature in the New Processr jobs that enables users to reorder list items along with their sub-lists. This new functionality allows users to easily reposition list fields for better organisation and flexibility.

Lock Jobs on Campaign Templates

Lock jobs builds on the campaign templates and allow Admin & Super users to lock jobs within templates, preventing non-Admins from editing or removing them in campaigns created from these templates.

Read more about the Lock Jobs feature here.

Fixes

New Processr - Reordering Mapping Fields Causes Values to Become Empty

We have resolved an issue in the new Processr jobs where, in the configuration, adding a new key-value field and moving it using the Up/Down positioning buttons without entering values would cause previously entered values to be cleared. This issue has now been fixed.