Tuesday 01 September
Action Required
API Authentication Upgrade
We're upgrading the authentication used by the Convertr API as part of ongoing improvements to platform security and to support new product capabilities we'll be rolling out over the coming weeks.
API access tokens will move to a new format and will be longer than the tokens issued today. The way you request and use access tokens isn't changing — your existing client credentials and authentication flow will continue to work as they do today.
Who's affected: Systems that authenticate to Convertr's API using OAuth access tokens. Dashboard/browser users are not affected.
What to check: If your integration stores or caches Convertr access tokens, make sure the field used to store them can support at least 2,048 characters. We recommend treating access tokens as opaque values rather than relying on their format or length. If your integration doesn't store access tokens, no action is required.
Planned rollout: 1 October 2026
We'll be monitoring the rollout closely and can revert individual accounts to the previous authentication method if we identify an issue. If you'd like to test your integration ahead of the change, contact your Customer Success Manager or Convertr Support.
For full details and FAQs, see ACTION REQUIRED: API Authentication Upgrade.
Wednesday 16 September
Improvements
Lead Invalidation Summary and Leads Breakdown Widget
We have made a few improvements to the Leads Breakdown widget and Lead Invalidation Summary on the Campaign Leads page.
The Leads Breakdown widget now more accurately reflects when there are no QA-generated Caution or Invalid leads to investigate. The wording has also been updated for campaigns containing leads that have been manually invalidated or marked as stale, so the widget does not incorrectly indicate that all leads are valid. View Jobs will only be available when there are QA issues to investigate.
We’ve also added Sales Margin to the Leads Breakdown widget, making campaign margin information available alongside lead figures for users who have access to revenue details.
Learn more about Lead Invalidation Summary: here
Thursday 17 September
New Feature
Convertr Govern: Account-Level Policy Rules
Setting data rules separately for every campaign is repetitive, and it only takes one campaign configured differently to create a gap.
Account-Level Policy Rules let you set your requirements once, at the account level, and have them applied automatically — to every campaign, source, supplier, and market.
Account-Level Policy Rules helps you:
- Set a rule once instead of configuring it campaign by campaign.
- Build a policy quickly using job groups to define the rules you wish to apply to every lead.
- Catch records that don't meet your rules automatically — a named approver and a recorded reason are required before an exception is released.
- Generate on-demand proof of what happened to any record: every approval and exception, with a name and reason attached.
Your existing campaign-level rules aren't replaced, they keep working exactly as they do today, with your account rules applied on top. No new setup or contract is required; this is additional capability inside the platform you already use.
Available for Admins only.
Please note: Changing a policy applies to all leads from that point onwards; records already processed under a previous version aren't automatically re-checked.
For more information, see Convertr Govern: Account-Level Policy FAQ.
New Feature
Enterprise Login Provider Management
You can now manage which Login Providers are available for each user role within your enterprise from Enterprise > Login Providers.
This provides greater control over how users authenticate and allows different authentication requirements to be applied to different user roles. For example, Admin and Super User roles can be required to use SSO, while other roles use Password or Password + MFA.
The new configuration allows Admins to:
Enable available Login Providers by user role.
- Configure different authentication options for different roles.
- Enable more than one Login Provider for a role where required.
- Manage Password + MFA at enterprise level rather than individually for each user.
When creating or editing users, only the Login Providers enabled for their selected user role will be available.
This feature is being rolled out on request. Contact Convertr Support if you would like Enterprise Login Provider Management enabled for your enterprise.
For detailed guidance on configuring Login Providers, see Managing Login Providers within your Enterprise.
Monday 21 September
Improvement
Value Transform - Manipulations: SHA-512 encoding
We have added a new option to Value Transform - Manipulations that lets users hash values using SHA-512.