Connect your accounts once. Open one page and know what ran.
Our team links your accounts in the first week. After that the page pulls from them when you open it, the work runs on a schedule whether anyone is at a desk, and every request you make from the screen is logged with a ticket number.
Who connects my accounts, and what do you never hold?
Our team does the connecting. You add our Google account as a manager on your Analytics property, your Search Console site, your Ads account and your Business Profile listing, from your own console, the way you would add a bookkeeper to your bank. Each grant is a manager invitation you can revoke in that console whenever you choose. We never hold your passwords.
Your CRM, Stripe, your booking platform, your email campaign platform and your website forms are linked by our team from the inside, with access you grant during setup. There is no wizard, no sign-in button on our site and nothing to paste. Every connection is recorded in a per-client map, and that map, never the browser, decides which Analytics property, which Ads account and which Search Console site your page may read.
Some things stay out on purpose. Not connected on any instance: your email, your calendar and your customers' card data. Stripe is read only; nothing here creates a charge or a refund. A phone lead counts only when your CRM records it. Nothing on the screen writes to your Ads account, your CRM, your site or your Business Profile.
What do I see when I open it, and how fresh is it?
You see your numbers within the first second. The page renders last night's snapshot first, so there is never a blank screen. It then asks our service for the live payload, which is served from cache at once. If that cache is older than five minutes, your pull starts behind the request and the fresh numbers swap in when they land, with your place on the page kept. The swap waits while a dialog is open or you are typing.
The header says how old every number is. Next to the words Marketing Command Center, a stamp reads the time of the last pull. Hover it and it tells you whether the page was pulled live when you opened it or is showing the last saved snapshot because the live service could not be reached. Staleness is never invisible.
Press Refresh and a full pull of every connected source starts. A pull takes two seconds to a little over three minutes depending on how many sources you have, so the button returns at once and the page checks back until the stamp moves, then reloads. Every path through that button ends in a reloaded page. A slow pull, an unreachable service or a timeout all end the same way, with a stamp that says the age of what you are reading. It never shows an error.
What does the screen tell me without anyone writing a report?
The Overview is the report, assembled by the page rather than by a person. Headline metrics sit at the top; click one and it opens with its current value, its change and its window. Program goals sit under them, each with a progress bar and an on-target mark, so what we hold ourselves to sits beside what happened. Below that: the pipeline funnel stage by stage, revenue by channel with each channel's share, and every workstream in a grid with its status and its latest figure. Click a workstream and its view opens.
Every view names its source and its window. The search view shows queries, impressions, clicks and average position from Search Console, and the positions there are Search Console average positions. The ads view shows spend, conversions and cost per conversion for every campaign, as fresh as Google publishes them. The Leads view reads the sheet your own forms append to, newest first, so a lead is counted from your form, never from a platform's estimate.
A view whose source is not linked stays off the navigation, and the Integrations view lists what is connected. Jobs shows a coming-soon card until its data is trustworthy. Nothing on the screen is typed by a person, and there is no monthly PDF, because the page already says everything a PDF would, more recently.
What runs on a schedule, and what waits for a person?
Scheduled work runs whether anyone is at a desk. Prospects are sourced weekly to your target profile on Command. Content moves through research, draft and publish on your cadence on Launch, Growth and Command: each topic passes a demand gate on real search volume and the live top ten before a word is written, each piece is filed as a Google Doc in your Drive, and a featured image is generated per piece. The Google Ads change watch reads every account we manage at 7:05am Eastern. Where your forms feed the lead sheet, a lead watch compares that sheet with Ads and GA4 at 7:20am Eastern. The fallback snapshot bakes at 12:01am Central.
Judged work stays with a person. 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 with the draft, the mailbox and the time. Replies are classified, and not-interested and bounced addresses are suppressed. Named accounts are always reviewed by a person. Budget and bid changes in ad accounts are made by a person, never by a scheduled job. Approval on content is a setting you choose.
Your requests go the same way. Ask for a website change, a content topic, a keyword target or a category from inside the screen and it is logged, opened as a ticket with a number, and sent to your team. The confirmation on your screen carries the ticket number. None of those requests write to Ads, your CRM, your site or your Business Profile directly; a person makes the change, and the record shows when it was done.
What does a normal morning look like once it is running?
Take a Tuesday. At 7:05am Eastern the ads watch reads four things from your Google Ads account: the change history, with what was edited, by whom and through which tool; the list of account users; the conversion actions; and the campaign settings. It compares each with the day before. Our own writes and Google's routine churn are filtered out first. A third party changing a budget, a bid strategy, a network setting or the status of a spending campaign reaches the team as the run finds it; new ad copy, a geo change or a schedule change goes into the 8am digest. Across the mapped accounts in one 29-day window: 337 change events, 291 our own writes, 21 material.
At 7:20am Eastern, where your forms feed the lead sheet, the lead watch runs five named checks: loader, blind, ads blind, stalled and silent. It exists because of one case, anonymised: a tag change stopped every conversion for six weeks, 21 real leads landed in the sheet while Ads reported zero, and the owner paused the campaign that carried every counted lead and cut its budget 90 percent. The sheet is written server-side on every submission, so it is the count that cannot be wrong about whether a form was sent.
At 9am you open the page. The 12:01am snapshot renders first, the live payload arrives from cache, and because nobody has opened it since yesterday a pull starts behind the request; when it lands the numbers swap in and the stamp moves. Your CRM pipeline, Stripe payments, booking platform jobs, website leads and email statistics are current. Ads and GA4 show the newest hours Google has published. Search Console shows the newest day Google has released, two to three days back. Nothing on the page was typed by a person.
How soon does it show my numbers, and what should I check first?
Two to four weeks, and setup is not billed. Week one is access: the manager invitations, the CRM link, the website and its forms, and your login working. Week two is the first pull, which fills the Overview with your numbers, plus the answer-engine baseline across ChatGPT, Gemini, Claude and Grok, the keyword set for the search view, and the ads watch starting on your account. Weeks three and four are the content cadence, the first ads reports and the email flows. By the end of it every tile that can be filled from your accounts is filled. A view whose source is not linked stays off, and nothing is filled with a sample.
Your login is a single-use link from login.trulata.com, sent to the email on your seat. The Team view shows seats used of plan seats, and you invite by email as Member or Admin. Remove a seat and the revocation takes effect within 30 seconds. Every instance passes a preflight before every deploy, and one of its checks is that no other client's name appears anywhere in your files.
Before you sign, open demo.trulata.com. There is no form. It runs the same engine code every client runs, on a fictional company, with every number illustrative. Check three things. Click a headline metric and confirm it opens with its window. Open a workstream from the Overview grid and confirm the view names its source. Press Refresh and watch the stamp move. Then ask us which of your sources will be live and which will lag, because the answer is per source and we will put it in writing.
What runs, and how often.
| What | Where it comes from | How fresh |
|---|---|---|
| Page load | Our service, then your connected sources | Instant from cache; a snapshot older than 5 minutes is pulled behind the request |
| Refresh button | A forced pull of every connected source | 2 seconds to a little over 3 minutes, then the page reloads |
| Fallback snapshot | Nightly bake, every client, one registry | 12:01am Central; a failed pull leaves the previous page up |
| Outbound sourcing | Your target profile | Weekly; drafts to a review-first queue; every send logged |
| Content | Demand gate on search volume and the live top ten | On your cadence; approval optional |
| Ads change watch | Google Ads change history and user list, every managed account | Daily, 7:05am Eastern |
| Lead watch | Your lead sheet against Ads and GA4 | Daily, 7:20am Eastern, where forms feed the sheet |
| Your requests | The screen, to your team | Logged and ticketed as you send them |
The header stamp on every page says how old each number is: your CRM, Stripe, your booking platform, website leads and email statistics are live, Google Ads and GA4 lag by hours, and Search Console runs two to three days behind.
Questions, answered.
Do I have to connect anything myself?
No. You send four manager invitations from your own Google consoles, for Analytics, Search Console, Ads and Business Profile, and our team links your CRM, Stripe, your booking platform, your email campaign platform and your website forms from the inside. There is no wizard and nothing to paste.
What happens if one of my sources is down?
You see the last good numbers for that source, with a stamp saying how old they are. The page never shows an error and never ships an empty section; the nightly bake refuses to deploy a failed pull and leaves the previous page up.
Does anything send email or spend money on its own?
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. Budget and bid changes in ad accounts are made by a person, never by a scheduled job. Stripe is read only, and nothing here creates a charge or a refund.
How long does setup take?
Two to four weeks, and it is not billed. Access in week one, the first pull and baselines in week two, content, ads reports and email flows in weeks three and four. A view whose source is not linked stays off rather than showing a sample.
Can I ask for changes from inside the screen?
Yes. Website changes, content topics, keyword targets, categories and general requests go to your TruLata team from the screen. Each one is logged and opened as a ticket with a number you can quote back.
Why does Search Console lag when everything else is live?
Because Google releases Search Console data two to three days after the fact. The page shows the newest day Google has published and the header stamp says so. Ads and GA4 lag by hours for the same reason; your CRM, Stripe, website leads and email statistics are live.
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.