Skip to main content

Dashboard

The Dashboard is the screen you land on after signing in. It is built to answer one question first - "what needs me today?" - and then to show how things are going. Detailed reporting lives in Analytics; the Dashboard is for triage and quick launch.

Everything on it reflects your current workspace and its real data, so a new or quiet workspace shows honest empty states rather than sample numbers.

Needs your attention​

A banner at the top surfaces issues worth acting on now, worst first. It is assembled from live signals across the product:

  • Delivery problems - for example, messages on one channel going out but almost none confirming delivery in the last 24 hours. Each channel (email, SMS, push, WhatsApp, Viber) is checked on its own, and the alert names the channel.
  • Blocklisted sending identity - a sending domain or IP found on a blocklist, which hurts deliverability until it is delisted.
  • Wallet certificate expiry - an Apple Wallet signing certificate expiring within 30 days (passes stop updating once it expires).
  • Monitoring alerts - any active integration-health alerts already raised for the workspace.

Each row has a direct action button that takes you to the right place to fix it, and a dismiss control. When there is nothing to act on, the banner collapses to a single line: "Nothing needs your attention".

Ideas​

Above the attention banner, an Ideas strip suggests one thing to try from your own numbers. It follows three rules: it speaks only when a report can back the idea (otherwise the strip does not appear), it shows one idea per source, and it stays inline - never a pop-up. Each card names its evidence, has one action, and a Discuss link that opens the AI Assistant with the question already typed (nothing is sent until you press Enter). Not now hides a card for a week on this browser.

The sources, in order:

  • An experiment - the widest measured gap in the content performance report over the last 90 days of email, with the recipients per arm needed to tell the values apart. The action starts a campaign, where the compose step offers the same test. See examples shows what each of the two values means and up to three of your own emails that carry it.
  • Held messages - the engagement gate against its always-send holdout over the last 30 days. It appears only when the gate met its criteria (no conversion loss, unsubscribes within tolerance) or clearly lost conversions.
  • Collisions - the share of people who received two of your sends on the same day, judged by the workspace's own collision threshold.
  • A journey step - the message step in a live journey that could not send to the largest share of the people reaching it (consent, suppression, quiet hours, frequency cap), with the main reason.
  • Regulars went quiet - regular customers (3 or more orders, a rhythm of their own) whose purchase-overdue flag turned on this week - the gap since their last order passed 1.5 times their usual gap within the last seven days - with the weekly order value their rhythm was worth, in your reporting currency. It appears when they number at least 25, or 2% of your active regulars, whichever is larger; both knobs are yours under Settings → Monitoring → Alerts, next to the collision alert. If a live journey (or an active or scheduled campaign) already reaches the segment on the purchase-overdue flag, the card names it and opens it. Otherwise Start win-back drafts a journey for you - a daily sweep of the segment "Regulars who went quiet" (created if you have none with exactly that filter), a wait until each person's usual order time, and an empty message step for you to write, leaving on Order Completed - and never activates it.

Every source also checks whether you already handle the thing before suggesting it: an experiment on a content field you are already testing in a campaign or a journey Experiment node says so and links there instead; a journey step is not suggested when a branch already follows it or a newer draft version already changes it (and a paused journey is never read); the held-messages and collisions cards report what already ran, so they have no such check.

Key metrics​

Four cards, each showing a value for the last 30 days, a change versus the previous 30 days, and a sparkline where data is available:

  • Active users - people who did something in the workspace in the last 30 days: a session, a page view, a custom event. Being sent a message does not make someone active, and bots and deleted contacts are excluded. The change is versus the previous 30 days.
  • Messages sent - messages sent across email, SMS, push, WhatsApp and Viber. In-app impressions are displays rather than sends, so they appear under In-app in Message performance, not here.
  • Click rate - people who clicked divided by messages delivered (push by messages sent, in-app by messages displayed), over the whole 30 days - the same rate as on the campaign page, see How open and click rates are calculated. A person counts once per message however often they click it (but twice if they click two different messages), and bot and scanner clicks are left out.
  • Store revenue or Delivery rate - if a store is connected, the fourth card shows store revenue over the window: every order the store recorded, not only orders attributed to a campaign. If no store is connected, it shows the delivery rate instead - messages confirmed delivered divided by messages sent, over message channels only.

The two windows are the last 30 days ending today and the 30 days before them, in the workspace timezone, with no day counted in both. The change figure is a relative change versus the previous 30 days. An up arrow is always green and a down arrow always red, so the direction matches the sign.

Users over time​

A chart of Active users and New users across a range you choose - 7, 14, 30, or 90 days. Active means the person did something that day; being sent a message does not count. Days are bucketed in the workspace timezone. The range control changes both the points and the date labels, and hovering shows the exact values for a day.

Message performance​

A funnel of your sends on a shared denominator, so each step is comparable. The bar at the top shows each channel's share of messages sent and doubles as a filter - click a channel (or pick one from the menu) to see just that channel's funnel; click it again to return to all channels.

Steps differ per channel, because channels report differently:

  • Email, push, WhatsApp, Viber - Sent, Delivered, Opened, Clicked.
  • SMS - Sent, Delivered, Clicked. Carriers report delivery but not opens, so there is no open step to misread.
  • In-app - Displayed, Seen, Clicked, because in-app messages are displayed rather than sent.

Opened and Clicked count messages, the same way as the Click rate card: a person counts once per message however often they open or click it (twice if they open two different messages), and bot and link-scanner activity is left out. A click on an email counts as opened - it proves the email was opened even when images were off or every open was a mail client's automatic fetch. Clicked is therefore a share of delivered messages, not a count of clicks that could pass 100% of delivered.

Scheduled & running​

What is going out, so nothing sends unnoticed. Each row is a scheduled or currently live campaign, with its channel and either a Live marker or its send time. A footer shows how many drafts are not scheduled yet, with a shortcut to review them. Live campaigns come first, then scheduled ones by send time, earliest first, read across every campaign in the workspace. The header's "N campaigns send today" counts every campaign scheduled for today in the workspace timezone.

Quick actions​

Four shortcuts to start work: New campaign, New journey, New segment, and Import audience.

Top campaigns​

Your campaigns ranked by a metric you choose - Click rate (the default) or Conversions. Conversions come from each campaign's own conversion goal - the same count as on the campaign page; a campaign with no goal shows No goal set rather than 0. Archived campaigns are left out. A campaign delivered to fewer than 100 people is listed after the ranked ones, without a rank, because one click on one send would otherwise read 100% and come first. Changing the metric re-sorts the list and updates the caption. Each row shows a rank, the campaign name, a sent-volume bar, and the ranking metric alongside a second stat.

Journeys​

Journeys run continuously, so this panel shows their live state rather than one-off sends. The header reads how many journeys are live and how many users are in flight across them. Each row shows the journey name, its step count and users in flight, completions in the last 7 days, and its conversion rate.

If a journey is broken - for example, a message step with no sender identity configured - it is flagged inline in red with a Fix button that opens the journey editor. This surfaces a silent failure that would otherwise be invisible.

Want the underlying numbers and trends? See the Analytics Overview. For revenue and store data, see the E-Commerce Overview.