Convertr RoadmapClick the tabs below to see what we're working on now and next. Full release notes can be found by clicking the link in the top-left corner of the page.
Considering
Discovery
Next
In Progress
Done
Connectivity and Integrations
Create and Update Campaigns from Salesforce
The ability to automatically create a campaign in Convertr from your Salesforce data (and subsequently update that campaign when your Salesforce configuration changes).
We anticipate the first version of this will use a trigger in Salesforce to create a campaign in Convertr cloned from a Convertr campaign template (which will be updated with values from Salesforce).
Lead Validation and Enrichment
Integrations into your own enrichment provider(s) of choice - note that this requires you to have your own subscription.
Connect to your preferred provider to validate, complete and append enrichment data.
If you want to do this today (whilst we build a dedicated integration to your provider of choice), try using our Universal Connector.
More Fields Available via the API
We frequently receive requests for more fields to be made available via the API (for the purpose of automating data transfer).
As things stand, continuing to add more and more fields could eventually start to negatively impact performance. So, the goal of this work is to make available the fields you want whilst maintaining optimal performance.
Efficient Campaign Creation and Management
Data Field Consistency (Form Fields)
The goal of this work is to help you reuse the same data fields going forwards so that the same data isn’t stored in multiple different fields e.g. jobTitle and job_title. This is important for reliable reporting and avoids the need to query multiple fields and spend time consolidating the data.
There are many places where data fields can be created. The most used method with the highest cause of duplications is Form fields. Therefore this is where we’ve started and the first feature will be the introduction of an auto-complete prompt. These suggestions don’t force an existing field to be used, but do will help users reuse existing fields instead of creating new variations by highlighting the existence of a field or showing which is most commonly used if there are many.
Read more in the 'how to' guide (but please note this feature isn't currently live).
In-Platform Communications
The ability to add notes and chat with colleagues at an entity level (e.g. campaigns). This means that you can make notes and have conversations about specific items. These will then be preserved for easy actioning and review.
We also plan to add the ability to communicate with Publishers regarding campaign change notifications.
Campaign Setup Troubleshooting
Tools to help you test and check your campaign setup ahead of go-live to ensure the configuration has the intended outcome
Streamlining Work with Partners
Partner Visibility of Lead Invalidation Reasons
By making the full lead invalidation reasons readily available to your lead supplier, it has the dual benefits of:
Helping them quickly supply an updated/compliant or replacement lead
Reducing the need for time-consuming communications to discuss causes of invalidation
User Management and Compliance
New Dedicated API Permissions
This new dedicated API permission provides the same API access as Admins but with no access to log into the platform (to help with user management and compliance).
It will work as follows:
Same API access as Admins
Access to all data (no data masking)
Unable to login to the platform
Does not have to deal the with platform password settings
Powered by airfocus
Data Field Consistency (Form Fields)
Data Field Consistency (Form Fields)

The goal of this work is to help you reuse the same data fields going forwards so that the same data isn’t stored in multiple different fields e.g. jobTitle and job_title. This is important for reliable reporting and avoids the need to query multiple fields and spend time consolidating the data.

There are many places where data fields can be created. The most used method with the highest cause of duplications is Form fields. Therefore this is where we’ve started and the first feature will be the introduction of an auto-complete prompt. These suggestions don’t force an existing field to be used, but do will help users reuse existing fields instead of creating new variations by highlighting the existence of a field or showing which is most commonly used if there are many.

Read more in the 'how to' guide (but please note this feature isn't currently live).