Event Manager
Event Manager is the Salesforce Setup page that consolidates configuration for all event-driven integration features the platform supports: Platform Events, Change Data Capture, Flow Orchestration Events, and the supporting infrastructure for subscriptions, replay, and channel management.
Definition
Event Manager is the Salesforce Setup page that consolidates configuration for all event-driven integration features the platform supports: Platform Events, Change Data Capture, Flow Orchestration Events, and the supporting infrastructure for subscriptions, replay, and channel management. The page is the operational surface for event-driven architecture on Salesforce, giving admins and integration engineers a single place to monitor what events flow through the org, who subscribes to them, and what happens when a subscription falls behind.
Event-driven architecture has grown significantly in Salesforce deployments over the past five years, driven by the need for real-time integration between Salesforce and external systems, between Salesforce and other clouds (Marketing Cloud, Data Cloud, MuleSoft), and between different layers of customization within Salesforce itself (Flow listening for record changes, Apex publishing custom events for downstream processing). Event Manager is the page that brings this varied landscape under a single management view.
The event types and configuration Event Manager surfaces
Platform Events: custom event definitions
Platform Events are custom event types defined by the admin (similar to how custom objects are defined). Each Platform Event has its own fields, and an event is fired by inserting a record of that event type via Apex, Flow, or the REST API. Subscribers (Apex triggers, Flows, external systems via the streaming API) receive the event in real time. Event Manager lists every Platform Event defined in the org with its fields, retention policy (typically 72 hours), and current publish and subscribe volumes. The page also exposes the throughput limits and shows current consumption against those limits.
Change Data Capture: automatic events on record changes
Change Data Capture (CDC) automatically generates events whenever specified standard or custom objects have records created, updated, deleted, or undeleted. Subscribers receive a snapshot of what changed, with old and new values. CDC is the right tool for replicating Salesforce data to an external system in real time without writing custom Apex publishers. Event Manager shows which objects have CDC enabled, the current publish volume, and the subscription state of any internal or external listeners. CDC has its own throughput limits separate from Platform Events; the page surfaces both.
Subscriptions and replay
Each event channel (Platform Event or CDC channel) can have multiple subscribers: Apex triggers, Flow listeners, external systems consuming via the streaming API. Event Manager lists every subscriber and the current replay state. A subscriber that falls behind sees the events accumulate up to the retention limit, then drop. Replay IDs let a subscriber catch up after a brief downtime by requesting events from a specific point. The page exposes the current replay ID for each subscriber so admins can detect lagging consumers and intervene before events are lost.
Limits and throughput
Both Platform Events and Change Data Capture have throughput limits scaled to the org's edition and any add-on event allocation. Hourly publish limits, daily publish limits, and per-subscriber delivery limits all apply. Event Manager shows current consumption against each limit as a percentage with a trend over time. Exceeding a limit causes events to be rejected (publish-side) or dropped (subscribe-side), which produces silent integration failures. The platform sends in-app notifications when consumption crosses certain thresholds, but proactive monitoring through the Event Manager dashboard is the right operating practice.
Flow Orchestration events
Flow Orchestration is a Salesforce feature for building multi-stage workflows that span multiple users and run over extended time periods (days or weeks). Each stage in an orchestration can produce events that other stages subscribe to. Event Manager surfaces these orchestration events alongside Platform Events and CDC, giving admins a complete view of every event channel in the org. The orchestration events have their own retention and replay characteristics that differ slightly from standard Platform Events, and Event Manager documents the specifics for the org's current configuration.
Channel management and grouping
Beyond individual events, Event Manager exposes Channel concepts: a Channel can group multiple related events into a single subscription target for efficiency. An external system that wants to consume Account changes plus Opportunity changes can subscribe to a single Channel rather than two separate event subscriptions. The Channel configuration is part of the Event Manager surface, and getting the Channel design right matters for integration performance and code complexity on the consumer side.
Monitoring and alerting on event health
Event Manager is not a real-time dashboard, but it produces enough data for monitoring tools to alert on event health. Common metrics: publish rate over time per channel, subscription lag per consumer, error rate on event delivery, and consumption against limits. Mature event-driven deployments build observability that pulls from Event Manager's reporting surfaces and visualizes the metrics in Splunk, Datadog, or CRM Analytics. Without observability, problems with event delivery are typically discovered hours or days after they start, by which point recovering missed events may be impossible.
The shift toward event-driven architecture
Salesforce has been steadily nudging customers toward event-driven patterns over the past few releases. The Pub/Sub API (gRPC-based, higher throughput than the legacy streaming API), increased Platform Event allocations in newer editions, broader CDC object coverage, and Flow Orchestration are all parts of this push. The reason is practical: event-driven integration scales better than the alternative of polling REST endpoints from external systems, and it produces lower latency for real-time use cases like inventory updates, fraud detection, and customer journey orchestration. Customers who invest in event-driven patterns early tend to have cleaner integration architectures three years later than customers who built on polling. Event Manager is the page where that investment becomes visible. A mature event-driven deployment shows up as several active channels, healthy subscriber lag metrics, and clear ownership documentation for each channel.
Common patterns and anti-patterns
Three patterns recur in well-run event-driven deployments. Event sourcing where every state change is captured as an event, used for audit and rebuilding read models. Saga orchestration where long-running multi-step workflows coordinate through events between systems. CQRS (Command Query Responsibility Segregation) where write operations produce events that downstream read models consume. Three anti-patterns also recur. The chatty channel where one Platform Event covers many unrelated business events, making subscribers harder to write. The forgotten subscriber where an Apex trigger or Flow remains active long after the original use case retired, silently consuming throughput. The unmonitored consumer where no one watches for lag until events start dropping. Avoiding the anti-patterns and adopting the patterns is what separates an event-driven architecture that ages well from one that becomes a maintenance burden.
Set up and monitor events through Event Manager
Configuring event-driven integration on Salesforce spans Platform Event definition, CDC enablement, subscriber registration, and ongoing monitoring. The walkthrough below covers the standard sequence for a typical real-time replication use case where Salesforce data needs to flow to an external system in near real time.
- Define the event type or enable CDC
Decide whether the use case is better served by a Platform Event (custom event shape, fired by Apex or Flow) or by Change Data Capture (automatic events on standard or custom object changes). For replication, CDC is usually right; for custom business signals (a new milestone reached), Platform Events are right. Configure the chosen approach: create the Platform Event definition with its fields, or enable CDC on the target object from the Change Data Capture page in Setup.
- Configure subscribers
Identify the subscribers that need to consume the events. For internal subscribers, build the Apex trigger or Flow that processes each event. For external subscribers, configure the external system to subscribe via the streaming API, CometD, or the Pub/Sub gRPC API. Each subscriber needs a clear contract for what it does with each event and how it handles retries on failure. Document the subscribers in the org's integration runbook before going live.
- Validate end-to-end in a sandbox
In a sandbox, fire a sample event (publish a Platform Event record or update a CDC-enabled object). Verify the subscriber receives it, processes it correctly, and any downstream changes happen as expected. Test failure modes: subscriber temporarily offline, subscriber slow to process. Confirm the replay-based catch-up works correctly. Iterate until the integration handles every scenario from the test plan.
- Promote to production and monitor through Event Manager
Deploy the Platform Event definition or CDC configuration to production. Activate the subscribers. Open Event Manager and monitor for the first hour to confirm events are flowing and subscribers are keeping up. Set up alerts (via the platform's notification settings or a custom monitoring tool) for any subscriber that falls behind. Schedule a weekly review of event throughput and subscription lag for the first month, then settle into the steady-state cadence.
- Event retention is 72 hours for most event types. A subscriber that is down for longer loses any events it missed.
- Platform Event publish limits are hourly and daily. Exceeding them causes events to be rejected at publish time without an error to the calling code.
- CDC events represent changes, not full record state. Subscribers that need a full record snapshot must query the record separately after receiving the change event.
- Subscriber lag is silent. Without monitoring, a subscriber that falls behind goes unnoticed until events start dropping past the retention window.
- Sandbox event throughput limits are lower than production. Sandbox tests for high-volume scenarios need careful scaling considerations.
Trust & references
Straight from the source - Salesforce's reference material on Event Manager.
- Platform Events Developer GuideSalesforce Developer Docs
- Change Data Capture Developer GuideSalesforce Developer Docs
Hands-on resources to go deeper on Event Manager.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What does Event Manager represent in the Salesforce Platform?
Q2. Who can benefit from understanding Event Manager?
Q3. How does Salesforce's multi-tenant model affect Event Manager?
Discussion
Loading discussion…