All templates

Automated Litmus Email Client Reports

Every Monday, WebRun opens Litmus, reads the email analytics on last week's campaigns, works out which email clients and devices your subscribers actually opened on, compares the mix with previous weeks, posts the readership picture to Slack, and drafts the designer a QA priority list in Gmail.

Runs on WebRun · Strict Lockdown policy
Every Monday at 9:00 AM WebRunorchestrates each step
1 Litmus read the client and device mix
2 Slack post the readership picture
3 Gmail draft the QA priority list
In short

How do I find out which email clients my subscribers actually open on?

WebRun reports where your subscribers really read every Monday. It reads Litmus email analytics on last week's campaigns, breaks opens down by email client and device, compares the mix with recent weeks, posts the picture to Slack, and drafts your designer a ranked QA priority list.

  • QA time goes to the clients your list actually uses
  • A shift in the mobile to desktop split is caught weekly
  • No email reaches your list from the automation

Built for email designers · marketing teams · CRM managers · agencies

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens litmus.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Litmus - read the client and device mix
    litmus.com
    WebRun in Litmus: read the client and device mix
    WebRun opens Litmus to read the client and device mix.
    • Open Litmus and go to email analytics for last week's campaigns
    • Read the share of opens by email client and by device type
    • Note dark mode opens and the split between mobile and desktop
    • Compare the mix against the previous few weeks to spot a shift
    • Do not change a test configuration or send anything. WebRun only reads the analytics

    Done when Last week's opens are broken down by email client and device with the change against recent weeks.

  3. 2
    Slack - post the readership picture
    slack.com
    WebRun in Slack: post the readership picture
    WebRun opens Slack to post the readership picture.
    • Post the readership picture to your marketing channel
    • Lead with the top clients by share of opens and the mobile to desktop split
    • Show what changed against recent weeks so a shift is obvious
    • Name any client that has grown enough to be worth testing from now on

    Done when The marketing channel has this week's readership picture.

  4. 3
    Gmail - draft the QA priority list
    gmail.com
    WebRun in Gmail: draft the QA priority list
    WebRun opens Gmail to draft the QA priority list.
    • Draft an internal email to the email designer with the QA priority list
    • Rank the clients to test on next send by share of your actual opens
    • Name the clients no longer worth spending QA time on
    • Leave the email in Drafts for you to send. No campaign or subscriber is emailed

    Done when The designer has a drafted QA priority list waiting for your approval.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
litmus.com
ScheduleRuns automatically on this cadence
Every Monday at 9:00 AM
DeliveryHow each run's result reaches you
Readership report · Slack
OutputWhat each run produces - A weekly readership breakdown by email client and device, with the change against recent weeks and a ranked QA priority list.
Text
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it send any email to my list?

No. WebRun reads analytics on campaigns you already sent. The only email it writes is an internal QA note to your designer, and that stays in Gmail Drafts until you send it.

Does it change my Litmus tests?

No. It reads the analytics view only. Adding or removing a client from your test set is a human decision made from the priority list it produces.

How does it decide what is worth testing?

It ranks clients by their share of your actual opens over recent weeks, so QA time follows where your subscribers really read rather than a default list of clients.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.