Marketo
Marketo is one of the destinations the LeadScale Engine™ delivers into most often.
The LeadScale Engine delivers records into Marketo through a standard integration configured by LeadScale's technical team. Records go through the checks agreed for the programme before delivery. On one enterprise programme, LeadScale also established a return connection from Marketo so existing-customer data could support suppression and reporting.
When the destination changes
When one enterprise client moved its marketing automation to Marketo, its suppliers were already submitting records to the Engine. LeadScale switched the destination connection to Marketo, so those suppliers could continue submitting records without changing their setup.
LeadScale also established a return connection from Marketo for existing-customer suppression and reporting. Delivery brought new records into Marketo; the return route made customer data held there available to the Engine, so incoming responses could be screened against it.
The technical data services page's section on using existing data explains how client data can be brought into the Engine's processing.
What reaches Marketo
Records go through the programme's checks and rules for duplicates and repeat responses before delivery. For records created through a LeadScale programme, source, timestamp, lineage and consent audit information travel with them. Marketo can be one of several systems receiving the record.
The lead validation page explains the checks available and how their order is configured.
Getting it running
You specify where the records need to arrive. You and LeadScale agree the checks, their order and how to handle records that fail before processing starts. LeadScale's technical team configures delivery into Marketo.
Where the programme needs existing-customer data for suppression, LeadScale's technical team also configures an agreed return connection from Marketo into the Engine.