Observe
Observe is where operators watch what happened and how external systems stay in sync: signals, outcomes, and webhooks (plus any health surfaces your operator exposes outside this manual).
Desk entry points
| Area | Typical route | Purpose |
|---|---|---|
| Observe hub | /dxp/observe | Navigation into Observe tools. |
| Signals | /dxp/observe/signals | Traffic, errors, or product signals (as configured). |
| Outcomes | /dxp/observe/outcomes | Conversion or funnel outcomes tied to Engage / commerce. |
| Webhooks | /dxp/observe/webhooks | Outbound subscriptions + delivery outbox, Inbound partner endpoints + inbox, and Agent gates (supply-side POST tab). |
| Purchase requests | /dxp/observe/purchase-requests | Staff PO queue; approve to send agent.replenish.purchase_order outbound. |
How Observe differs from Engage
- Engage answers “who is in the journey and what is the next human action?”
- Observe answers “did the systems agree, did the numbers move, did anything fail silently?”
In this module
- Signals and outcomes — reading dashboards without drowning in noise.
- Webhooks and events — how to create, test, and debug outbound + inbound webhooks in the desk.
- Checkout inventory holds — commerce webhook payloads (
reserved, order paid/cancelled) and checkout holds (Create module). - Agent replenishment — agent gates, forecasts, purchase requests, and wholesaler outbound events.
Related
- Engage
- Troubleshooting — when Observe shows errors tied to desk or edge availability.