Portfolio operators
See which property needs attention first, compare sites on a shared schema, and move from suspicion to evidence in one pass.
Telemetry for launches, diligence, and operator reviews
See what each Bitter property is earning, ranking, and risking.
BitterAnalytics is the measurement layer behind BitterHub. It consolidates GA4, search, revenue, deploy, and uptime signals so operators, buyers, and first customers can judge a property without reconciling six systems by hand.
- Authenticated analytics access through BitterHub
- Public liveness check at /up
- Support and follow-up routed through BitterDesk
Who it is for
Built for the people who have to trust the numbers quickly.
BitterAnalytics is not a generic self-serve analytics SaaS. It is the telemetry spine for the Bitter portfolio, designed to make launch reviews, operator decisions, and buyer diligence faster and more defensible.
Buyers and diligence reviewers
Verify traffic, search, revenue, deploy history, and uptime signals together instead of relying on selective screenshots.
First customers and support leads
Use BitterHub for the product view, then route questions, walkthroughs, and exceptions into BitterDesk without a dead-end handoff.
Onboarding path
Start in BitterHub. Learn here. Escalate through BitterDesk.
The public site explains the contract. The authenticated surface lives in BitterHub. Support and human follow-up live in BitterDesk. That split keeps the launch surface clear while giving operators and buyers a real next step.
Inspect or register a property in BitterHub
BitterHub is where operators access portfolio summaries, per-property trends, and the authenticated API path.
BitterAnalytics collects and normalizes the evidence
GA4, Search Console, Bing, Stripe, deploy, and uptime data are stored on a shared timeline so comparisons stay honest.
Escalate questions and exceptions in BitterDesk
When a buyer, customer, or operator needs a walkthrough, BitterDesk is the support path instead of an orphaned mailbox.
Try the live contract
A first user can verify the service without guessing where the product lives.
BitterAnalytics keeps the raw telemetry service private, but the public launch surface still exposes a clear proof path: health at this domain, authenticated analytics through BitterHub, and a repo-owned smoke check that watches the same promises.
Public health
GET /up returns the Rails liveness response, so an operator can confirm the running service before asking for data access.
Authenticated analytics
BitterHub reads summaries, trends, signals, and portfolio rollups through /api/v1/hub using the Hub service token.
Launch smoke
The repo smoke command checks the landing page, health endpoint, FAQ interaction, CTA path, and responsive screenshots.
Signals in the feed
One schema across growth, revenue, and reliability.
The value is not that BitterAnalytics connects to one more tool. The value is that every property ends up comparable on the same operating surface.
GA4 and Search Console
Sessions, users, landing pages, queries, impressions, clicks, CTR, and position trends for launch and SEO reviews.
Bing and sitemap visibility
Search coverage from Microsoft Search alongside Google data, with the same per-property framing.
Revenue snapshots
Stripe-backed totals and event ingestion keep buyer conversations tied to actual commercial performance.
Deploy and uptime context
Release cadence, availability, and response health sit near revenue and traffic so operational regressions are visible early.
Shared portfolio vocabulary
Every property is read on the same terms, which makes weekly review and triage less interpretive.
Historical trend preservation
Snapshots accumulate over time so launch comparisons do not disappear when vendor dashboards rotate or filter differently.
Human support path attached
When the data raises a question, the next action is explicit: open BitterDesk and resolve it with context already in hand.
Questions
Frequently asked questions
Is BitterAnalytics a standalone dashboard?
No. BitterAnalytics is the telemetry layer behind BitterHub. This site is the public launch surface; operators use BitterHub for authenticated portfolio views and API access.
What can a buyer or operator verify here?
The service combines traffic, search, revenue, deploy, and uptime signals so launch reviewers and diligence buyers can compare a property's performance without relying on hand-picked exports.
How does a new property get onboarded?
Properties are registered through BitterHub. BitterAnalytics then collects the configured source data on a shared cadence and makes it available through the authenticated Hub surface.
Where do support, walkthroughs, or exceptions go?
BitterDesk is the human support path. Use it for walkthroughs, data disputes, onboarding help, or launch follow-up that needs a real operator.
Support path
Need a walkthrough, dataset, or operator follow-up?
Open BitterDesk so the portfolio context, support loop, and next action stay attached to the same launch conversation.