By Adam Carter - June 21, 2021
When Convertr began, one of our core goals was to improve data processes and transparency between brands, agencies, and lead providers. To aid this, the Convertr platform has long included a legacy Enterprise-to-Enterprise connection to sync leads between two platforms. Our latest release expands our platform connections to now include:
For those of you familiar with the old E2E integration, the same functionality is still available under the Convertr Connect integration.
When set up, this integration allows data providers to automatically deliver leads from their platform into their customer’s platform campaign. It also provides real-time feedback on the customer lead status to keep both parties aligned on lead acceptance and rejections.
Learn how to configure the Convertr Connect Integration in the help center.
To simplify the integration process, users will now see a new ‘Place Sync Tags’ button. This update simplifies setup and provides visual confirmation the tags are placed and synced.
|
|
We will soon be releasing two new processr jobs to help sync campaign rules between platforms.
In essence, these two new processr jobs allow the data provider to query certain campaign rules on a customer platform and process leads against the most current requirements. Without these new jobs, the data provider would need to manually review all campaign rules to check for changes.
Below is a visual representation of the data flow:
Receiving Platform:
(Generally a brand or agency customer receiving leads)
The campaign manager would set up their campaign rules by configuring simple conditional validation and validation list processr jobs as normal.
Sending Platform:
(Generally a publisher or data provider delivering leads)
The user would select from a list of Convertr Connect job configurations that have been set by the Receiving Platform. Once set, these jobs would automatically update to match the rules set in the Receiving platform.
If leads fail the campaign rules, this information will be shown in the current QA Flags section.
| Examples of a lead rejection because it does not match a required value on the receiving platform. | |
|---|---|
| Error Message – Convertr Connect Simple Conditional Validation Job | Error Message – Convertr Connect Validation List Job |
|
|
| Examples of a lead rejection because a job has been deleted from the receiving platform. | |
|---|---|
| Error Message – Convertr Connect Simple Conditional Validation Job | Error Message – Convertr Connect Validation List Job |
|
|
Learn how to configure the Convertr Connect Simple Conditional Validation and Validation List jobs in the help center.
Want to learn more about how Convertr can simplify campaign management, automate data processes and improve alignment, request a demo today.
Campaign Templates and Guidance Notes
Genuine templates help ensure campaigns are built correctly When users create a new campaign by simply copying from another, they have free reign to make as many changes as they want. It is common to have compiled detailed instruction manuals to tel
Super Users and Configurable Permissions
Precisely control user actions and access to data We know that if you're responsible for the data in your system, users being able to access configurations that they shouldn't touch or having the ability to delete data they shouldn't, can keep you a
Publisher Notifications of Campaign Changes
Continue to receive valid leads as you update your campaign requirements after your campaign has started We know that up to 80% of campaigns have their requirements updated at least once after the campaign starts. This can cause all sorts of probl
Book a demo with one of our experts to review your current demand generation process, define your objectives and answer any questions.
London: +44 (0)203 617 7659
Denver: +1 (720) 699 7880