Platform Event Bus — Integration

Overview

Publish content, campaign, schedule, registration, attendance, claim, audience, and analytics events so other apps can react without tight coupling.

Capabilities

• Publish namespaced EngagementHub lifecycle events

• Subscribe selectively to project, delivery, and external business outcomes

• Use correlation IDs, idempotency keys, workspace IDs, entity IDs, and contract versions

• Avoid sending full article bodies or unnecessary personal data in event payloads

• Support retries, dead-letter handling, audit visibility, and consumer independence

1. 1

   Step 1

   Declare EngagementHub publish and subscribe topics in the app manifest.

   Back to top
2. 2

   Step 2

   Define payload contracts with minimal identifiers, status, timestamps, and safe display metadata.

   Back to top
3. 3

   Step 3

   Register handlers for only the events EngagementHub truly needs.

   Back to top
4. 4

   Step 4

   Add idempotency and replay protection to each consumer.

   Back to top
5. 5

   Step 5

   Run contract tests for publish, retry, duplicate, and out-of-order cases.

   Back to top
6. 6

   Step 6

   Monitor event logs and dead-letter records from workspace operations.

   Back to top

Limitations

• The event bus should not be used to transfer large bodies, binary files, or full audience member lists.

• Consumers must retrieve authoritative details from the owning app when needed.

• Event ordering may not be guaranteed across unrelated entity streams.

FAQs

Pricing