LeadByte Dynamic Redirects

What it does

By default, LeadByte delivery is asynchronous - the lead is queued and delivered in the background while the visitor continues through your normal thank-you flow. With Dynamic Redirect on, the lead is posted to LeadByte synchronously at submission, and the visitor is redirected to the URL LeadByte returns (typically a buyer's landing page). This is how you hand a lead to a buyer in real time - and optionally pass along values the buyer returns.

How LeadByte returns data

LeadByte nests buyer data two levels deep:

{
  "records": [
    {
      "status": "ACCEPTED",
      "buyers": [
        {
          "externalref": "https://buyer.com/thanks",
          "phone": "5551234",
          "company_name": "Acme"
        }
      ]
    }
  ]
}

The redirect URL lives at records[0].buyers[0].externalref   by default.

Basic setup

Funnel → Lead Delivery → your LeadByte integration.

1. Dynamic redirect - turn on. (Off = LeadByte stays fully async, unchanged.)
2. Response Redirect Field - the field inside records[0].buyers[0]   that holds the URL. Defaults to externalref  .
3. Fallback URL (optional) - where to send the visitor when the response has no valid URL. Leave blank to just continue the funnel's normal flow.

Submit → wait for LeadByte → redirect to the returned URL (or fallback).

Advanced Settings (optional)

These let you read specific values out of the buyer response, route on them, and forward them. They activate automatically once you add a response field or a routing rule.

Response fields — reading values from the response

This section pulls values out of the buyer's response (what LeadByte sends back), not the data your visitor typed on the form. Each row has two boxes:

• Left box = a nickname you choose. You reference it later as response:<name>   (in rules) and it becomes the query-param name when appending to the URL.
• Right box = the JSONPath - the exact location of that value in LeadByte's response.

How to fill in the right box: do one test post (or ask LeadByte / the buyer for a sample response), look at the JSON that comes back, and copy the path to each value. LeadByte's buyer values sit at records[0].buyers[0].<field>  .

The exact keys (phone  , company_phone  , …) are whatever LeadByte actually returns - match them to the real response. (A leading $.   is optional.)

Important: if the value you want is something the visitor submitted (their own company name/phone), it does not go here - Response fields only read the buyer's response. Sending the lead's own data to LeadByte is done in the integration's field mapping/payload.

Append response values to the URL

Turning on Append response values to URL reveals a checklist of your response fields. Tick the fields you want forwarded - each ticked field is added to the buyer's redirect URL as a query param.

• Param name = the field's nickname (left box); value = what came back.
• Example: with buyer_phone  , company_phone  , and company   ticked, and LeadByte returning those values plus externalref: https://buyer.com/thanks  , the visitor lands on:

https://buyer.com/thanks?buyer_phone=5551234&company_phone=5559876&company=Acme

So yes - it captures the values that come back and forwards them on the URL. Qualifiers:

• Applies only to the redirect URL LeadByte returns - not the Fallback URL, and not a URL chosen by a routing rule.
• Empty values are skipped.
• Existing params are never overwritten (if the buyer URL already has ?phone=…  , it's left as-is).

Routing rules

Conditions on your response fields that decide where the visitor goes, checked top to bottom - first match wins. Each rule routes to a step, child page, another funnel, or a custom URL.

response:status  equals  REJECTED  →  Custom URL: https://…/not-a-fit

Routing priority

1. Routing rules, in order.
2. If nothing matched and the response has a valid redirect URL → that URL (with any appended params).
3. Otherwise → the Fallback.

Loading screen

A branded "reviewing your results" spinner + Loading message shown while LeadByte responds.

Timeout

How long to wait, 1-30s (default 15). On timeout the fallback fires; the lead is still saved.

Fallback

On timeout or no match with no usable URL: Continue the normal flow, show a Message, route to a step/page/funnel, or a Custom URL.

Notes & gotchas

• The lead is always saved, even if LeadByte errors or times out - redirect never blocks capture.
• LeadByte uses JSONPath (buyer data is nested), unlike LeadProsper's flat keys.
• Works on the hosted page and embedded forms.