LEADCONDUIT INTEGRATION
LeadsBridge
Move lead data from Ad platforms to marketing apps automatically & in real time for timely outreach and better results.
SPECIFICATION
Fields & configuration
The exact fields LeadConduit uses, appends, and the configuration options available for this integration.
Move lead data from Ad platforms to marketing apps automatically & in real time for timely outreach and better results.
Response Fields
LeadConduit returns the following data to the lead source.
| Response Field | Description |
|---|---|
Id | The lead identifier that the source should reference |
Outcome | The outcome of the transaction (default is success) |
Reason | If the outcome was a failure, this is the reason |
Price | The price of the lead |
Fields
The following fields are used by this integration and automatically added to your flow when missing.
| Field | Description |
|---|---|
| Trustedform Cert Url | URL to the TrustedForm Certificate |
| Reference | External lead identifier |
| Original Source | Source integration used in the bridge |
| Source Timestamp | Lead creation date and time |
| Wildcard variable for custom fields |
Move lead data from Ad platforms to marketing apps automatically & in real time for timely outreach and better results.
Response Fields
LeadConduit returns the following data to the lead source.
| Response Field | Description |
|---|---|
Outcome | Success or failure |
Reason | If the outcome was not success, this is the reason |
Warnings | Array containing warning messages, such as "Invalid input" or "Missing input" |
Queue Id | If the request is successful, this is the Queue ID provided by LeadsBridge |
Warnings Pretty | Data from the warnings array, combined into one string |
Fields
The following fields are used by this integration and automatically added to your flow when missing.
| Field | Description |
|---|---|
| Url | Server URL |
| Method | HTTP method (POST, PUT, DELETE, or PATCH; default: POST) |
| Basic Username | HTTP Basic Authentication user name |
| Basic Password | HTTP Basic Authentication password |
| Json Property | JSON property in dot notation |
| Json Parameter | To "stuff" the JSON into a parameter and send as Form URL encoded, specify the parameter name |
| Nested Extra Parameter | Extra JSON object that is included in the url encoded request body. Only added when the "json_parameter" mapping is enabled. |
| Extra Parameter | Extra parameters to include in URL, only used when JSON Parameter is set |
| Outcome Search Term | The text to search for in the response. When found outcome will be "success". Regular expressions are allowed. Pro tip: Use Outcome on Match to use this term to search for "failure" instead of "success". |
| Outcome Search Path | Narrow the search scope using dot-notation path (for JSON responses), XPath (for XML responses), or CSS selector (for HTML responses) |
| Outcome On Match | The outcome when the search term is found - "success" or "failure" or "error" (default: success) |
| Reason Path | The dot-notation path (for JSON responses), XPath location (for XML responses), or regular expression with a single capture group, used to find the failure reason |
| Price Path | The dot-notation path (for JSON responses), XPath location (for XML responses), or regular expression with a single capture group, used to find the lead price |
| Fallback Price | The fallback price to use if the price_path fails to parse a price from the response. |
| Reference Path | The dot-notation path (for JSON responses), XPath location (for XML responses), or regular expression with a single capture group, used to find the reference ID |
| Default Reason | Failure reason when no reason can be found per the optional Reason Path setting |
| Header | HTTP header to send in the request |
| Send Ascii | Set to true to ensure lead data is sent as ASCII for legacy recipients (default: false) |
| Capture | A named regular expression with a single capture group, used to capture values from plain text responses into the named property |
| Response Content Type Override | Override response's Content-Type header with custom value. |
| Cookie Search Term | The text to search for to identify an HTTP cookie. Usually the cookie 'name' is sufficient; regular expressions are allowed |
| Follow Redirects | If true, follow redirects even on methods other than GET (default: false) |
| Timeout Seconds | Produce an "error" outcome if the server fails to respond within this number of seconds (default: 360) |
GETTING STARTED
Add LeadsBridge in three steps
Add the integration
Find LeadsBridge in your LeadConduit flow and add it as a step, no IT or code required.
Map your fields
Match your lead data to LeadsBridge's fields. Required fields are added to your flow automatically when missing.
Route & go live
Match your lead data to LeadsBridge's fields. Required fields are added to your flow automatically when missing.
KEEP EXPLORING
More integrations
Start routing leads with LeadsBridge
Connect LeadsBridge to your lead flow in minutes, or tell us what else you need and we'll support it.