I Don't Open Analytics Anymore. I Just Ask.

A few weeks back I wrote about reading my GA4 numbers without leaving the chat. That was part one. I stopped opening Google Analytics. The chat read the traffic for me.

I framed it as an analytics story. I had it slightly wrong.

The chat is not reading "Google Analytics." It is reading my site. And my site is hosted on BlackOps, which means it has a shape the chat already understands. Posts. Pages. Newsletter signups. That is every site BlackOps hosts. Same three things, every time.

That shared shape is the whole trick. You are not querying a metrics API and translating the answer back into your own site. You are asking your site how it is doing, in plain language, and it already knows what a post is, what a page is, and what a signup is. Because it is the thing serving them.

So I built five tools that let you ask.

Five ways to ask your site what is working

Same three things. Different jobs.

Here is the part worth your time.

Every BlackOps site is posts, pages, and newsletter signups. The building blocks do not change. What you are trying to do with them does. So the question worth asking is never the same twice.

I run a blog. For me, posts are the product. The question I ask my site is which writing actually moved someone. Last 28 days: 971 sessions, 804 users. The traffic came from 443 direct, 316 google organic, 52 from a Medium repost, 12 from LinkedIn, 5 from the newsletter. The Medium repost outpulled LinkedIn four to one. I did not feel that. I asked, and the site told me. And when I mark a newsletter signup as a key event, ga4_landing_page_conversions tells me which post sent people to subscribe, not just which one got read.

Now hand the exact same three building blocks to someone else.

A consultant does not live and die by blog traffic. Their pages are the product. The services page. The about page. The contact form. Their question is which post pushes a reader toward the contact page, and which "popular" post is a dead end that converts no one. Same ga4_landing_page_conversions tool. Completely different definition of a win.

A product is different again. I also run blackopscenter.com, which is not a blog. It is a product with a pricing page and a signup. So the question there is the funnel. Last month: 6 people viewed pricing, 5 started the form, 1 signed up. Tiny numbers, but that is the exact chain I care about, and ga4_events hands it to me in one question. My blog never asks that. My product asks little else.

A newsletter-first writer judges every post by one number. Did it add subscribers. ga4_landing_page_conversions ranked by the signup event is the whole scoreboard. Traffic is noise. Subscribes are the game.

Same posts. Same pages. Same signups. Four people, four completely different definitions of working. The chat answers all of them, because the structure underneath is shared and your goal is the only thing that changes.

You do not learn a dashboard. You ask a question.

That is the shift, and it is bigger than five tools.

Analytics used to mean leaving what you were doing, opening a separate tool, remembering where the right report lived, and bending your actual question into its filters. The tool was generic, so you did the translating. Every time.

When your site is hosted somewhere that already knows it is made of posts, pages, and signups, you stop translating. You ask the site, in the words you would use anyway, in the same place you write the posts. It knows what you mean because it is your site, not a dashboard pointed at it.

Part one was me getting my analytics tab out of my own way. This is the bigger version. Your site is a thing you can talk to now. What you ask it is the only part that is up to you.

If you want it, it lives on BlackOps Center.