The Customer.io Workspace Performance Dashboard Is The First Place You Should Look Every Monday
On 13 January 2012, the cruise liner Costa Concordia ran aground off the island of Giglio. The bridge had route-deviation alarms. It had a coastal chart that showed the Le Scole rocks. Those alarms had been switched off. The right coastal chart was not loaded—the bridge was working from a 1:100,000 open-sea chart instead of the 1:20,000 chart that marked the rocks. The captain, by his own admission, was "navigating by sight". 32 people died.
Instruments only help if someone looks at them. The cruise industry learned that the hard way in 2012. Most Customer.io workspaces are still relearning it.
On 8 April 2026, Customer.io shipped the Workspace Performance dashboard as part of its biggest single product release. Six weeks on, almost no marketing team has a habit around it. The dashboard surfaces things that used to require a support ticket to confirm. Whether your sends are going out immediately. How campaign processing is performing. Whether a specific subsystem is degrading independently from the rest. For lifecycle teams running behaviour-triggered campaigns, a stalled queue is a silent revenue leak. This post is the five-minute Monday-morning scan, the four signals to read, and what to do when something goes red.
Where the dashboard lives, and why most teams have never opened it
The Workspace Performance dashboard sits in Customer.io's redesigned navigation under Manage → Workspace performance. The direct URL is fly.customer.io/workspaces/last/health. The canonical documentation page is docs.customer.io/journeys/health/—worth noting because the more obvious-looking path docs.customer.io/messaging/dashboard/ redirects to the new Home dashboard, which is something different.
Most teams missed it because it launched alongside seven other big features in the same release: the AI Agent, LLM Actions, Goals, Universal Search, the UI refresh, WhatsApp, and LINE. The dashboard didn't get a launch fanfare of its own. Customer.io's launch announcement captures it neatly: "It's the kind of operational clarity that used to require a support ticket to answer. Now it's a URL away."
The URL is the habit. Bookmark it.
Workspace Performance vs Home vs the status page: three things people are confusing
Three surfaces shipped on 8 April 2026 and people are already confusing them.
The Home dashboard is the redesigned front page when you open the workspace. It's a navigation surface, not a monitoring one.
Workspace Performance is the operational view. It tells you whether your workspace is processing data and sending messages on time. That's what this post is about.
Then there's the Customer.io status page at status.customerio.com, which is platform-wide. It shows component-level uptime across every customer of Customer.io. If status.customerio.com is amber and your dashboard is red, that's a platform incident affecting you. If status.customerio.com is green but your dashboard is red, the problem is local to your workspace.
Different questions, different surfaces. Use all three. Don't conflate them.
The four signals that actually matter
Forget the panels for a second. Four things matter on this dashboard.
Signal 1: Processing delay (ingress)
The Overview tab shows processing delay across the last 24 hours, split into ingress (data coming in) and egress (messages going out). Ingress is the more interesting one for most teams.
Ingress lag covers everything coming from your Track API, integrations and reverse-ETL feeds. When an event takes longer than usual to land, every behaviour-triggered journey downstream fires late. A 30-second ingress delay is a non-event. A 5-minute delay is your trial-onboarding email arriving after the user has already bounced.
Signal 2: Outgoing throughput (egress)
The Messaging tab shows outgoing throughput: the current rate of messages leaving your workspace. The absolute number doesn't matter much. Patterns do. If throughput drops to zero on a weekday when your scheduled broadcasts should be firing, something is wrong. Hover on Sent today to compare against yesterday. A sudden 80% drop while volume should be steady is a flag.
Signal 3: Per-service health (with the thresholds you actually need)
The Services tab is the most useful and the least flashy. It shows per-subsystem health with explicit numeric thresholds, taken directly from Customer.io's documentation:
- Normal: no backlog, delay under 10 seconds
- Slight delay: 10 to 60 seconds
- Delayed: 1 to 5 minutes
- Major delay: over 5 minutes
These thresholds let you stop arguing about whether something is "a bit slow". Under 10 seconds is fine. Over 5 minutes is an incident. Anything in between is a yellow flag worth watching.
Different services can degrade independently. Segment updates can sit in Major delay while campaign processing is Normal, and the reverse happens too. Read the Services tab. Don't rely on the overall workspace status badge to surface a problem that's local to one subsystem.
Signal 4: Active issues and alerts
Two surfaces tell you something is already broken. Active Issues on Overview lists problems affecting the workspace. Alerts on Messaging warns when specific workflows or channels are degraded.
If you're under time pressure and can only check one thing on the dashboard, check these two.
What "healthy" actually looks like
The workspace gets an overall Health status: Healthy, Busy, or Slow performance. Healthy is green and means what it says. Busy is yellow and means you're processing more events than normal—delays are possible but the workspace is keeping up. Slow performance is red and means at least one service is degraded with errors.
One pattern worth tuning out: a single subsystem sitting at Slight delay for a few minutes is not an incident. If you've got 20 services, the chance one of them blips in any given window is high. Look at duration and look at criticality. A 30-second Slight delay on a low-volume subsystem doesn't need a Slack message. A sustained Delayed on Campaign Processing does.
The Monday-morning five-minute scan
Bookmark fly.customer.io/workspaces/last/health. Open it every Monday morning. The scan goes in this order:
- Overall Health status: green, yellow, or red? If red, skip to the triage section below.
- Overview → Active Issues: anything listed? Read it. Click through.
- Services tab: anything not Normal? Note which subsystem, note the severity.
- Messaging → Alerts: any workflow flagged?
If everything is green and Active Issues is empty, you're done. Close the tab. Five minutes.
If something is yellow or red, you move to triage. That's the next section.
When something goes red: a three-action decision tree
You see red on the dashboard. Three possible actions, in priority order.
Action 1: check the status page. Open status.customerio.com in another tab. If there's a current incident covering Data Processing or Message Sending, your dashboard is reflecting a platform-wide issue. You can't fix it. Communicate to stakeholders, watch the status page for an ETA, log the impact, move on.
Action 2: check Suggested Optimizations. Customer.io's status page is green, but your workspace is red. Scroll to Suggested Optimizations on the Overview tab. The recommendations are AI Agent-generated—archive unused segments, pause campaigns with no recent sends, throttle incoming data. They're useful, but they're not magic. Treat them as starting points, not orders. There are reasons to read AI Agent guardrails before letting any AI suggestion modify your live workspace.
Action 3: raise a ticket. Status page green, Suggested Optimizations don't apply, and a service has been in Delayed or worse for more than 30 minutes. Raise a support ticket. Include a screenshot of the dashboard, the specific service that's degraded, the timestamp, and what you've already ruled out. Customer.io support can see things you can't from inside the workspace, and the dashboard data is what they'll ask for first anyway.
If the dashboard is normal but a single campaign is misbehaving, the dashboard is the wrong tool. Go to that campaign's diagnostics instead.
Make it a habit, but don't over-engineer it
The dashboard has no native alerting yet. There's no "ping me when this goes red" toggle, no SLO breach notifications, no per-channel SLA. As of May 2026, it's a passive surface. You have to look at it.
The fix isn't a custom Slack integration with five hand-tuned thresholds. The fix is a recurring Monday calendar block and the URL bookmarked. Five minutes a week. Operational habits that compound for Customer.io workspaces are quiet and small, much like the way the holdout checkbox replaces an entire attribution debate with a single setting. The point is the habit, not the toolchain. Don't build infrastructure before you've built the routine.
If you do want a lightweight signal, set a calendar reminder. That's it.
What the dashboard doesn't do (yet)
Be honest about what's missing. No anomaly detection. No threshold-based alerting. No SLO. No per-campaign processing breakdown beyond the channel-level rollups on the Messaging tab.
Worse: the dashboard catches operational degradation, not content degradation. If processing is Normal but your Liquid templates are silently rendering blank because a property has gone null, the dashboard will not warn you. It tells you whether messages went out. It does not tell you whether they were any good.
Likewise, automated changes made via Customer.io's MCP server won't appear on the dashboard as an event. The dashboard tells you the workspace is healthy. It does not tell you what AI just changed inside it.
The dashboard is a starting point, not a complete operational stack. Treat it that way.
Frequently asked questions
Q: Where is the Customer.io Workspace Performance dashboard?
In the redesigned navigation under Manage → Workspace performance, or directly at fly.customer.io/workspaces/last/health. The supporting documentation is at docs.customer.io/journeys/health/. The path docs.customer.io/messaging/dashboard/ is not it—that redirects to the new Home dashboard.
Q: When was the Customer.io Workspace Performance dashboard released?
On 8 April 2026, alongside the AI Agent, LLM Actions, Goals, Universal Search, WhatsApp, LINE, and the new Home dashboard.
Q: What are the Customer.io processing delay thresholds?
Per the official docs: Normal is under 10 seconds, Slight delay is 10 to 60 seconds, Delayed is 1 to 5 minutes, Major delay is over 5 minutes. These apply per service on the Services tab.
Q: Is the Workspace Performance dashboard the same as the Customer.io status page?
No. The dashboard is specific to your workspace and shows local processing, sending, and per-service health. The status page at status.customerio.com is platform-wide and shows the health of Customer.io's underlying services across every customer. Check both. If the status page is amber, the dashboard is reflecting a platform incident, not a workspace one.
Q: What's the difference between the Home dashboard and the Workspace Performance dashboard?
The Home dashboard is the redesigned front page when you open the workspace—a navigation and at-a-glance surface. The Workspace Performance dashboard is the operational monitoring view. Both shipped on 8 April 2026 but answer different questions.
Q: Can I get alerts when the Customer.io Workspace Performance dashboard goes red?
Not natively—not as of May 2026. There's no built-in threshold-based alerting and no SLO notifications. The pragmatic alternative is a weekly calendar block and the URL bookmarked, not a custom alerting pipeline.
Q: What does "send queue depth" mean in Customer.io?
It's the number of messages waiting to be sent. The dashboard surfaces this on the Messaging tab via Outgoing throughput (the current send rate) and processing delay (how long egress is taking). If throughput drops while delay rises, the queue is backing up.
Q: How do I know if my Customer.io campaigns are processing on time?
Open the Workspace Performance dashboard, check the Services tab for any subsystem related to campaign processing or segment updates, and confirm it's in the Normal band (under 10 seconds delay). The Messaging tab also shows per-channel state for Campaigns, API-triggered Broadcasts, and Push Notifications.
Q: Why is my Customer.io campaign showing "Pending" or "With errors"?
"Pending" means Customer.io is evaluating recipients and queuing messages—normal during a send. "With errors" means the workflow has hit problems and needs attention. The dashboard surfaces both states under the Messaging tab. "With errors" warrants opening the campaign diagnostics directly.
Q: Does the Workspace Performance dashboard show data per workspace or account-wide?
Per workspace. If your account contains multiple workspaces, each has its own dashboard.
Q: What should I do when the dashboard shows "Major delay"?
Three-step triage. Check the Customer.io status page first. If there's a platform incident, you can't fix it from inside the workspace. If the status page is green, check Suggested Optimizations for AI-surfaced recommendations. If neither resolves it and the service stays in Major delay for over 30 minutes, raise a support ticket with a screenshot, the affected service, and the timestamp.
Q: How often should I check the Customer.io Workspace Performance dashboard?
Once a week is the minimum that catches most issues before subscribers notice. A five-minute Monday scan covers normal operations. Add a second look any day you've shipped a new campaign, integration, or data source.
Q: Can I monitor Customer.io send queue depth from Slack?
Not natively. The dashboard has no Slack integration as of May 2026. You can build one with a scheduled task hitting the workspace, but it's a workaround. For most teams, the calendar reminder and the bookmarked URL get you most of the value.
Sources
- Workspace Performance dashboard documentation, Customer.io Docs
- Release notes: track the health of your workspace and troubleshoot issues, Customer.io, 8 April 2026
- Customer.io's biggest AI marketing release announcement, Customer.io, April 2026
- UI refresh: your new Home dashboard, Customer.io Release Notes, 8 April 2026
- Customer.io status page, Customer.io
