Know what your email did this morning, without asking anyone for a report.
Open the email view and read your email platform's own numbers: every campaign with its sends, opens, clicks and unsubscribes, and the lifecycle flows running for your business. Nothing on it is typed in, and nothing on it sends.
What do I see when I open the email view?
A stat row across the top, then a card of your lifecycle flows. Find the view in the sidebar under Channels, beside SEO, Google Ads, Content and Outbound. The stat row carries the account totals: contacts on the account, sends across the recent campaigns read, and the average open and click rate across those sends. Click a tile and it opens to its current value, the window it covers and its source. Under the stat row, the flows card lists every flow with its performance. Click a flow and it opens with its performance, its trigger and its status.
Read the header before the numbers. It carries the time stamp of the data on the screen, and the stamp says whether the page pulled live when you opened it or is showing the last saved snapshot. Two buttons sit in the top bar. Refresh pulls fresh data from your connected accounts right now. Export downloads the view as a CSV with a Flow column and a Performance column, one line per flow, so a flow's numbers can go into a spreadsheet without retyping.
Check all of this in the demo before you buy. demo.trulata.com has no form, runs the same engine code every client runs, and shows a fictional company with illustrative numbers. Open the email view there, click a stat tile, click a flow, and press Export. What you see in the demo is the screen your account gets.
Are my lifecycle flows actually running?
Yes, and the view is where you see it. A lifecycle flow is a sequence that sends itself when something happens: a new lead gets a welcome, a quote that went quiet gets a follow-up, a finished job gets a review request. The card is titled "Lifecycle flows, always running". It lists each flow with its performance and its status, and a short note under the card says how the whole thing runs. Most owners have never had a place to check that a flow is live. This is that place.
Your flows are built with you in weeks three and four of setup, alongside your content cadence, ads reports and goals, and they send from your own email platform. Setup takes two to four weeks and is not billed.
Three things run whether anyone is at a desk. Your flows send on their triggers from your own platform. The dashboard pulls your email statistics when someone opens it. And at 12:01am Central a fallback snapshot is baked for every client, so the page always has last night's numbers to fall back on. Nothing else about your email runs on a clock.
Changing a flow stays with a person. Send the request from any tab of the dashboard or email [email protected]; either way it reaches your team and lands in the Support view with a ticket number. Nothing on the screen writes to your email platform, so a flow is never paused, edited or started by a click.
Are these this morning's numbers?
Yes. Email statistics are read from your email platform's API, and they are among the sources that move on every load, with your CRM, Stripe, your booking platform and website leads. Here is what happens when you open the page. It loads last night's snapshot first, so you never look at a blank screen. It fetches the cached payload at once. If that payload is older than five minutes, a pull runs in the background and the numbers update.
Take a campaign you send at 9am. Open the dashboard at noon and the campaign is in the read, newest first, with how many contacts it went to, unique opens, unique clicks and unsubscribes. Open rate is unique opens divided by sends. Click rate is unique clicks divided by sends. Both come from the counts behind the tile, never from a pasted report. Press Refresh at four and the pull takes between 2 seconds and a little over 3 minutes; the page reloads when the stamp moves and never shows an error.
Two limits, stated plainly. A metric your platform does not report is left out of the view rather than shown as zero. And every night at 12:01am Central a fallback snapshot is baked for every client; a failed pull or a failed syntax check leaves the previous page up, so the worst case is last night's numbers, never an empty page. Other sources on the dashboard have lower ceilings set by their owners: Google Ads and GA4 run hours behind during the day, and Search Console runs 2 to 3 days behind. Email statistics are live.
Which platform does it read, and do I have to move my list?
ActiveCampaign, read live where you send through it, and no, your list stays where it is. The connection is an API key and your account URL, both issued from your own ActiveCampaign account under Settings, then Developer. Our team makes the connection from the inside during setup with access you grant. There is no wizard, no sign-in button and no client-side OAuth, and we never hold your password.
The key is tested against your account before it is stored, and the test answers with the number of contacts on the account, so a wrong key surfaces at setup and not later as an empty tile. The key is then encrypted at rest. The only part kept in the clear is a last-four hint, so we can confirm which key is on file without reading it. The plaintext is decrypted server-side for the pull and is never returned to a browser. Ask, and the key is deleted from our store.
Send through something else? Ask during setup, or press Request an integration on the Integrations view of a live dashboard; the ask goes straight to your team. What is not connected on any account, and never read: your inbox, your calendar and your customers' card data.
Can a click on the screen email my customers?
No. The write paths from the screen are few, and the list is complete: ask a question where that view is offered, set a lead outcome, request a website change, and request a content, keyword, category or targeting change. The requests go to your team and are logged. None of them writes to your email platform, your ads account, your CRM, your site or your Business Profile.
Your flows do send, from your own platform, on their triggers, under rules built with you. Prospecting to new businesses is a different engine on its own page: prospect emails leave from a review-first queue; a person releases them, or the queue releases on the schedule set for the engagement, and every send is logged. Not-interested replies and bounced addresses are suppressed, and named accounts you specifically want are always reviewed by a person before anything leaves.
Your inbox is not connected and is never read. The view knows what your email platform and your forms know, and it says so.
How does email connect to my leads?
At the moment a lead arrives. When someone submits a form on your site, the form handler appends the lead to your lead sheet server-side and emails your team, so the first email a lead triggers is the one that tells you they exist. That email carries the lead's own address as its Reply-To, so your first reply goes straight to the person. The Leads view reads the sheet newest first: received time, name, phone, email, what they asked for, their message and the page they were on.
From there your CRM and your flows take over. A welcome or follow-up flow sends from your email platform on the rules built in setup, and the email view is where you see that it ran and how it performed. Leads are counted from your own forms, never from an ad platform's report, so the lead count and the flow performance start from the same record.
What the email view reads.
| What | Where it comes from | How fresh |
|---|---|---|
| Campaign statistics | Your email platform's API: sends, unique opens, unique clicks, unsubscribes, newest first | Live |
| Open rate, click rate | Computed from sends and unique opens or clicks | Live |
| Account totals | Contacts on the account; sends and average rates across the recent campaigns read | Live |
| Lifecycle flows | Your email platform, listed with performance and status | Live |
| Platform | ActiveCampaign today; others on request during setup | Per account |
| Your inbox, calendar, card data | Not connected | Never |
| Writes to your email platform from the screen | None | Not applicable |
The email view reads your email platform through its API, never moves your list, never sends from the screen and never reads your inbox.
Questions, answered.
Which email platforms are supported?
ActiveCampaign today, read live where you send through it. Other platforms are connected on request during setup, and your list stays where it is either way.
Are open and click rates live?
Yes. They are read from your platform's API when the page is opened, a pull runs in the background when the cached payload is older than five minutes, and Refresh pulls on demand.
Does the Command Center send email to my customers?
No. Your flows send from your own platform under rules built with you. Nothing goes out because of a click on the screen.
Do you read my inbox?
No. It is not connected on any account, and neither is your calendar.
Can I pause a flow from the screen?
Not directly. Request it from any tab and your team pauses it; the request lands with a ticket number. Nothing on the screen writes to your email platform.
What is a lifecycle flow?
A sequence that sends itself when something happens, such as a welcome after a new lead or a review request after a finished job.
How long does Refresh take?
Between 2 seconds and a little over 3 minutes, depending on the account. The page reloads when the time stamp moves and never shows an error.
See it running
before you decide.
The demo is the real product on a fictional company, with no form in front of it. Pricing is three published tiers. Setup on your own accounts takes two to four weeks.
Open the live demo See pricing
New here? See what the Command Center is. Prefer to write? Send us the one thing you want to know.
- Refreshed when you open itLive data on page load, never a monthly PDF
- Counted from your own formsLeads recorded server-side, compared daily with Ads and GA4
- Four answer engines, measuredChatGPT, Gemini, Claude and Grok, with a published denominator
- A review-first queue on every sendEvery draft waits in a review-first queue and every send is logged.