What is a Recipient?

Learning objectives

• You will understand what a Recipient is within LeadConduit.
• You will learn how Recipients are classified into Buyer, Standard, and Custom types and the scenarios for using each one.
• You will be able to explain the distinctions and practical implications of each recipient type.

Overview

Summary:
A Recipient is the final endpoint in a LeadConduit flow where processed and enriched lead data is delivered to an external system or partner.

Why it matters:
Recipients determine where your leads are sent and how they are handled. Whether the leads are delivered to a buyer’s system, routed through a pre-built standard integration, or managed by a custom solution, configuring the correct Recipient type ensures that lead data is properly received, tracked, and acted upon.

Practical examples

Example 1 – Buyer Step Recipients:
Scenario: A lead aggregator sells pre-qualified leads to multiple third-party buyers.

• Setup: Configure a Recipient Step specifically as a Buyer Step Recipient.
• Mapping: Map critical fields like name, email, and phone to meet the buyer’s submission guidelines.
• Outcome: Leads are routed directly to the buyer’s system, ensuring immediate follow-up; this configuration emphasizes buyers where the recipient is solely used for lead purchase transactions.

Example 2 – Standard Recipients:
Scenario: LeadConduit’s built-in integrations are used to send data to popular platforms like Salesforce or HubSpot.

• Setup: Select a Standard Recipient from the available pre-built integration options.
• Mapping: Use automatic field mappings for common data points such as first name, last name, and email, with the option to fine-tune if needed.
• Outcome: Leads are delivered in a consistent, pre-validated format that minimizes configuration effort and speeds up implementation.

Example 3 – Custom Recipients:
Scenario: Your leads need to be delivered to a unique system that is not supported by standard integrations, requiring a custom HTTP or API endpoint.

• Setup: In your flow, add a Recipient Step and choose the “Custom” option.
• Mapping: Manually define the integration type—such as a Custom HTTP POST using JSON—and map your lead fields to the recipient’s API parameters according to their documentation.
• Outcome: Lead data is transmitted exactly as specified, allowing for tailored processing and specialized reporting. This configuration caters to scenarios where both unique business logic and specialized data formatting are required.

Implications & applications

Key takeaways:

• A Recipient is the final delivery endpoint that receives your refined lead data.
• Recipients are classified into Buyer, Standard, and Custom types, each with distinct configuration and use-case scenarios.
• Proper field mapping and configuration in a Recipient Step are essential for accurate lead delivery and performance tracking.

Practical applications

• For lead buyers: Use Buyer Step Recipients to send leads directly to purchasing partners, ensuring fast follow-up and transparent transaction reporting.
• For efficient integration: Utilize Standard Recipients when working with popular platforms that offer pre-built integrations, streamlining the setup process.
• For tailored solutions: Create Custom Recipients when delivering leads to unique or non-standard destinations, providing flexibility with bespoke field mappings and data formatting.
• For comprehensive reporting: Correct recipient configuration guarantees that lead outcomes are accurately captured in LeadConduit’s dashboards, aiding in cost analysis and ROI measurement.

Frequently Asked Questions (FAQ)

What distinguishes a Buyer Step Recipient from other types?

A Buyer Step Recipient is specifically configured for delivering leads to lead buyers who purchase the leads. In contrast, Standard Recipients use pre-built integrations with common mapping setups, and Custom Recipients allow for fully tailored configurations to meet unique endpoint requirements.

Can I change a Recipient from Standard to Custom after configuration?

No, the integration type is determined at the initial creation of the Recipient Step. Changing the delivery method requires creating a new Recipient Step with the desired configuration.

How do I decide which Recipient type to use?

Use Buyer Step Recipients when your objective is to send leads directly to purchasing partners, Standard Recipients for effortless integration with popular platforms, and Custom Recipients when you need specific field mappings or when the target system is unique.

How important is field mapping in the Recipient configuration?

Field mapping is critical because it ensures that lead data is accurately transmitted in the format expected by the recipient system. Incorrect mappings can lead to data rejections, delivery failures, or inaccurate performance reporting.

Glossary