Keep the outcome connected to the bid.
Connect signed tracking calls to delivery and spend. Use a durable event spool to carry outcomes from intake to application and reporting.
Coming soon. Request early access.
An event becomes an accountable outcome.
Verify the tracking call.
Intake checks the signed bid token and parses the event, including exchange notices and VAST player events.
Record before acknowledging.
Verified events enter a local durable spool. Consumers apply effects and acknowledge their progress.
Apply and aggregate.
Billable effects update spend, permitted impressions update caps, and delivery aggregates feed reporting.
Account for retries and delayed signals.
Separate wins from billing.
A win notice is not itself a spend event. The first accepted billable signal, billing notice or VAST impression, accounts spend for the bid.
Replay unacknowledged work.
Spool consumers resume from their acknowledged positions. In a split deployment, events can be forwarded to control for aggregation.
Keep a diagnostic trail.
Sampled auction captures use the adtrace format, while delivery aggregates make outcomes available to the control plane.
Is this exactly-once event delivery?
The spool uses at-least-once delivery. Deduplication and once-per-bid accounting handle repeated signals. That is distinct from promising exactly-once transport across the whole deployment.
Switch to a modern,
affordable DSP.
Buy programmatically or go direct, with agentic workflows and validation included.