Sharing your data on your terms
Specify what a partner needs to see or receive, then build the exchange around that requirement. LeadScale's Engine can count, check and deliver lead or contact records, with processing and delivery traced through an audit trail.
LeadScale can count eligible lead or contact records against a specification, apply agreed processing and deliver through a configured route. Define the recipient, required information and intended use before arranging the exchange. Processing and delivery have an audit trail; hosting and direct-access requirements need to be scoped for the arrangement.
Decide what the partner needs at each stage
A prospective customer may first ask whether enough records fit a programme. Once the requirement is agreed, it may need selected records in its receiving system. Treat the feasibility question and the delivery requirement as defined stages of the exchange.
- Specify the output. Establish whether the partner needs a count, selected records or direct access to an environment. Identify the fields and selection criteria.
- Agree processing. Define the contact checks, duplicate rules and any enrichment required, including handling of failed results.
- Assess the route. Record delivery can use a configured integration, the receiving system's API or files. Hosting and access requirements need their own technical scope.
- Trace the hand-over. Processing and delivery have an audit trail. Where records are supplied against an order, delivery is reconciled against it.
Make the exchange specific enough to assess
Put five things into the discussion: the recipient, the output it needs, the intended use, the receiving system and the obligations governing the exchange. Add any requirements for storage, retention and onward use that the parties need to resolve.
For a count request, agree the specification and how the result will be supplied. For a record transfer, agree the selected records, fields and destination. For partner access, specify who needs access, what they need to do and where the data must remain.
These requirements give the technical and commercial teams the same arrangement to assess. The technical data services page explains the work behind processing and delivery connections.
Assess the hosting and access arrangement
If the partner needs to run queries or combine datasets in a shared environment, scope the hosting, access and operating requirements explicitly. Specify where the data must remain, who needs access and what the partner needs to do.
For the Engine's current processing controls, review the governance mechanisms. Where certification matters, check the certificate holder and exact scope.
Questions about the exchange
Can we assess the inventory before transferring records?
Yes. The Engine can count eligible records against a live specification. Agree the criteria and the way the result will be supplied.
Can the recipient use its existing system?
Assess the receiving system and delivery route. The Integrations hub describes the available connection options.
What needs to be decided for direct access?
Who needs access, which tasks they need to perform, what information they may receive and where the data must remain. Use those requirements to assess the environment and arrangement.
Define the exchange you are willing to make
Tell us what the partner needs, the use you want to support and your environment requirements. We'll discuss the processing and delivery scope around that arrangement.