Email Reports

The numbers people need,
in the inbox they already read

Schedule a summary of one project or many, or a whole dashboard, to land daily, weekly or monthly in each team’s own time zone. Recipients need an email address, not a Countly account.

In this demo deployment, one digest per team, each sent at its own hour in its own time zone.

Part of analytics

What lands
in the inbox

Every figure comes with its change against the period before, so a weekly email always says whether the number moved.

Analytics

The traffic most reports carry, for every project you list.

Total sessionsTotal usersNew usersTotal timeAverage time

Events

The outcomes you pick by name. One at zero still shows, because that is often the point.

Completed signupsSubmitted ordersFailed paymentsAny custom event

Revenue and crashes

For the people who act on them.

Paying usersPurchasesPurchase valueUnique crashesFatal and non-fatal

A whole dashboard

The board itself, widget by widget, for a date range of its own.

One widget per rowAs arrangedPDF copy

Set up once

A report for every team,
in a few minutes

Name it for the audience, pick what it carries, set when it goes out, and send it to yourself first.

Built to be trusted

Small details that keep
a digest worth opening

A report people stop trusting is a report they stop reading.

  1. 01

    Their time zone, not yours

    Set per report, so a Monday report reaches Berlin and Austin on Monday morning.

    Per report
  2. 02

    No account needed

    Send to a client, an executive or a shared inbox that has never signed in.

    Recipients
  3. 03

    One-click unsubscribe

    Each recipient’s link removes exactly that address from that report, with a way to resubscribe.

    Every email
  4. 04

    Never twice

    A send is stamped, so a restart or a second server in the same hour cannot send it again.

    Every send
  5. 05

    Access checked at send time

    If the owner loses access to a project, the report pauses instead of mailing data they can no longer see.

    Every send
  6. 06

    A PDF copy

    Attach the same report as a file for people who archive rather than read.

    Optional

Works with

Email Reports, with the
rest of Countly

Every feature reads the same live data, so an answer in Email Reports doesn’t stop there. These are the handoffs built in.

All features

Data ownership

Rendered on your server,
sent on your schedule

Every email is built fresh from the projects at send time, by the deployment that holds the data, and can go out under your own sender name and address.

Data privacy
AspectFlexEnterprise
EnvironmentDedicated single-tenant instanceYour cloud, your data center or air-gapped
Data residencyThe Google Cloud region you chooseWherever you deploy, including air-gapped networks
Vendor accessOperated by Countly; access limited, granted by you and loggedNo default access
ISO 27001Certified
ISO 27017Certified
ISO 27018Certified
SOC 2Type II examined
TISAX®Participant*

*Countly Ltd. is a TISAX® Participant. TISAX® is a registered trademark of and governed by ENX Association. Learn more at enx.com/tisax

Try it

Every feature.
One data layer.