Concepts

Concepts

Understanding how LeadConduit's concepts work together is crucial for effective platform usage. This guide maps the relationships between all twelve core concepts.

Conceptual Layers

LeadConduit's architecture consists of four primary layers, each building on the previous:

1. Data Foundation Layer

These concepts handle how data enters, gets validated, and becomes accessible:

• Fields - Define what data can be collected
• Types - Parse and validate that data
• Templates - Make data dynamically accessible

2. Business Logic Layer

These concepts control decision-making and data transformation:

• Rules - Universal decision engine
• Pricing - Financial calculations
• Mappings - Data transformation

3. Identity & Integration Layer

These concepts manage who participates and how they connect:

• Entities - Identity system
• Integrations - Technical connections
• Flows - Orchestration engine

4. Analytics & Data Access Layer

These concepts provide visibility and analysis:

• Events - Complete audit trail
• Reporting - Business intelligence
• Exports - Bulk data access

Key Relationships

Fields ↔ Types

Fields reference types to define how data is parsed and validated. Every field has a type that determines its behavior.

Types ↔ Templates

Templates access the parsed data that types create. Simple variable mode preserves the typed data, enabling type-aware operations.

Rules → Templates

Rules depend on templates for dynamic value access. Templates provide the data that rules evaluate.

Rules Usage Pattern

The rule engine is used throughout LeadConduit:

• Acceptance Criteria: Rules gateway at source and flow level
• Volume Caps: Rules determine which leads count toward limits
• Pricing: Rules with "last match wins" for tier selection
• Filter Steps: Rules control flow routing and termination
• Mappings: Rules control when transformations apply

Pricing Dependencies

Pricing uses rules for conditional tiers and is applied at:

• Source level (purchase price)
• Recipient level (sale price)
• Four-layer precedence: source service → source rules → flow service → flow rules

Mappings → Templates + Rules

Mappings orchestrate both:

• Templates provide the values to map
• Rules determine when mappings apply
• Used at source (inbound) and recipient/destination (outbound)

Flow Steps Dependencies

Within flows, different step types have specific dependencies:

• Filter Steps → Rules determine routing logic
• Enhancement Steps → Integrations to call services
• Recipient Steps → Integrations for delivery, Mappings for format
• Destination Steps → Entities define who, Integrations define how

Entities ↔ Integrations

Entities declare which integration modules they support. The integration modules define the technical implementation.

Events → Reporting → Exports

• Events are the raw data source
• Reporting aggregates events into metrics
• Exports extract event details for external use

Flows ↔ Everything

Flows are the orchestration layer that brings all concepts together:

• Use entities for sources and destinations
• Apply types through field definitions
• Evaluate rules for decisions
• Use templates for dynamic behavior
• Apply mappings for data transformation
• Generate events for visibility

Data Flow Through Concepts

1. Lead Arrival

• Entity (source) submits data
• Integration (inbound module) receives it
• Fields define expected data structure

2. Data Normalization

• Mappings rename vendor fields to standard names
• Types parse and validate each field
• Templates may transform values

3. Pre-Processing Business Logic

• Rules in acceptance criteria determine if lead qualifies
• Pricing calculates purchase cost using rule layers
• Volume Caps check limits using rules
• Templates provide dynamic values for all evaluations

4. Lead Processing

• Flow orchestrates the journey through configured steps
• Rules in filters control routing
• Integrations call external services for enhancement
• Mappings transform data for each destination

5. Lead Delivery

• Entities (destinations) receive the lead
• Integrations (outbound modules) handle delivery
• Mappings reshape data to match requirements
• Pricing records the revenue

6. Visibility & Analytics

• Events capture every action with full data snapshots
• Reporting transforms events into business intelligence
• Exports provide detailed data for external analysis

Concept Dependencies Matrix

Important Concept Interactions

Data Availability Timeline

• Raw data arrives without prefixes
• After parsing: standard fields get lead. prefix
• Custom fields never have prefixes
• Appended data gets namespace of the service
• TrustedForm Decisions only available in pre-processing

Outcome Types Across Concepts

• success - Business logic passed
• failure - Business logic failed (fixable)
• error - Technical problem (retry might work)

Special Behaviors

• Pricing rules use "last match wins" (different from other rules)
• Types validate but don't block (set valid flag)
• Templates have three modes based on content
• Events capture complete snapshots, not just changes

Understanding these relationships is key to mastering LeadConduit. Start with Flows and explore outward based on your needs.