Route leads via API or funnel builder based on form submissions, with conditional, base, failover, thresholds, and authentication settings.
Form Routing sends lead data to endpoints via API calls or built-in funnel forms. You configure routing rules, filters, CAPs, rotational thresholds, and authentication within each endpoint’s Form Settings.
Pingtree offers three routing models for form distribution:
Base Routing
Add an endpoint here if no custom routing rules apply (excluding filters, CAPs, response mapping). Leads flow to all base endpoints in priority order.
Conditional Routing
Use this when custom IF/THEN rules are defined. Only leads matching those conditions route here.
Failover Routing
Configure endpoints here to catch leads not sold by Base or Conditional routing. Only applies if earlier models do not accept the lead.
Route Lead A (California) to a specific endpoint and Lead B (others) to a fallback:
Endpoint A
Failover Endpoint
Routing Setup
Distribute leads by percentage across multiple endpoints:
Combine conditional, base, and failover logic:
Pingtree processes in order: Conditional → Base → Failover.
Some endpoints require a temporary token for each POST:
Form Routing is activated when:
![REPLACE HERE: Form Routing Flow Diagram]