Skip to main content
Every request that touches Juiced leaves a receipt. When a source pings or posts, Juiced records an incoming log. When Juiced pings or posts to a partner, or sends a lead to a customer’s webhook, it records an outgoing log. Together they answer the two questions you’ll ask most, “What did they send us?” and “What did we send them?” Both live under Entries in the sidebar, next to Leads.

​
Incoming logs

An incoming log (also called a distribution flow) is one run of the pipeline, covering a ping, a post, the lead it created, and every distribution stage the lead visited. Open Incoming logs to see them all, newest first.
Incoming logs list with Source, Ping, Post, Lead, Honored, Recipient, and Sold For columns, a search box, and a Filters buttonIncoming logs list with Source, Ping, Post, Lead, Honored, Recipient, and Sold For columns, a search box, and a Filters button
The search box matches source and recipient names. Click Filters to narrow the list by any of these.
  • Ping status and Source
  • Has Ping, Ping Honored, Has Post, Has Lead, and Assigned (each Yes or No)
  • Recipient Type (Customer or Partner) and Channel Type (Bid, Customer, or Ping/Post)
  • Test mode (real traffic by default, or test only)
  • Created date range
Filters are kept in the page URL, so you can bookmark or share a filtered view.

​
Inside an incoming log

Click a row to open it. The page title is the log’s ID (it starts with dflow_).
Incoming log with an Inbound, Routing, and Outbound timeline, Details and Records in the sidebar, and an empty Outgoing logs tableIncoming log with an Inbound, Routing, and Outbound timeline, Details and Records in the sidebar, and an empty Outgoing logs table
  • Timeline has three lanes. Inbound holds what the source sent (the ping and post), Routing holds what Juiced did with it (lead created, each stage’s result, who won), and Outbound holds pings and posts Juiced sent to partners. Each card describes its event in plain language and links to the related ping, post, or lead where there is one.
  • Details shows the flow’s Status, Mode (Live or Test), Duration, and when it was Initiated.
  • Records links to the Source, Lead, Recipient, Ping, and Post, plus Offers (the number of offers made, with a View link).
  • Outgoing logs lists every partner ping and post this flow triggered, with date, type, partner, result, and price.

​
Offers

Click View next to Offers to see every offer the lead attracted. The dialog lists each bidder’s Name (the winner is badged Winner), Channel, Bid, Effective price, Penalty (hover it for the reason), Score, Discount, Charged, and Status. It’s the fastest way to see why one buyer beat another. See ping-post for how offers are scored.

​
Outgoing logs

Outgoing logs lists every request Juiced sent out, including pings and posts to partners and webhook deliveries. Rows are grouped by the incoming log they belong to, with a View log link to jump back to it.
Outgoing logs list grouped by log number, with date, type, partner, result, price, and a View log link on each rowOutgoing logs list grouped by log number, with date, type, partner, result, price, and a View log link on each row
The search box matches partner names and endpoint URLs. Filters cover these options.
  • Type (Ping, Post, or Webhook)
  • Result (Pending, Succeeded, Duplicate, Rejected, HTTP error, Timeout, Validation failed, or Error)
  • Partner
  • Test mode (real traffic by default, or test only)
  • Created date range
Click a row to see the full exchange.
Successful outgoing post with the request payload, the partner's response, and Details in the sidebarSuccessful outgoing post with the request payload, the partner's response, and Details in the sidebar
  • Request shows what Juiced sent, as Payload, Headers, or Raw body.
  • Response shows what the partner sent back, as Body, Headers, or Raw body. When something went wrong on our side of the wire, an Error tab shows the error class and message.
  • Details lists Result, Type, Mode, Partner, Price, Response code, Method, Format (JSON or Form), Duration, Timestamp, and Endpoint.
  • Records links to the incoming log.
Outgoing post with an HTTP error result, a 503 response code, and a response body reading Service temporarily unavailableOutgoing post with an HTTP error result, a 503 response code, and a response body reading Service temporarily unavailable

A failed post, where the partner's endpoint answered with a 503.

​
Ping and post inspectors

Pings and posts don’t have their own list pages. You reach them from an incoming log (the Ping and Post links under Records, or View ping / View post on a timeline card), or from a lead’s View Ping and View Post actions.

​
Ping inspector

Shows exactly what a source sent to the ping endpoint and what Juiced answered.
Ping inspector with the request payload, a response body containing a price and Match found message, and Details and Records in the sidebarPing inspector with the request payload, a response body containing a price and Match found message, and Details and Records in the sidebar
  • Request shows the Payload and Headers, plus Validation errors when the ping was rejected.
  • Response shows the Body and Headers Juiced returned, including the price offered.
  • Details lists the response Status code, Mode, Source, Method, Timestamp, and ping ID.
  • Records shows the Source, Lead category, Lead type, County, and Postal code the ping resolved to.

​
Post inspector

A post (also called a submission) is the full lead a source sent to the leads endpoint. Every post is stored as received, whether or not it became a lead.
Post inspector with the request payload, Juiced's response, and Details and Records in the sidebarPost inspector with the request payload, Juiced's response, and Details and Records in the sidebar
  • Request shows the Payload as received (even fields that don’t map to anything in your lead category), plus Validation errors when the post was rejected.
  • Response shows the Body, Headers, and Raw body Juiced sent back.
  • Details lists Status (Pending, Accepted, or Rejected), Mode, Source, Response code, Duration, Timestamp, and ID.
  • Records links to the Lead the post created, if any.
Test traffic is hidden by default. When a vendor is testing their integration, set the Test mode filter to Test only on Incoming logs to find their requests.

​
Permissions

Each log screen has its own permission, so you can give a support teammate access to the logs without access to everything else. Incoming logs, outgoing logs, pings, posts, and offers are each controlled separately in roles.