How it works
- In the ping phase, your source sends partial lead data (typically just enough to identify the lead type and location). Juiced auctions this data to your customers, collecting bids in real time.
- In the post phase, your source sends the complete lead data once a winning bid is determined. The lead is assigned to the winning customer, funds are transferred, and everyone’s happy.
Pinging Juiced from your sources
Your sources run ping-post against Juiced with the v1 API. They pingPOST /api/v1/ping with the fields marked required for ping, and get back the outcome and, for non-vendor sources, the bids.
price instead of bids. To post the lead, the source sends the full lead to POST /api/v1/leads with the ping’s id as ping_id. See Submit a Ping and Submit a Lead for every field and response.
Sources still pinging
/api/ping are on the deprecated legacy API, which answers with a UUID ping_id and a message such as Match found. It keeps working, but new integrations should use v1. See Moving from legacy to v1.Partner integrations
Partners are external systems that receive your leads. When you configure a partner integration, you set up both ping and post configurations to match their API requirements.Request mapping
Each partner has their own field names and payload structure. Request mapping lets you transform Juiced’s lead data into whatever format your partner expects. Use merge fields in double curly braces to insert lead data.Using ping response data in posts
Some partners return data in their ping response that must be included in the subsequent post request, such as session IDs, tracking tokens, or campaign identifiers. When configuring a post request mapping, you can reference fields from the ping response using theresponse. namespace.
Ping response fields are only available when configuring post requests. They won’t appear in ping request mappings since no response exists yet at that point.
Offer penalty percentage
Sometimes you want to give certain partners a competitive disadvantage without changing what they actually pay. The offer penalty percentage does exactly this. It reduces a partner’s offer score without affecting the charged amount. For example, say a partner submits a $100 offer and has a 25% penalty.- Their offer score becomes $75 (used for ranking)
- Their charged amount stays $100 (what they actually pay if they win)
- A partner has lower lead quality or conversion rates
- You want to favor other partners without explicitly blocking anyone
- You’re managing partner relationships while maintaining pricing transparency
The penalty percentage is snapshotted on each offer, so changing a partner’s penalty only affects future offers, not ones already in the system.
Offer scoring
When multiple partners respond to a ping, their offers are ranked by score. The highest score wins. By default, the score equals the offer amount, but penalties can reduce this.
In this example, Partner A wins even though Partner B offered more money, because Partner B’s penalty brought their score below Partner A’s.
You can see every offer for a lead, with its penalty and score, in the Offers dialog on the lead’s incoming log.
Seeing ping-post traffic
Every ping and post leaves a trail you can inspect.- In Incoming logs, each ping or post a source sends to you starts an incoming log. The Ping, Post, and Honored columns tell you at a glance whether the ping matched and whether its offer won on the post.
- Ping and post inspectors show the exact request and response. Open a ping or post from its log (or from a lead’s View Ping / View Post) to see them. See Ping and post inspectors.
- Outgoing logs list every ping and post Juiced sends to a partner, with the partner’s response, response code, and timing. See Outgoing logs.





