Weekly
Get a weekly email of new users by source
Each Monday you see which UTM sources brought new users, compared with the week before.
- Runs
- Weekly
- Apps
- Amplitude
- AI
- Not needed
- Access
- API key + secret
Send this to your assistant
Create a ClickRuntime automation: every Monday at 8am, email me last week's new users in Amplitude grouped by UTM source, with the change from the previous week.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
Marketing teams spend on channels such as search, social, referrals and partners, and Amplitude can show where new users come from. But the picture is only useful when someone looks at it regularly. Most weeks no one has time to build the chart, choose the right user property, set the dates and compare with the week before. So a channel that doubled and one that quietly collapsed are both noticed at the end of the month, when the budget has already been spent.
Each week, the automation runs a segmentation query for new users grouped by a property such as the acquisition channel or utm_source, compares each group with the previous week and emails you a table of the counts and the change. The biggest movers are easy to see.
Growth marketers, founders who manage ad budgets themselves and agencies that report on acquisition each week can use it.
What you get out of it
Budget follows what works
With new users by channel next to last week's figures, you can move spend toward the sources that grow and away from the ones that stall, while the week is still fresh.
Channel failures are caught within a week
A campaign that was switched off by mistake, a broken tracking link or a partner that stopped sending traffic shows as a sharp fall in its row of the table.
Reporting takes no preparation
The same table arrives each Monday, so the weekly marketing meeting starts with data instead of a scramble to build charts in Amplitude. A weekly meeting is better when the first slide already exists.
Week-on-week change is built in
Each row shows the previous week alongside, so growth and decline are clear without mental arithmetic, and seasonality is easier to judge over several weeks. Both a slow decline and a sudden jump are easier to judge when the comparison is printed beside the number.
Stakeholders see acquisition without a login
Managers, clients and investors can read the email and follow how new users arrive, which makes budget conversations quicker and better informed. Budget talks become shorter when the numbers are shared.
How it works
What happens, step by step
Every Monday, ClickRuntime asks Amplitude how many new users arrived last week from each UTM source.
It compares each source with the week before.
You get an email listing every source with its new users and how many more or fewer it brought than last week.
Before it runs live
- Connect Amplitude
What you get
Build your own
Need it to work differently?
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 Amplitude steps into one automation
Under the hood
The code that runs this automation
import json
from datetime import date, timedelta
from clickruntime import on_trigger, credentials, http, notify
def amp(path, **params):
auth = (credentials.secret("AMPLITUDE_API_KEY"), credentials.secret("AMPLITUDE_SECRET_KEY"))
resp = http.get(f"https://amplitude.com/api/2/{path}", auth=auth, params=params)
resp.raise_for_status()
return resp.json()["data"]
def by_source(start, end):
e = {"event_type": "_new", "group_by": [{"type": "user", "value": "utm_source"}]}
data = amp("events/segmentation", e=json.dumps(e), start=start.strftime("%Y%m%d"),
end=end.strftime("%Y%m%d"), m="uniques", i=7)
return {label[1] if isinstance(label, list) else label: sum(series)
for label, series in zip(data["seriesLabels"], data["series"])}
@on_trigger
def run(event):
end = date.today() - timedelta(days=date.today().weekday() + 1)
this, prev = by_source(end - timedelta(days=6), end), by_source(end - timedelta(days=13), end - timedelta(days=7))
lines = [f"{src or '(none)'}: {n:,} ({n - prev.get(src, 0):+,})" for src, n in sorted(this.items(), key=lambda kv: -kv[1])]
notify.email_me("New users by UTM source, last week", "\n".join(lines))
return {"sources": len(lines)}FAQ
Common questions
Which user property defines the channel?
Does it count new users or all active users?
What happens to users with no channel value?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Post yesterday's Amplitude users to Slack
Your team starts each day with active and new user counts in the channel.
See how it worksFind out when a key Amplitude event stops firing
If Purchase events drop to zero or far below normal, you hear about it within the hour.
See how it worksKnow the moment your website goes down
Your team hears in Slack when the site stops responding or slows down, and again when it's back.
See how it worksKeep exploring
Set up “Get a weekly email of new users by source” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.