Monday 2 December

New and Improved

Reporting : 'OriginalStatus' to store original status of lead

We have updated the way lead status is reported via Lead Export and Report Builder.

A new field, 'QA Result’, will now display the current status of the lead in both Lead Reports and Lead Exports.

Additionally the field 'Original Status’ will reflect the initial/original status of the lead, regardless of reprocessing, for new leads. For existing leads, the field will continue to display the current status of the lead.
To summarise,

• For new leads: 'Original status' will report on the initial/original lead status irrespective of reprocessing and 'QA Result' will report on the current status of the lead
• For existing leads: Both 'Original Status' and 'QA Result' will report on the current status of the lead

Example: The below image shows a report generated for existing and new (highlighted) leads. For existing leads, the columns 'originalStatus' and 'QA Result' both show the current status of the leads after reprocessing.

For new leads, the column 'originalStatus' retains the initial status of the leads prior to them being reprocessed and 'QA Result' shows the current status after reprocessing.

 

---

 

Tuesday 3 December

Fixes & Improvements

Conditional Validation job usability

We’ve enhanced the Conditional Validation Processor job by removing default key numbering. This change reduces confusion for new users and simplifies the validation process for better usability.

The below image shows the Fieldvalues with the key numbering:

Before	After - We have now removed the key numbering as shown below:

Read more about the Conditional Validation job here.

Batch CSV client email validation

We have fixed an issue with email validation in the Batch CSV Processor job, which previously restricted certain valid email formats. The validation process now supports a broader range of email formats, ensuring accurate processing and improved functionality.

Removed email numbering keys from HTTP Integration job

We have updated the HTTP Integration Processor job by removing email numbering in the Recipients section, simplifying the interface, and improving user experience.

Removed unused feature from HTTP Integration job

We have updated the HTTP Integration Processor job by removing the ‘verify_ssl_peer’ and ‘verify_ssl_host’ fields from the API configuration. These fields were obsolete and no longer used, ensuring a cleaner and more streamlined configuration process.

Fixed broken redirect URL during login

We have resolved the issue with the broken redirect login URL, ensuring a seamless and reliable user authentication experience. Users can now be redirected to the correct login page without interruptions.

 

---

 

Wednesday 4 December

Fixes & Improvements

Permissions: Contact Status Column Not Visible to Super Users

We’ve resolved an issue that previously prevented Super Users from adding the Contact Status column to the leads table for campaigns with the Call Centre Services feature enabled. With this fix, super users can now add the Contact Status column using custom columns when the Call Centre Services feature is active on a campaign.

Add details of lead data edits to System > Audit

We’ve improved the logging in the System > Audit table. Previously, changes made through the lead profile did not display the lead ID or update details in the System Audit table. Now, the System Audit table will clearly show both the lead ID and the details of any updates.

Before

After

Logic change to consider Processr Status for calculating 'Publisher over-delivery' count

We’ve resolved an issue where campaign reports displayed incorrect lead counts in the publisherOverdelivery column. We had a situation where regardless of the Hold Publisher Over Delivery feature being enabled, if the lead was over the publisher cap this was being accredited to the publisher over delivery number. This has been corrected to accurately reflect the number of leads with the On Hold - Publisher Over Delivery status in older campaigns.

Campaign suppression Lists Import Option Removed

We are simplifying how suppression lists work in campaigns. The option to add new suppression lists to campaigns will no longer be available.

What is Changing:
You will not be able to add new suppression lists to campaigns.

What Stays the Same:
Any suppression lists already configured in your campaigns will continue to work as usual.

What to Use Instead:
Going forward, we recommend using Validation Lists at the Advertiser level or System level as alternative suppression/acceptance lists.

Report Builder > Publisher Band Information available in Lead Reports

We’ve added Band ID and Band Name fields to the Report Builder > Lead Type. Admins, Super, Agency  (masked and unmasked) and Report users can now include these fields in lead reports. This update also allows grouping by Band ID and Band Name for more flexible reporting.

Fields

Grouping

The Revenue column on the dashboard shows the same value as Revenue Remaining

We’ve resolved an issue where the custom columns Revenue and Revenue Remaining displayed identical values on the dashboard. These columns will now correctly show the revenue generated and remaining revenue for the campaign, aligning with the data in campaign reports.

 

---

 

Friday 13 December

Fixes & Improvements