A dashboard shaped by what you connect.
What connecting really is.
Next to each tool’s name there is a single connect button. Press it, and the tool itself — Google, Stripe — opens its own sign-in window, the same screen you would see anywhere else. It asks, in that company’s own words, whether SiteOps may look at your figures. You press allow, the window closes, and the first numbers arrive while you’re still on the page.
That is the entire ceremony. SiteOps never sees your password — the permission lives with the tool, and you can withdraw it from your Google or Stripe settings whenever you like. And the permission only goes one way: SiteOps can read your numbers, never change them. Revenue included — whether you take payments through Stripe, Paddle or Creem, SiteOps reads what came in and can’t move a price, issue a refund or touch a customer.
The first morning after.
The day after you connect, the page has already done a quiet night’s work. Yesterday sits assembled: how many people arrived, what they paid, which video brought them in — laid out in the order the story happened, not in the order the tools happen to sort it.
What surprises most people is what isn’tthere. No setup wizard asking you to build widgets, no grid of blank charts for tools you don’t use. Two connections produce a small page that is entirely true — and that turns out to be worth more than a big page that is half empty.
When a tool has no connect button.
Almost every business has one stubborn number that lives somewhere with no official way to connect — a booking system, an internal signup counter, a spreadsheet someone fills in by hand. For those, SiteOps gives you a private address to send numbers to.
Your developer runs one short line — once — that sends the figure there. And for your own site it’s even simpler: drop in our one-line SDK and page views, events and conversions flow in on their own. Either way the number lives on the page like every officially connected one: same blocks, same plain words, and nobody can tell it came in through the side door.
When tools come and go.
Disconnect a tool and its blocks fold away the same day — no dead tiles, no chart apologising for missing data. The page closes the gap and reads as if the tool had never been there. Reconnect it next quarter and its history returns with it.
New connections work the same way in reverse. Plug in Search Console and your search queries take a place beside your traffic, because those two explain each other. The layout follows what the numbers mean, not the order you connected things in — so the page always reads front to back, whatever it is made of.
Fair questions.
What can SiteOps actually do inside my accounts?
Read, and only read. When you approve a connection, the tool grants SiteOps permission to look at your figures — never to change settings, move money or post anything on your behalf. You can withdraw that permission at any moment from inside the tool itself, and the connection simply goes quiet.
One of my tools has no way to connect. Am I stuck?
No. SiteOps gives you a private address for numbers that live outside the usual tools — a booking system, an internal counter, a spreadsheet someone updates by hand. It's a URL that belongs to you: anything sent there becomes a block on your page, kept up to date by whoever owns that number. And for your own site there's the one-line SDK — paste the snippet once and page views, events and conversions flow in by themselves.
What happens to the page when I disconnect something?
Its blocks fold away and the page closes the gap — no empty tiles or broken charts left behind. Your history is kept, so if you reconnect the tool next quarter, its numbers come back with the past still attached.