Bid history
How each bidder actually behaves
Across every sale a bidder has touched — their wins, their drop-outs, their head-to-head competitors, their bid cadence — the per-customer view that turns raw bids into a portrait.
Data domains
Aggregated behaviour by person
Where the Bids domain stores every individual bid, the Bid History domain rolls those bids up per customer, per sale, and per category. It's the lens you use to answer 'who is this bidder, really' — their typical entry point in a lot, where in the increment they drop out, the consistency of their wins, the categories they keep returning to.
It also captures the head-to-head graph: which paddles tend to bid against this one, who outbids them most often. That graph is the foundation of better invitations, smarter segmentation, and earlier warning when a high-value bidder is drifting away.
Ask your data
From a question to a churn-risk shortlist
Ask which named bidders are losing momentum. The MCP server scans the per-customer history, flags the downward trend, and returns the shortlist.
Access & governance
Behavioural data, masked by default
Bid History is powerful for retention, sensitive when paired with identity. Pre-aggregated metrics are openly accessible; per-customer-identifiable history requires explicit PII access.
Aggregate distributions (win rate buckets, cadence histograms) are available to all analyst roles.
The `primary_rivals` field returns de-identified IDs by default; joining to names requires both PII capability and rival consent.
Drop-out-risk scores are surfaced only to roles with the `customers.engage` capability so they can act on the prediction.
Related domains
History is the bridge from bids to action
Let's talk
Ready to modernize your auction house?
Book a personalised demo and see Auction Rabbit tailored to your sale calendar