What LeadScale connects to
Salesforce, HubSpot and Marketo are named integrations with the LeadScale Engine™, and other systems connect by file, upload or API.
Records coming in
Webinar and event platforms
An attendee list arrives as a batch file after the event; a registration can be posted to the API as it is made.
Ecommerce and payment systems
The Engine processes customer records as well as leads, so records from an ecommerce or payment system arrive by file or API.
Records from your CRM
Your CRM can push records to the Engine by file or configured integration.
Media and lead generation sources
Records bought through media arrive as a file or API submission, and the programme's checks run before anything is delivered.
Posting records to the API
Any system that can make a web request can post records to the Engine, including a custom-coded form on your website.
Records going out
CRM and marketing automation
- Salesforce. Named native integration.
- HubSpot. Named native integration.
- Marketo. Named native integration.
- Eloqua. Standard delivery destination.
- Pardot. Standard delivery destination.
Ad platforms and audiences
Checked leads and target accounts sync into LinkedIn matched audiences and display audiences, usually within 48 hours. Where you share conversion data, a conversion recorded after delivery can also be reported back to the platform the click came from.
Email platforms and diallers
An email platform or a dialler is as much a destination as a CRM, and one record can go to several systems in one run.
Spreadsheets and workspace tools
Output can leave as a download or an automated export to a named person; chat and workspace tools connect through the API or webhooks.
Files and cloud storage
Any storage account reachable over FTP, or written to through the API, can be used at either end.
Taking records out through the API
Records go out over the same REST interface that brings them in, with webhooks alongside.
Not on the list?
A system without a named integration connects by one of three routes: a file transfer, left in an FTP location or written out to one; the upload interface, for a file by hand and a download of finished records; or the Engine's REST API and webhooks. Who builds the connection is covered under technical data services.
Name the system and what you want to move in or out of it.
We will tell you which route it takes.