Automated AppsFlyer Attribution Monitoring
Every morning, WebRun opens AppsFlyer, reads yesterday's installs and in-app events per media source and app, compares each against its own recent daily baseline, posts sources that fell sharply or reported nothing to Slack, and drafts a Gmail message to the affected partner that waits unsent for your review.
How do I find out when a media source stops reporting installs?
WebRun watches your AppsFlyer attribution every morning. It compares yesterday's installs and events for each media source against that source's own 14 day baseline, posts sharp drops and silent sources to Slack, and drafts a partner email in Gmail that waits unsent for your approval.
- A silent media source is caught the next morning, not at month end
- Partner emails are written and waiting, never sent unreviewed
- Quiet days stay quiet, so every alert matters
Built for user acquisition managers · mobile growth teams · app marketing agencies · performance marketers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
hq1.appsflyer.comin a real browser with your saved login - no setup, no API keys. -
1
AppsFlyer - compare installs against baseline
appsflyer.com
WebRun opens AppsFlyer to compare installs against baseline. - Open AppsFlyer and pull yesterday's installs and in-app events by media source and app
- Compare each source against its own trailing average for the last 14 days
- Flag any source reporting zero, or well below its own baseline, and note the size of the gap
Done when Every media source with a sharp drop or no data is listed with its baseline and gap.
-
2
Slack - post the sources that dropped
slack.com
WebRun opens Slack to post the sources that dropped. - Post the flagged sources to your growth Slack channel, biggest gap first
- Show yesterday's number, the 14 day average, and the percentage change for each
- Stay silent when every source is inside its normal range
Done when The growth channel has today's list of sources that went quiet.
-
3
Gmail - draft the partner email
gmail.com
WebRun opens Gmail to draft the partner email. - Draft a short Gmail message to each affected media partner naming the app, the dates, and the observed drop
- Attach the figures so the partner can check their side without a second email
- Leave every message as an unsent draft. You review and send it yourself
Done when A partner email sits in Gmail drafts for each flagged source, unsent.
How is each run configured?
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.
Every action is checked against this policy before it runs.
Questions, answered
Will it email my media partners on its own?
No. WebRun writes the partner email and leaves it as an unsent Gmail draft. You read it, adjust the tone, and press send, so no partner hears from you without a human deciding.
How does it tell a real outage from a slow day?
It compares each source against its own trailing 14 day average rather than a fixed number, so a small source with naturally low volume is not flagged while a large source going silent is caught immediately.
Does it alert every day even when nothing is wrong?
No. When every media source sits inside its normal range the run posts nothing, so a Slack message from this workflow always means a source needs looking at.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.