Collect commerce events once.
Serve the complete journey.
Define website, web-app, native-app and transaction events once. Validate them at the source and deliver only permitted context to analytics, service and operational systems.
The complete capability
Collection is part of the governed operation.
Collection starts where the interaction happens. Each accepted event uses the same business definition for quality, context, purpose and delivery.
Websites and web applications
Define product views, searches, filter choices, cart changes, checkout steps and service interactions as business events. Collection JavaScript can be generated from the DimML agreement to check the application data layer before transmitting accepted events.
Native mobile apps
Instrument relevant screen views, product interactions, cart changes and service requests against the agreed event contract. Connect the app to the stream API and validate platform permissions, authentication and delivery behaviour for the selected implementation.
Backend and transaction systems
Combine permitted interaction events with confirmed orders, payments, returns and delivery updates. A checkout click describes an interaction; confirmation from the transaction system establishes the business outcome.
One controlled flow
The same agreement governs the source through the confirmed result.
Define the purpose, permitted fields, required context, quality conditions and collection permissions before an event leaves its source. Apply the approved processing and destination rules in the stream. Link sessions or channels only when the identity and purpose conditions allow it. For mobile delivery, explicitly test offline queues, duplicates, late events and a permission change before queued data is sent.
web, app or transaction data + current context → accepted business event → permitted service output → delivery result → updated context
- Validate the source contract and required context.
- Apply the active purpose, quality and business rules.
- Transform and deliver the permitted backend input.
- Use the confirmed result to update context and evidence.
Example in context
One accepted event can serve several responsibilities.
A shopper adds an item in a native app and later completes a purchase on the website. Where the approved identity and purpose rules allow the events to be linked, the confirmed order updates the shared context. Analytics can receive the permitted conversion event, customer service can see the relevant order status and a configured cart reminder can be suppressed. Each destination receives the fields allowed for its task.
Start with one source, one rule set and one accepted destination.
Validate normal events, missing context, changed permissions, duplicates and an unavailable endpoint before extending the same operation.