Run every location from one screen, and keep each business's numbers apart.
A second location, a second brand under the same owner or six trucks across three towns break a single-account dashboard the same way: the numbers merge, and a blended number cannot tell you which half is working. The Command Center is configured business by business, so every number is stored and shown under the business it belongs to, and where we build the form, each lead row names the page that produced it.
Keep two businesses on one account without merging a number.
Two businesses fit on one Command Center without sharing a number. Behind every Command Center is a per-client connection map: one entry for the business, with a pointer to every account we read for it. The analytics side of that map holds several accounts of each kind, one row per account. A client with two businesses gets a dashboard configured business by business: each business has its own Google Analytics property and its own content track, plus its own Search Console site and Business Profile listing where those are connected, and every number is stored and shown under the business it belongs to. Nothing reaches your screen by name-matching alone. During setup we surface the likely matches, a person confirms each account your dashboard reads, and a channel that does not apply is recorded as not applicable, so a gap is a deliberate answer, not a blank.
Two unrelated businesses under one owner are never summed. A combined session count or a combined lead count would describe a company that does not exist, so the workspace carries a standing rule against it. The same configuration keeps a second location readable on its own instead of folded into a total.
Read every Business Profile listing as its own location.
Each listing gets its own row in the map. Add our Google account as a manager on every listing you want read; we list the locations that access exposes, and a person confirms each one into the map. Reads run one listing at a time, so one listing's reviews, rating and listing performance are stored under that listing and never under another. The Business Profile connection page covers what is read and what is not.
Grant manager access in your own console and revoke it there, per listing. We hold no password for any of them.
Know which location or service line produced each lead.
The lead row tells you. When a form on your site is submitted, the form handler appends a row to a lead sheet server-side. Where we build your forms to capture it, that row carries the page the form sat on and the town the visitor gave, and the sheet keeps the page the visitor entered on, the referrer, the traffic source and any campaign identifier that came with the click. The Leads view reads that sheet newest first and shows the town on each row and the page in its detail. If your site separates locations or service lines by page, the row already says which one produced the lead. No tag has to fire. No cookie has to survive.
For a multi-truck business the town field carries the location. A quote request from a town on the edge of your service area shows as exactly that, and the outcome you set from the screen (contacted, quoted, won, lost, not a lead) is stored against the lead and shown on its row. A call straight to a truck counts only if your CRM records it; there is no call-tracking system. The lead ledger page explains why the count is kept server-side, and the attribution use case follows one lead from click to won job.
See spend and cost per lead for each location on its own.
You get it per campaign. The Ads view reports spend, conversions and cost per conversion for every campaign across every account in the map, so where each location or business runs its own campaigns, that location's figure is its own campaign row. The account-level totals on the view sum every mapped account, which is why campaigns, not accounts, carry the location. Google publishes performance hours behind, and the Ads view reads through yesterday. The daily change watch covers every mapped account, not only the first: at 7:05am Eastern it reads each account's change history and raises material changes made by anyone other than us, including Google's own auto-applied recommendations and any change to who has access. The ads reporting page describes the watch and the two incidents it exists for.
Where the business runs on a CRM or booking platform, the Jobs view reads jobs and the job pipeline live, and it appears only when that connection exists. Pipeline stages and sources come from the CRM; today the CRM we connect is GoHighLevel.
Give each location manager their own sign-in.
Invite each manager from the Team view. It shows the seats on your plan and who holds them; add a manager by typing their email and choosing Member or Admin. They sign in at login.trulata.com with a single-use magic link, so there is no password to set or share. Every seat opens the same workspace: a manager sees the screen you see, and no seat can change a connected account from it, because the product has no such write path for anyone. Remove a seat from the Team view and it stops working within thirty seconds.
Seat counts follow the tier: three on Starter, three on Launch, ten on Growth and unlimited on Command. A business with a manager per location needs a seat for each of them; the tier table has the numbers and the team view page has the detail on roles and revocation.
Connect several accounts in the same two to four weeks.
Setup takes the same two to four weeks, with more rows in the map. Week one is access: manager invitations on each Google property, account and listing, plus the access you grant our team to connect your CRM, Stripe, your booking platform, ActiveCampaign and your forms from the inside. There is no wizard and no client-side OAuth. Week two is the first pull, the baselines and keyword set per business, and the ads watch on each account. Weeks three and four bring the content cadence, the ads reports, the email flows and the goals. Views appear as their sources connect, so a location whose listing is confirmed in week one is on screen before a location whose owner has not yet granted access.
If you already run the marketing across several locations yourself, the local services marketing page describes the agency side of the same work, run by our team on the same screen.
What stays separate, and how fresh it is.
| What | How it is kept apart | How fresh |
|---|---|---|
| Sessions, sources, pages, key events | One GA4 property, configured per business | Hours behind intraday, set by Google |
| Campaign spend, conversions, cost per conversion | One campaign row per campaign, across every mapped account | Through yesterday; change history read daily at 7:05am Eastern |
| Queries, impressions, clicks, average position | One Search Console site, configured per business | 2 to 3 days behind, set by Google |
| Reviews, rating, listing performance | One Business Profile listing per location | Through yesterday, on Google's schedule |
| Leads | One row per submission; page and town on the row, landing page, referrer, traffic source and campaign identifier on the sheet where the form captures them | Live, the moment a form is submitted |
| Seats | One per manager, Member or Admin | Removed from the Team view; access ends within 30 seconds |
Every account your dashboard reads was suggested by us and confirmed by a person, and a location whose access has not been granted shows as not connected rather than borrowing a neighbour's number.
Questions, answered.
Can two businesses share one Command Center?
Yes. The workspace is configured business by business: each business has its own Google Analytics property and content track, plus its own Search Console site and Business Profile listing where those are connected. Every number is stored and shown under its business, and the two are never summed.
Does each location need its own Google Business Profile listing connected?
Each listing you want read needs our Google account added as a manager on it. A person confirms each one into the map on its own row, and it is read as that listing.
How do I know which location a lead came from?
From the lead row. Where we build the form to capture it, it records the page the form sat on and the town the visitor gave, and the sheet keeps the landing page, referrer, traffic source and campaign identifier, all written server-side when the form is submitted. The Leads view shows the town on the row and the page in the lead's detail.
Can each manager have a login?
Yes. Invite them by email as Member or Admin and they sign in with a single-use magic link. Seats are three on Starter, three on Launch, ten on Growth and unlimited on Command.
Does a manager's seat show only their location?
No. Every seat opens the same workspace. The separation is in the data rows, not in who can see them.
Do you track calls to individual trucks?
No. A phone lead counts only if your CRM records it. There is no call-tracking system.
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.