Skip to Content
OperationsDiagnostics

Diagnostics

Investigate from the outer configuration boundary toward the device. Avoid jumping directly from a low open rate to a provider conclusion.

Engage environment diagnostics with provider readiness, workers, integrations, audience data, quotas, and actionable findings
Environment diagnostics starts with configuration and worker readiness before drilling into an individual delivery or installation.

Installation checklist

  1. Correct environment and app key.
  2. SDK start succeeded with expected version/endpoint.
  3. Installation ID appears under the expected app.
  4. Privacy and runtime features permit the operation.
  5. Pending SDK operations converge.
  6. Profile binding and generation are expected.
  7. Events/attributes/subscriptions appear at the right scope.

Push trace

Collect broadcast/request ID, delivery ID, environment/app, installation ID, provider, attempt count, provider code, token invalidation state, timestamps, TTL, priority, and collapse key.

Content trace

For in-app, record experience ID, published version, app, profile/installation, sync version, audience result, trigger event/screen, schedule, frequency counters, priority/conflict result, locale/variant, placement, and display decision.

For Message Center, record entry ID, template/revision, summary/detail rendering resolution, locale, cache state, read mutation, and action result.

Automation trace

Use run ID and step executions. Check entry trigger, audience/re-entry result, published version, current step, available/claimed times, retries, quiet hours, target app intersection, and failure code.

Health and quotas

Operations diagnostics report provider readiness, active access keys, worker health, webhook health, API usage, audience/event freshness, quota pressure, retention, and billing state. A warning may indicate missing configuration rather than an outage.

Engage environment usage and quota dashboard with API, events, profiles, messages, automations, media, and warning thresholds
Usage and quota context helps distinguish capacity pressure from a provider or SDK failure.

Safe support bundle

Include:

  • environment/app labels and non-secret IDs;
  • app, SDK, OS, and device versions;
  • installation ID;
  • message/request/run IDs;
  • UTC timestamps and timezone;
  • redacted SDK/server logs and provider error codes;
  • exact reproduction state (foreground/background/terminated).

Exclude app/access keys in full, installation credentials, push tokens, provider credentials, webhook secrets, binding codes, and personal payload values.

Workspace governanceGlossary