Signals and outcomes
Signals (/dxp/observe/signals)
Signals are higher-frequency indicators: HTTP errors, integration failures, stock anomalies, or custom counters your operator wired in. Use Signals to:
- Spot spikes after a deploy or campaign launch.
- Correlate edge issues with platform incidents (timestamps matter—use a single timezone convention across the team).
Outcomes (/dxp/observe/outcomes)
Outcomes summarise business results: orders completed, trials started, forms submitted, journey completions, etc. Use Outcomes to:
- Validate a campaign against baseline.
- Compare Spaces or regions when your tenant is multi-site.
Content tags (Library and publish)
When creators assign content tags on pages or Library assets in a Space, outbound events such as content.page_published may include a content_tags array (slug, label, kind). Downstream warehouses and custom Observe apps can facet on those dimensions even before the desk adds tag filters to Signals charts.
Tag the same way you organise Library — content tags for public/analytic labels, internal tags for ops-only workflow. Tags are Space-scoped unless your core uses consolidated sharing.
Good habits
- Triage window — pick a rolling window (24h / 7d) and stick to it when comparing before/after.
- Segment — always know whether you are looking at one Space or the whole workspace.
- Escalation — when a chart looks wrong, capture UTC time, Space host, and metric name before paging engineering.