Weekly

Get weekly Customer.io campaign numbers by email

Each Monday you get one table of sends, opens and clicks per campaign for the past week.

Runs: Weekly
Apps: Customer.io
AI: Not needed
Access: App API key (read)

Send this to your assistant

Create a ClickRuntime automation: every Monday at 8am, email me a table of last week's sent, opened and clicked counts for each of my Customer.io campaigns. My workspace is in the EU region.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

Customer.io campaign metrics are rarely compared across campaigns. Marketing runs onboarding, win-back and promotional flows, but each lives on its own screen, so nobody can quickly say which sends are driving opens and clicks. Without a regular review, weak campaigns run for months.

Each week, this lists your Customer.io campaigns, fetches their metrics for the past seven days, and emails you a table with sends, opens and clicks per campaign. All your campaigns are lined up in one view.

Lifecycle marketers and growth leads who manage several automated campaigns use it to decide where to spend their next hour. Every figure comes from the metrics Customer.io reports for each campaign over the last seven daily steps, so one table covers all of your flows and the numbers match the dashboard.

What you get out of it

Compare campaigns in one table
Seeing every campaign together shows which ones drive engagement. You can quickly separate strong performers from ones that deserve a rewrite. Lining every campaign up in one table shows which ones drive engagement, and which deserve a rewrite or a retirement.
Find automated flows that stopped working
An onboarding campaign that quietly sends far fewer emails than before may be broken. The weekly figures reveal drops that nobody would notice by looking at one flow. An onboarding flow that quietly sends far fewer emails than last week may be broken, and a single-flow screen would not show it.
Focus effort on the biggest opportunities
A high-volume campaign with a low click rate is where improvement matters most. The table shows where a small change would reach many people. A busy campaign with a low click rate is where improvement matters most, because a small change reaches many people.
Keep leadership updated
Forward the email to leadership as a regular marketing report. It replaces manual exports and spreadsheet assembly each week. The email can go to leadership as a regular marketing report, so nobody assembles exports and spreadsheets each week.
Build a history for planning
Weekly metrics accumulate in your inbox as a record. When planning next quarter's lifecycle program, you can see what held up and what faded. Weekly metrics pile up in your inbox as a record, and planning next quarter's program can use what held up and what faded.

How it works

What happens, step by step

Once a week, ClickRuntime gets your list of Customer.io campaigns.
For each campaign it adds up the email sends, opens and clicks from the last 7 days.
Campaigns that sent nothing are left out, and you get one email with a table of the rest.

Before it runs live

Connect Customer.io

What you get

RunsWeekly

Get weekly Customer.io campaign numbers by emailtoday, 9:00Succeeded

Email · Weekly campaign metricsOnboarding drip Sent 2,310 Opened 1,402 Clicked 288

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Run it at a different time, more or less often, or only on weekdays
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other Customer.io steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

weekly_campaign_metrics_digest.pyexample

from clickruntime import on_trigger, credentials, notify, http

API = "https://api-eu.customer.io/v1"

@on_trigger
def run(event):
    headers = {"Authorization": f"Bearer {credentials.secret('CUSTOMERIO_APP_API_KEY')}"}
    lines = [f"{'Campaign':<32}{'Sent':>7}{'Opened':>8}{'Clicked':>9}"]
    for c in http.get(f"{API}/campaigns", headers=headers).json()["campaigns"]:
        series = http.get(f"{API}/campaigns/{c['id']}/metrics", headers=headers,
                          params={"period": "days", "steps": 7, "type": "email"}).json()["metric"]["series"]
        sent, opened, clicked = (sum(series.get(k, [])) for k in ("sent", "opened", "clicked"))
        if sent:
            lines.append(f"{c['name'][:31]:<32}{sent:>7}{opened:>8}{clicked:>9}")
    notify.email_me("Customer.io campaigns, last 7 days", "\n".join(lines))
    return {"campaigns": len(lines) - 1}

FAQ

Common questions

What period do the metrics cover?

The last seven days, using Customer.io's daily metrics for seven steps. Each email therefore reflects a full week of activity for every campaign in the list. The email covers the last seven days, using Customer.io's daily metrics, so each week shows a complete picture for every campaign.

Does it include newsletters as well as triggered campaigns?

It lists the campaigns returned by the Customer.io API for your workspace. If you want to limit the table to certain campaign types, your AI assistant can add a filter for approval. It lists the campaigns the API returns for your workspace, and it goes ahead only on your word.

Are conversion or revenue figures included?

The email covers sends, opens and clicks. Conversion metrics depend on how you track goals in Customer.io, and if they are available through the API they can be added to the table. Conversion figures depend on how goals are tracked in Customer.io, and they can be added to the table when the API provides them.

What permissions does it need?

App API key (read). Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it runs (weekly). Checks that find nothing to do and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

The moment it happens