Fitting the stack you already run
Composable data infrastructure
The LeadScale Engine™ sits between the sources supplying lead and contact data and the systems that use it, taking on the agreed processing and delivery.
The LeadScale Engine receives records through its API, file routes or configured integrations and processes them against programme rules. It delivers through a standard integration, the receiving system's API or files. The Engine sits between capture and destination systems, while your CRM and marketing tools retain their existing roles.
Place the processing between your systems
Start with the systems you run, where the data originates and where it needs to arrive. LeadScale's technical team works through those connections with you. The Engine configuration section of technical data services explains that setup work.
- Map the hand-offs. Identify the sources, receiving systems and points where records need processing before they move on.
- Place the Engine. Agree which checks and processing it will perform between capture and delivery, and which jobs remain in the surrounding systems.
- Connect each direction. Systems can submit to the Engine's API or use a configured integration. Files can arrive by transfer or manual upload. Delivery uses a standard integration, the receiving system's API or files.
- Run the agreed flow. Incoming records pass through the configured processing and are delivered to one destination or several. Processed records can also be downloaded.
Input and output are separate connection decisions. Posting records to the Engine's API describes an incoming route. Delivery through a destination platform's API describes an outgoing route into that platform.
Routes into and out of the Engine
API submission.
Your system can submit records to the Engine's API for processing through the agreed flow.
File routes.
Transfer or upload files into the Engine; receive processed files through a file-transfer location or download them.
Named integrations.
Salesforce, HubSpot and Marketo have individual integration pages explaining their supported connections.
Delivery through a destination API.
The Engine can call the receiving system's API. Work beyond standard routes is scoped separately as custom work.
The Salesforce integration page, HubSpot integration page and Marketo integration page explain what each connection covers. The integrations catalogue brings the wider set of routes together.
On one enterprise programme, the client's marketing automation platform changed while suppliers continued submitting data as before. LeadScale switched delivery to the new platform and added a return connection for suppression and reporting. That was a configured change on a particular programme, rather than a promise that any destination can be exchanged without work.
Adding checks to an existing form
Everest used Engine code on its enquiry form to check phone numbers as visitors entered them. The code was designed to be lightweight. The Everest case study explains what the checks did and how the form was used by visitors.
What stays in your other tools
The Engine handles the agreed record processing and hand-offs. Campaign calendars, analytics, visualisation and attribution modelling remain in the tools you use for those jobs.
A system outside the named integrations needs its connection assessed individually. Some use standard API or file routes; where additional development is needed, that work is scoped as custom from the start.
Questions from technical teams
Can the Engine work with the systems we already run?
The Engine delivers records into a client's existing CRM and marketing platforms. The connection depends on how the destination accepts data, using an integration, its API or a file route. The systems involved are assessed during setup.
Can our engineers submit records directly?
Yes. Your systems can submit records to the Engine's API. LeadScale's technical team works on setting up the connection. Outgoing delivery is a separate route through the receiving system's API, an integration or files.
Can we use the Engine without LeadScale Services?
Yes. The Engine can be bought without LeadScale Services, and clients do so. Discuss the connection and configuration work you need when scoping that engagement.
What if our destination is not on the named list?
The named list is not the only way to deliver records. The destination's API or a file route may provide the connection. The particular route needs to be confirmed; any work beyond standard routes is scoped as custom work.
Where should the Engine fit?
Bring the systems you run and the hand-offs between them that give you trouble.