Technical data services

Before adding the Engine to your systems, you need to know what the change will involve for the people who work with them. Where will records come from? What needs to happen before your team receives them? Which parts will LeadScale handle, and which will need work on your side?

LeadScale’s technical team works through those questions with you during onboarding. The starting point is your current workflow: the sources feeding it, the systems receiving data and the work you need the Engine to do between them.

A working connection establishes a route for the data. The setup also needs to specify what happens to each record before the receiving team gets it.

LeadScale’s technical team translates your requirements into checks, filters and processing conditions. Some programmes also need enrichment to add missing information after the checks have run. The combination is agreed before processing begins.

The Engine configuration page describes how those requirements become rules. For what can be added to a record, see the data enrichment page.

A CRM can be a source for a programme as well as the place new records arrive.

If an acquisition programme needs to exclude existing customers, the customer data in your CRM has to be available for suppression. Delivering new records into that CRM would only address one part of the requirement.

LeadScale’s technical team can set up retrieval from client systems so that information can be used in the Engine’s processing. Existing-customer data can then be used to screen new responses before delivery. The deduplication and suppression page explains how that data is prepared and used alongside rules for repeat responses.

Most programmes need records delivered into one destination. Some need more than one system involved, with a record’s next step depending on what comes back from an earlier one.

LeadScale designs those flows around the programme. The Engine can deliver to several destinations and support a sequence between systems where it is needed. The work is to establish which system needs the record, what happens there and what should follow.

If a lead becomes an opportunity or a sale in your CRM, that result needs a route back before it can inform subsequent activity. The technical setup can connect those later outcomes to the programme that supplied the record.

The client and LeadScale agree what the programme is trying to optimise for. Where you share outcome data, the Engine and connected systems can be configured around those outcomes.

On programmes set up for it, agreed outcomes can return through connected systems. Which outcomes return depends on the programme and the systems involved.

For the questions those results can help investigate, see the data quality and conversion analysis page. It distinguishes what capture and processing show from what needs information about later outcomes.

Data can enter the Engine by file transfer or upload, through an API, or through a configured integration. Those routes are also available for delivery into one or more destination systems.

Marketo, Eloqua, HubSpot and Pardot are among the most common marketing automation integrations. They use standard connections, so the platform receives Engine records through the same route it uses for records from your other sources.

This helps establish the scope of the work. A standard connection can be used where it fits; where it does not, custom work is possible and is scoped separately. The integrations catalogue gives your team the documented connection options to discuss with us.