Traffic
What your bidders are reading
Catalogue views, search terms, time-on-lot, device, source — the upstream signal that explains where attention is going before a single bid is placed.
Data domains
Above-the-funnel signal
The Traffic domain captures every catalogue view, search, and filter your visitors run — on the public website and inside the native iOS and Android apps — and aggregates them per-lot, per-category, and per-session. It's the upstream signal: what people are interested in, before they've committed to a bid.
Pair it with the Lots and Bids domains and you can answer questions the bid book alone can't: where the interest is concentrating in the lead-up to a sale, which search terms are converting to bids, and which catalogues are over- or under-performing relative to attention.
Ask your data
From a question to a search-term conversion ranking
Ask which catalogue searches actually turn into bids. The MCP server joins anonymous traffic to identified bid events and ranks the terms by conversion.
Access & governance
Aggregate-first, identity-aware
Traffic data is most useful in aggregate. Individual session identity is hashed, not linked back to a named customer unless the visitor was signed in and explicit consent applies.
Aggregate counts (views per lot, search-term ranking) are open to all analyst roles.
Joining traffic sessions to a named customer requires both the customer's consent and the `customers.read.pii` capability.
Raw event-level traffic is retained for 90 days; pre-aggregated rollups are retained indefinitely for trend analysis.
Related domains
Traffic feeds every other domain
Let's talk
Ready to modernize your auction house?
Book a personalised demo and see Auction Rabbit tailored to your sale calendar