Send LeadByte leads to Juiced

Before you start

• In LeadByte: the campaign the leads arrive in, and a buyer record for Juiced to select under Buyers & Financials (How to create a Buyer).
• In Juiced: a source, its bearer token, and the endpoint and field names from View API Spec.
• Pick the source type. Use Vendor when a vendor runs the LeadByte account and sends you leads, and Internal when the leads are your own. A ping returns its id in data.id, and the post carries it as ping_id. A vendor source reads its price from data.price (ping reference).
• Optional partner header. If Juiced gave you a partner ID for partner-attributed traffic, add X-Partner-Id. Leave it out otherwise.

Step by step

1. Create a source in Juiced and copy a token

   Go to Ingest > Sources > New source, set the Source type, turn on Test mode and click Create source. On the Authentication tab click New bearer token > Create token and copy it. Open Overview > More actions (⋯) > View API Spec for the endpoint and field names. See setting up a source.

2. Add a new delivery

   Open the Manage Deliveries tab and click Add New Delivery. Enter a Reference, set Trigger to When lead arrives (automatic), pick the Campaign, and choose Direct Post as the Action (or PingPost, step 6). Set Remote system (shown once Direct Post is selected) to JSON and URL to https://usejuiced.com/api/v1/leads (Deliveries Explained).

3. Select Juiced as the buyer

   Under Buyers & Financials, select the Juiced buyer. To record the price Juiced returns, choose Dynamic Revenue in the delivery settings, select JSON as the response type and enter data.price as the field that holds the revenue (check the path syntax in your account; Dynamic Revenue). Add caps if you need them.

4. Map the fields

   Under Custom Data Mappings, click Add New Mapping for each field: the Input Field is your campaign field and the Output Field is the Juiced key, such as first_name. Use Options for formats such as phone format.

5. Add the header and success responses

   In Advanced Settings, add Authorization with Bearer and your token, plus Accept: application/json. Under Remote System Response, add "accepted" (with the quotes) with Match By: Keyword and tick Success. Keyword matches any response that contains the text, so keep the quotes. Add "rejected" and "duplicate" as reject responses (Remote System Response).

6. Set up PingPost (optional)

   With the PingPost action, create the ping request to https://usejuiced.com/api/v1/ping with only the fields marked Required for ping (always zip) and set the ping response type to JSON. Every valid ping returns 200, so set the ping success requirement on data.status equal to matched. LeadByte's article shows the condition labels only in a screenshot, so check in your account. In the post, send ping_id with the value {$ping.data.id}, following LeadByte's dotted form for nested ping values (PingPost).

7. Send a test delivery

   Send a test lead with zip 00001 (accepted) and one with 00003 (rejected); LeadByte requires a test before the delivery can leave Saved. To see Juiced's reply in LeadByte, click the LeadID on the Lead Screen and check the response box. Check the lead in Juiced too, under Entries > Incoming logs with the Test only filter. Then turn off Test mode in Juiced and enable the delivery.

Field mapping

Example request

POST https://usejuiced.com/api/v1/leads
Authorization: Bearer <your token>
Content-Type: application/json
Accept: application/json

{
  "ping_id": "ping_01HZX4K2M8",
  "first_name": "Jane",
  "last_name": "Doe",
  "email": "jane@example.com",
  "phone": "5555550100",
  "zip": "00001"
}

For a Direct Post delivery, leave out ping_id. See the leads and ping API references.

Response parsing

The data.status values are Juiced's default mapping. Confirm them on your source's API spec and against a real response on the Lead Screen.

TrustedForm and Jornaya

If your LeadByte campaign stores a TrustedForm certificate URL or a Jornaya LeadiD, add a field such as trusted_form_cert_url or jornaya_leadid to the Juiced lead category or source, mark it Deliverable if your buyers ask for it, and add a Custom Data Mapping for it. See passing TrustedForm and Jornaya to Juiced.

Troubleshooting

• Every lead counts as sold. The success response matches on HTTP Status. Match by Keyword on "accepted" instead.
• Unauthorized (401). The header in Advanced Settings has a missing or doubled space after Bearer, or a pasted line break. A new Juiced token expires the old one 24 hours later.
• No revenue recorded. Dynamic Revenue is not set to JSON with the field data.price.
• 422 on the post after a ping. Read error.code on the Lead Screen: ping_mismatch means the post does not match its ping. Check that ping_id carries {$ping.data.id} and the post repeats the same ping fields.
• The delivery will not enable. LeadByte needs a successful test delivery first.

More fixes in webhook troubleshooting.

Frequently asked