Stream commerce activity

Using the platform event stream as a reporting feed — which events carry reporting value, registering an endpoint, verifying a delivery, and what at-least-once delivery does to your numbers.

Stream commerce activity

The event stream

What the stream is, what a delivery carries, and what it is and is not good for in reporting.

Event types for reporting

Which topics carry reporting value, and what to record from each.

Register an endpoint

A Cockpit action — the URL and the topics, registered per tenant.

Verify a delivery

The signature scheme, what to do until the signing secret is available, what to return, and when it retries.

Delivery guarantees

At-least-once, best-effort ordering, the retry window, and idempotent handlers.

The event stream is the platform telling you what happened, the moment it happens. For analytics it is the freshness feed: the thing that makes a counter move and an alert fire without polling.

These pages are the reporting-specific angle on a platform service documented in full elsewhere. Read Events for the envelope and the topic taxonomy, and Webhooks for delivery, retries and signature verification. Nothing here restates them — where a detail is the platform contract, it is a link.

The pages

  • The event stream — what you get, in reporting terms, and the two things a stream cannot do for you.
  • Event types for reporting — which topics are worth subscribing to when the goal is numbers, and what to write down when one arrives.
  • Register an endpoint — a Cockpit action, not a partner API call.
  • Verify a delivery — the one thing your receiver must do before it trusts a body.
  • Delivery guarantees — at-least-once and best-effort ordering, and what they mean for a figure somebody will argue about.

The one-paragraph version

Register an HTTPS endpoint in Cockpit for the topics you need. Each delivery is a JSON POST of the event's data, with the event id and topic in headers. Dedupe on the X-Revenexx-Event-Id header, return 2xx fast, and do the work out of band. Until Cockpit shows the signing secret, treat a delivery as a notification and re-read the entity through the API. Assume every event may arrive twice and out of order, and treat the stream as a change feed into a store you own — not as your store.

Where to go next