How SendTidings works.
Short articles on connecting integrations, sending the monthly report, and the handful of concepts that make everything else click. Skim the categories below, or jump straight to whatever you’re stuck on.
Heads up: these docs are still being illustrated with screenshots. You found this page through the URL bar; we haven’t added it to the nav yet. The writing is ready to read; the visuals are catching up.
- 01
Getting started
Set up your first site, send your first report, and learn the SendTidings way of working.
- 02
Integrations
Connect analytics, Search Console, uptime, and email providers once at the org level.
- Connect Plausible Connect Plausible once at the org level, cloud or self-hosted, and every site you've already added picks it up. No per-site key typing.
- Connect Google Analytics 4 Connect GA4 once per Google account. Each Google account holds its own grant, so multi-account setups need one connection per account.
- Connect Matomo Connect Matomo once at the org level, cloud or self-hosted. Same connect-once shape as Plausible: your URL, your token, every site inherits.
- Connect Cloudflare Web Analytics Connect Cloudflare Web Analytics with an account ID, site tag and a read-only API token. Free, privacy-first, and already on if your sites sit behind Cloudflare.
- Connect Google Search Console Connect Search Console once per Google account. Each property the account has access to becomes selectable at the site level.
- Connect UptimeRobot Connect UptimeRobot once with a read-only API key and pull monitor stats into every site's monthly report. You don't need uptime on every site.
- 03
Reports
Recipients, schedules, content, and how the monthly report actually gets built and sent.
- Schedule your monthly reports Pick a send day once per site and the report goes out automatically every month, covering the previous calendar month. Pause and resume with a single toggle.
- Send test email vs Send report now Two buttons, two completely different code paths. Test emails don't track opens, don't create history, don't flip badges. Here's when to use which.
- 04
Branding & sender setup
Your logo, your colours, and sending from your own domain so the report looks like yours.
- 05
Troubleshooting
When something looks off — badges not appearing, providers showing zero, Google going quiet after a week.
- Report shows zero visitors but the analytics tool has traffic Almost always a primary-provider mismatch: the site's pointing at Plausible whilst the data lives in GA4. One click and you're sorted.
- Why the Opened badge hasn't appeared yet On hosted SendTidings, open tracking is mostly automatic. The badge stays at Delivered for a short list of reasons — here's the checklist.
- Google account stopped working after a week Google OAuth defaults to Testing mode, which expires refresh tokens after 7 days. Here's why, what to do this week, and how to fix it for good.
- 06
Concepts
The mental model — orgs vs clients vs sites, primary providers, and how SendTidings thinks about your work.
- Org, client, site: the three levels The three-level model SendTidings uses: your agency on top, your clients in the middle, their sites at the bottom. It matters more than it sounds.
- Primary provider: which analytics source feeds the report Each site has one primary analytics provider: the one whose numbers go in the report. Switching takes one click, but you have to know it exists.
- Open tracking: directional, not precise Open rates are a vibe check, not a count. Apple Mail inflates, image-blockers under-report. Here's how to read the badge honestly.