Delayed Revenue Event
A delayed revenue event is the point at which money is actually realised in a business whose acquisition event and cash event are separated by time and by system boundaries. The advertising platform observes the earliest event in the path; the revenue lands in a different system, on a different object, under a different identifier. Instrumenting it means carrying a durable identifier across every handoff and reconciling backwards from the ledger that holds the cash, rather than forwards from the click.
Definition
In a business with a delayed revenue event, the sequence from acquisition to cash crosses more than one system of record, and the last system in the sequence is the only one holding money. Because advertising platforms can only observe events occurring on surfaces they instrument, the reported conversion is always an upstream proxy. The gap is not primarily a timing problem: even with unlimited patience, a click cannot be joined to a payment unless a shared identifier survived every handoff in between. The identifier, not the delay, is the engineering object. Subscription renewal, insurance commission, professional-service realisation and contingency-fee recovery are all instances of the same shape.
Why it matters
Where the delay is treated as an analytics inconvenience, one response is to optimise against an earlier proxy event. That works only if the proxy's relationship to realised value is stable, and where value is set by attributes the acquisition layer never observes, that relationship is not stable. Naming the delayed revenue event explicitly changes what gets built: instead of a reporting dashboard, the deliverable becomes an identifier chain and a reconciliation cadence spanning the systems that hold the enquiry, the delivery record and the ledger.