Prerequisites
- A role that can view incoming logs. If Incoming logs isn’t under Entries in your sidebar, ask an admin on your account.
- A question in mind. Logs are most useful when you open them with one, like “Why didn’t customer X win this lead?”, “Why was this lead unsold?”, or “Did the ping come in?“
1. Open Incoming logs
In the sidebar, expand Entries and click Incoming logs. The page lists every flow, newest first, with one row for every ping or post that came in, whether or not it ended up assigned.
2. Read the columns
3. Filter to narrow the search
The search box matches source and recipient names. Click Filters for the rest. These are the ones you’ll actually use.- Created (from/until) scopes to a specific window. It’s always the first filter to set during an incident.
- Source checks a single source’s health. Deleted sources are still listed, tagged “(Deleted)”.
- Ping filters by
Matched,No Match,Pending, orError. “My ping integration isn’t matching” starts here. - Ping Honored is Yes or No. No is the interesting one, showing flows where the ping’s winner didn’t end up with the lead.
- Has Ping / Has Post / Has Lead / Assigned are presence filters. “Show me flows that had a ping but never became a lead” is Has Ping set to Yes and Has Lead set to No.
- Recipient Type and Channel Type narrow to customers or partners, and to bids, direct customer assignment, or ping/post.
- Test mode shows real traffic by default. Switch to Test only to see only test flows.
4. Open a single log
Click any row to open the log. It has three parts.
Details and Records (sidebar)
Details shows the flow’s Status (for example Distributed, No Match, On Marketplace, Audit, or Error), its Mode (Live or Test), how long it took (Duration), and when it was Initiated. Records links to everything the flow touched, including the Source, Lead, Recipient, Ping, and Post, plus the number of Offers. A dash means that step didn’t happen. No ping means a direct post. No post means the ping matched but the full lead never arrived. No lead means the flow stopped before a lead was created, usually because the post was rejected.The timeline
This is the heart of the log. Events are laid out top to bottom in three lanes.- Inbound shows what the source sent, meaning the ping and the post.
- Routing shows what Juiced did, including the lead being created, each distribution stage’s result, and the final outcome.
- Outbound shows pings and posts Juiced sent to partners.
Outgoing logs
Below the timeline, Outgoing logs lists every partner ping and post this flow triggered, with the result and price. Click a row to see the full request and response. See Outgoing logs.5. Check the offers
Click View next to Offers to see every offer the lead received. It lists each bidder’s Bid, Effective price, any Penalty (hover it for the reason), Score, Discount, what was Charged, and their Status. The winner is marked Winner. This is where “why did customer A beat customer B?” gets answered. Offers are ranked by score, not raw bid, so a penalty can push a bigger bid below a smaller one. See ping-post for how scoring works.6. Jump to a log from a lead
If you already have the lead open, there’s a shortcut. From Leads, open the lead and choose View Log from its More actions menu. You’ll land directly on that lead’s log. This is the fastest path when a support question names a specific lead.7. Common debugging patterns
”Why didn’t customer X get this lead?”
Open the lead’s log and click View next to Offers. If the customer is listed, compare their score and status with the winner’s. If they’re not listed at all, they never made an offer. Check that their bid covers the lead’s location and lead type, and that it’s active and funded. The bid’s status usually tells you why it isn’t receiving leads.”Why was this lead unsold?”
Look at the Routing lane. Each stage card says whether it found matches and, if not, why. If every stage came up empty, nobody’s bid, partner, or rotation fit the lead. If the last card says the lead went to the marketplace and went unsold, the auction ended without a taker.”Why is this lead sitting in Audit?”
Look for the stage card from your Audit stage. The lead matched that stage’s eligibility conditions and is waiting for you to review it.”Why did the ping match but the post not assign?”
Check the Post record. If it was rejected, open it and look at Validation errors, which usually show a required field was missing. If the post was accepted, follow the Routing lane to see which stage passed on it.”Did this source’s ping integration even fire?”
Filter by Source, set Has Ping to Yes, and narrow Created to the last hour. Zero rows means no pings came in, so the source’s integration didn’t call Juiced. Rows with anError ping status mean the ping was malformed, so open one and check the ping’s Validation errors.
”Show me everything that went to customer Y today”
Search for the customer’s name and set Created to today. The Sold For column gives you each lead’s charged amount.What happens next
Logs are a reactive tool, since you open them when something needs explaining. A few habits pay off.- Bookmark a filtered view. Set Assigned to No and bookmark the page for a one-click “what didn’t sell today” review.
- Triage Error rows first during a morning health check. They’re flagged with an Error badge on the Source column and mean something went wrong while the flow ran.
- Check outgoing logs for partner problems. When a partner says they never got a lead, Outgoing logs shows exactly what was sent and what came back.
- Correlate with location analytics. A county showing zero leads assigned despite active bids is worth checking against the logs to see whether flows are happening there and failing, or no traffic is arriving at all.