Cloud · Service

    Know it's down
    before they do.

    Traffic, errors and uptime on one set of dashboards. When the checkout throws an error or the site stops answering, an alert reaches your team by email, Slack or SMS.

    See pricing
    At a glance
    From $0
    Typical Cloud plan: 2–3 weeks
    0/7
    Uptime checks
    0
    Alert channels: email, Slack, SMS
    WHAT'S INCLUDED

    Traffic, errors, uptime. One view.

    The Starter package is one site with up to eight standard events, uptime checks on up to five URLs, one dashboard, up to six alert rules and two rounds of changes. Custom events, funnels, migrations and extra dashboards are quoted in writing first.

    Analytics
    01
    Cloudflare Web Analytics, Google Analytics 4, or both
    02
    Standard events, up to eight: add to cart, checkout, purchase, sign-up. More are quoted
    03
    Conversion funnels for stores, priced separately
    04
    Consent settings for GA4
    05
    Migration from your current analytics, with history kept, priced separately
    Errors and uptime
    01
    Sentry error tracking, with stack traces and user context
    02
    Uptime checks around the clock on the pages that earn money
    03
    Alert rules with agreed thresholds
    04
    Alerts by email, Slack and SMS
    Dashboards and reports
    01
    A KPI dashboard of the numbers your team decides from
    02
    A monthly report template, priced separately
    03
    A written list of every alert, its threshold and who receives it
    04
    Every tool in an account in your name
    WHAT IT COSTS

    Setup from $149.

    Tool subscriptions are billed to your own accounts. The scope names the plan for each tool.

    $0
    Starting package
    Analytics, error tracking, uptime checks and alerts for one site: up to eight events, five URLs, one dashboard, six alert rules, two rounds of changes. Anything more is quoted in writing.
    0–3 wk
    Typical Cloud plan
    One site with standard events is shorter. The scope sets the date.
    0 min
    First call
    What you need to know and who needs to hear it, then a written scope.
    HOW LONG

    Four steps. Alerts last.

    The Cloud craft's typical plan. Custom events and extra dashboards move it.

    01
    Week 1

    Requirements

    KPIs, what needs watching, alert thresholds and who receives each alert.

    02
    Week 1

    Tool setup

    Analytics, error tracking and uptime checks configured in your accounts.

    03
    Week 2

    Dashboards

    KPI dashboards built on live data, and the monthly report template.

    04
    Weeks 2–3

    Alerts

    Rules set, each alert fired once as a test, reporting schedule switched on.

    IF IT GOES WRONG

    Every alert, tested.

    Fired once on purpose, before it is needed.

    01

    Test alerts

    Each alert is triggered once during setup, so the right person is known to receive it.

    02

    Thresholds in writing

    What fires, at what level and to whom is agreed first, so alerts stay few enough to be read.

    03

    History kept

    Moving from another analytics tool keeps your access to the data already collected.

    04

    Your accounts

    Analytics, Sentry and uptime tools sit in accounts in your name, with access you can remove.

    05

    Scope in writing

    Tools, events, dashboards and alerts are listed before setup. A change is priced before it is made.

    06

    Bugs fixed

    An event that does not record or an alert that does not fire is fixed as part of the setup.

    WHO IT'S FOR

    Live sites. With orders.

    If the second list sounds closer, start with the page it names.

    This service fits

    • 01
      A store where a broken checkout costs orders

      Errors and downtime reach the team by alert, not by a customer's message.

    • 02
      A web app in production

      Errors tracked with the stack trace, the release and what the user was doing.

    • 03
      A platform with many customers

      Analytics split per customer, for a SaaS product.

    • 04
      A team that decides from numbers

      Funnels, events and a monthly report, on data collected the same way every month.

    Start somewhere else

    • 01
      The site is slow, not broken

      Speed is an audit and a set of fixes. See Caching & Performance.

    • 02
      More orders from the same traffic

      Reading the funnel and testing changes is Growth Optimization.

    • 03
      Reports that send themselves to a sheet or a chat

      That is workflow work. See Business Automation.

    STANDARDS YOU CAN CHECK

    Every alert has an owner.

    Each one is written in the handover, and visible in the tools.

    01

    An owner and a threshold

    Each alert names who receives it, what triggers it and through which channel.

    02

    Google's event names

    GA4 store events follow Google's recommended names: add_to_cart, begin_checkout, purchase.

    03

    Errors tied to a release

    Sentry records which deploy introduced an error, with a readable stack trace.

    04

    Personal data scrubbed

    Error reports are configured to leave out passwords, card fields and other personal data.

    05

    Consent respected

    GA4 runs under the visitor's consent choice. The configuration is documented.

    06

    Dashboards on live data

    No spreadsheet is filled by hand. Every number on the dashboard comes from its source.

    BEFORE YOU BRIEF

    Before the first alert.

    Cloudflare Web Analytics, Google Analytics 4 or both for traffic. Sentry for errors. Uptime Robot for uptime checks. Grafana or Datadog where a team needs one dashboard across all of it. The recommendation follows the first call, and the scope names each tool and its plan.
    Uptime checks run around the clock. When a check fails, the alert goes to email, Slack or SMS. The check interval depends on the monitoring plan chosen, and it is written in the scope.
    Yes. A move from another analytics tool is part of the work, and access to your historical data is kept.
    Cloudflare Web Analytics does not use cookies. For GA4, consent settings are configured so tracking follows the visitor's choice. Whether that meets your obligations under GDPR or India's DPDP Act is a question for your legal adviser, and the setup is documented so they can check it.
    Some. Analytics that run in the browser, GA4 included, can be blocked. For a site proxied through Cloudflare, Cloudflare counts requests at its network, which a browser extension does not see. Running both gives two views to compare.
    Subscriptions are billed to your own accounts. Several of these tools have an entry plan at no charge, and the scope names the plan for each one and what would push you past it.
    Yes. Ongoing cover, such as dashboard upkeep, custom reports and a regular review of the numbers, is quoted in writing.
    You decide who receives what, and it is written down alert by alert. Every tool is set up in an account in your name, with access you can remove.

    Your site.
    Watched.

    A 30-minute call about what you need to know, and when. A written scope after it.

    See pricing