LeadConduit is the foundation of the ActiveProspect platform. It is a real-time data integration hub that allows you to filter, enhance, and deliver leads to any system. You can build complex lead flows using most any data enhancement/verification service and then make real-time decisions on your leads with rules-based logic.
LeadConduit integrates with lead vendors and allows you to reject leads that don’t meet your criteria in real-time.
Here's what you need to get started
- Compile a list of all the data collected from your Sources (Vendors)
- Make a list of the lead Sources (Vendors) from which you buy leads, including your primary contact and their contact information (email/phone)
- What data is required by your contract?
- Are there other Acceptance Criteria?
- e.g. Only accept leads when State = TX
- e.g. Only accept leads when LTV < 90%
- e.g. Phone Number Verification to Automatically Reject numbers known to be non-contactable
- e.g. Campaign ID = X based on value/range/source
0: Start a new Flow
Flows are where you configure the order of operations for processing your leads. You can use as many flows as you need. Typically you'll want to create a new flow (versus edit an existing flow) whenever you need a completely different order of operations to process leads.
Once you've identified the data that's collected from your lead Vendors and/or your own forms, you need to list this information in the flow so LeadConduit knows what data you're expecting and when (if) to perform basic validation (e.g. Is the phone number / email address / postal code a known, valid format?). LeadConduit has many standard fields to account for most of your needs, but you can create custom fields when needed.
2: Sources (Vendors)
Next, you add all the Sources to the flow. LeadConduit has a large number of standardized Sources, but if you can't find what you're looking for you can create a custom Source and add it to the flow.
3: Inbound Field Mapping
For simplicity and consistency, we recommend using the LeadConduit Standard Field Names when submitting data to LeadConduit, but you won't always have control over the Field Names. When that's the case, you need to normalize the custom field names to standard field names with Inbound Field Mapping.
4: Required Fields and Acceptance Criteria
Setting Required Fields and other Acceptance Criteria (e.g. Only accept leads when State = TX) allows you to enforce your data requirements up front so you don't waste time and money on leads you'll never be able to convert.
5: Adding and Configuring Steps
Now that you've set all the requirements for a lead entering the flow, you need to choose the order of operations for processing your leads. This is where you add data enhancement services, set up deduplication, log data to a batch file, configure delivery to a CRM / Email address, and catch errors/failures on any step.
6: Delivering Leads
Once your lead data is cleansed and enriched you need to deliver it to an email/batch file / CRM or other systems so it's actionable. Although there several pre-build connections to common services you can set up a delivery to most any system that accepts a GET or POST request, including JSON and some forms of XML.