Monday 02 July
New & Improved
Campaign Templates
We are excited to introduce our new feature, Campaign Templates, which allows the creation of a master campaign to be used as a template. Admins can easily toggle a switch to designate a campaign as a template, while non-admins will have the ability to view which campaigns are set as templates. This work is part of a wider theme to make campaign creation quicker and easier.
Defining master campaigns as templates is a foundational piece of work, upon which we will build additional functionality to help with:
-
Compliance, by
- Locking Jobs to prevent improper removal
-
Reduction in errors, by
- Locking Jobs to prevent accidental editing
- Identifying Jobs to be checked
-
Ease of use, by
- Adding guidance notes in-platform
- Turning on a new 'easy mode' by default
-
Auto-creating campaigns (e.g. from Salesforce)
- By triggering the creation of a campaign based on a template
Whilst this release simply enables you to specify which campaigns are templates, it will be followed up with the ability to add guidance notes. Subsequently we'll add the ability to lock and check jobs.
Note: If you've personalized the Dashboard view with 'Custom Table Views', you'll need to manually add the 'Type' column from the Table Columns dropdown. Alternatively, you can use the Reset button to revert the Dashboard view to its default settings, which will automatically include the new 'Type' column.
Read more about how to use this feature here.
Wednesday 03 July
New & Improved
User Permissions: Configuration for Form Management
We are excited to introduce a new sub-section called ‘Features’ in the Users section, for the following user roles: Super Users, Agency Users and Report Users. This section will hold feature toggles that will provide you with more granular control over user access to the platform functionality and data.
Today, we have introduced in this section, a feature toggle called ‘Form Management’ specifically for Super Users and Agency Users to help manage forms within the platform. With the checkbox ‘Form Management’ checked, users will be able to:
- Add Forms: Create new forms as per your requirements.
- Save as New: Duplicate existing forms, modify them and save them as new forms.
- Edit Forms: Update and make changes to existing forms.
- Delete Forms: Remove forms that are no longer needed.
- Archive Forms: Archive forms to retain them for future reference without keeping them active.
- Activate Forms: Reactivate archived forms or enable newly created forms for active use.
We have also moved the existing checkbox: ‘Enable Access to Business Insights’ to the Features sub-section and will now be displayed only for Agency Users and Report Users.
More feature toggles related to Deletion Management, User Management and Access to Processr tab will be made available in upcoming releases.
Read more in our guide on how to use this feature here.
Monday 08 July
New & Improved
User Permissions: Configuration for Delete Actions
Today, we have introduced below the Features sub-section, a feature toggle called ‘Allow Deletion’ specifically for Super Users and Agency Users, to manage their ability to perform delete actions on the platform.
With the ‘Allow Deletion’ checkbox checked, users will be able to:
- Delete Leads
- Delete Campaigns
- Delete Advertisers
- Delete Publishers
More feature toggles related to User Management and Access to Processr tab will be made available in upcoming releases.
Read more in our guide on how to use this feature here.
Tuesday 09 July
Fixes
New Processr - Inconsistency in Saving Blank Values
We have resolved an issue in the new Processr job that prevented blank values from being saved.
New Processr - Incorrect JSON Serialization for Empty Children Arrays
We have resolved an issue where, if a user deletes all child elements from a repetitive children type but the parent node remains, the platform would include an empty 'children' array in the JSON object. This behavior interfered with lead processing, which expects the 'children' key to be omitted when it is empty.
New Processr - "Field is required" Error on editing HTTP Jobs
We have resolved an issue in the new Processr job where users encountered a "Field is required" validation error when attempting to edit HTTP jobs, despite the fields already being populated.
New Processr: Batch CSV Import Settings Issue
We have fixed an issue in the new Processr that caused email fields to be omitted when importing a job using "Import from Settings".
WYSIWYG Editor Issue
We have fixed an issue with the WYSIWYG editor where the cursor would reset to the beginning when attempting to make an edit.
Wednesday 10 July
New & Improved
User Permissions: Configuration for User Management
We have now introduced below the Features sub-section, a feature toggle called ‘User Management’ specifically for Super Users and Agency Users, to control their ability to manage other users below them in hierarchy.
With the ‘User Management’ checkbox checked,
- Super users will be able to: Add, Edit and Delete all other users below them in the hierarchy. This includes: Agency, Advertiser, Advertiser Report User, Report User, Call Centre Operative and Publisher users.
- Agency users will be able to: Add, Edit and Delete Publisher users.
With this update, you can now revoke these permissions if you wish by unchecking the box.
Additional feature toggle related to Processr tab will be made available in upcoming releases.
Read more in our guide on how to use this feature here.
Thursday 11 July
New & Improved
Publisher Notifications: Ability for Publishers to see only campaigns that have unread updates
We have added a toggle to the list of campaigns in the Publisher portal to only show campaigns that have unread updates from Campaign Managers. This helps Publishers better understand which of their campaigns need their attention.
This feature will be specifically useful for publishers with a lot of active campaigns.
Read more about how to use this feature here.
Fixes
Pause Campaign not notifying publishers
Some of our customers have flagged that their publishers are not being notified when they pause a campaign. We have fixed this.
Monday 15 July
New & Improved
New Processr: Navigation focus for Validation error
We have improvised the navigation focus when users encounter a validation error. Now, upon clicking Save for a Processr job, if there is a validation error for a field, the navigation will automatically focus on the first validation error, if any, providing a better user experience.
User Permissions: Access to Processr
We have introduced in the Features sub-section, the final feature toggle related to User Permissions- ‘Access to Processr’, specifically for Super Users and Agency Users, to control their ability to access the Processr tab within campaigns.
With the ‘Access to Processr’ checkbox checked, Super users and Agency users will be able to access the Processr tab to add, edit and delete processr jobs.
Read more in our guide on how to use this feature here.
Fixes
WYSIWYG bold, italic and underline styles overriding each other
We have fixed an issue with the WYSIWYG editor where the Bold, Italic, and Underline styles were overriding each other.
Thursday 18 July
New & Improved
Campaign Templates - Internal Campaign Information
We are excited to introduce our new feature, Internal campaign information built on top of Campaign Templates, which allows users to add guidance notes.
Using Internal Campaign Information, admins with Admin and Super User access can provide guidance notes for users. To add, edit, or remove these notes, the campaign must be of the Template type.
Read more about how to use this feature here.
Fixes
New Processr: Eightbar validation is preventing config
We have resolved an issue with the validation of the Eightbar (formerly Neo) Integration that was preventing the addition of alphanumeric characters to 'Campaign_id' and 'Publisher_id'. Additionally, we have changed 'Questionnum3_oopostal' and 'Zipcode_verification' from mandatory to optional fields.
New Processr - HTTP Jobs to have number/string combination for keys
We have resolved an issue in the new Processr of HTTP integration where HTTP jobs were not loading correctly when the configuration contained a combination of numbers and strings for keys.
New Processr - Eloqua token button resets to "Get Token" state despite existing token
We have fixed an issue in the new Processr where, for Eloqua jobs, the Get Eloqua Token button was not showing as Refresh Eloqua Token despite having the Eloqua token stored in the job.
Monday 22 July
Fixes
New Processr: Batch Email Errors
We have resolved an issue concerning Batch Integration, where error emails were erroneously sent when integrations had mappings without a selected form field. Moving forward, errors will not be triggered if a mapping does not have a corresponding form field.
To confirm this did not prevent the batch integration from being sent.
Email Example:
Campaign Lead Batch failure: Campaign Processor Job ID 123456 failed. Error: One of included fields is not of a valid type. Expected "string", got "NULL".
Config Example Below:
Feature Sunsetting
Dun and Bradstreet
We have now sunsetted our Dun and Bradstreet solution and as a result, we have now removed the Form type ‘International Company Address Lookup’ and the enrichment job ‘Search International Company Information’. For any customers using these services, there will be no impact on your forms or campaign setup.
Wednesday 24 July
New & Improved
Skipping sharing of the change in Processr Job(s) with Publishers
We have added the Don't Share button to the Review and Share panel to skip sharing the change in Processr Job(s) with Publishers. We recommend using this button when you need to keep the change internal, and there is no action required from Publishers with the change.
Read more about how to use this feature here.
Lead API changes
We have added Marketo Id to the leads endpoint. The Marketo Id, which we store for the Marketo and Marketo programs integrations will now be available in the leadData property.
Fixes
New Processr: Duplication of Processr Jobs when moved to a Job Group
We have resolved an issue where adding a processor job to job groups resulted in the processor job being duplicated upon creation in the new Processor.
New Processr: Salesforce integration prompting validation for Security ID and not allowing blank field mapping
We have resolved an issue where users were prompted with a validation message to add a valid URL for the security ID field in the Salesforce integration. This occurred because configurations from the old processor were in a different order when migrated to the new configuration. Additionally, we have changed the behaviour to allow users to save configurations without each value having a mapped field.
New Processr: HTTP Integration - Empty header prompting validation
We have resolved an issue where users were prompted by a validation message to add a header for HTTP integration. This occurred when configurations from the old processor, which had an empty Header, were migrated to the new configuration.
Monday 29 July
Fixes
Super Users - Contact Status Column Not Visible
We have resolved an issue that prevented super users from adding the column 'Contact Status' in the leads table for campaigns with call centre services enabled.