Receive requests and validate version, impression, site, app, device, privacy and format.
Workflows
Every transaction becomes replayable.
This page explains the full transaction loop from request intake to commercial review, with facts and evidence at every step.
Runtime Flow
From request to evidence package.
This chain is the product backbone of the TradeMesh website.
Turn raw requests into auction context with inventory, floor, deal, privacy and device data.
Explain candidate seats, exclusions, policy impact and endpoint health.
Call DSPs, select winners, validate creative policy and assemble responses.
Link win, impression, click and loss notices to ledger records.
Privacy, creative, supply-chain, report export, approval and publishing events leave evidence.
Trace View
Business and engineering can read the same chain.
Each workflow needs runtime facts, commercial interpretation and reviewable evidence.
IngressPOST /ortb/prod/sep_demo_main/bidaccepted
NormalizeAuction context with floor, privacy and deal datavalid
RouteCandidate seats, exclusions and policy impactmatched
AuctionDSP response with seatbid evidencebid
EvidenceBI, ledger, notices, creative and privacy decisions linkedready
Operating Playbooks
Turn anomalies into actionable tasks.
The workflow page should show how common production issues are located, assigned and reviewed.
Inspect placement, geography, device, floor, privacy status and endpoint health to separate inventory issues from demand issues.
Split by DSP, geography, format and request size to identify endpoint, network or request-shape causes.
Replay differences through requests, win notices, impression notices, ledger and report exports.
Connect creative policy, scan evidence, landing-page limits and complaints to seats and routing.
State Machine
Every request moves through observable states.
The state machine tells engineering where the chain is stuck and gives business explainable customer outcomes.
Version, impression, site or app, device and privacy fields are available.
Inventory, floor, deal, privacy and seat capability match at least one demand path.
Endpoint responses, timeouts, no-bids and seatbid structure become runtime facts.
Notices, reports, ledger and adjustments enter the finance loop.
Alerts and Resolution
Do more than alert. Convert alerts into evidence tasks.
ADX runtime alerts need context, otherwise teams keep chasing logs.
Fill, timeout, error rate, missing notice, ledger gap or creative risk crosses a threshold.
Slice by customer, endpoint, placement, geography, seat and policy.
Adjust routing, throttle, roll back config, pause seats or repair authorization records.
Write resolution back into customer review, finance reconciliation and audit evidence.