Automated AppsFlyer Blocked Install Digests
Every morning, WebRun opens AppsFlyer, reads yesterday's blocked installs with the fraud reason behind each, groups the volume by media source and campaign in a Microsoft Teams post, and pings you on Telegram when a partner's blocked share jumps enough to be worth a clawback conversation.
How do I review the installs AppsFlyer blocked as fraud?
WebRun reads the installs AppsFlyer blocked as fraudulent every morning and groups them by media source, campaign, and fraud reason. It posts the digest to Microsoft Teams with each source's blocked share, and pings you on Telegram when a partner spikes above its own trailing average, with the spend attached.
- Fraudulent traffic is attributed to a named partner the next morning
- Blocked share is compared to each source's own baseline, so alerts mean something
- Clawback conversations start with volume, reason, and spend already gathered
Built for growth managers · user acquisition teams · mobile app marketers · performance agencies
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 - read blocked installs and reasons
appsflyer.com
WebRun opens AppsFlyer to read blocked installs and reasons. - Open AppsFlyer and pull yesterday's blocked installs
- Record the fraud reason recorded against each block
- Break the totals down by media source, campaign, and ad group
- Compare blocked installs against attributed installs for the same source to get a blocked share
Done when Yesterday's blocked installs are counted by source with a reason and a blocked share.
-
2
Microsoft Teams - group them by media source
microsoft.com
WebRun opens Microsoft Teams to group them by media source. - Post the digest to your growth channel, one block per media source
- Show blocked installs, blocked share, and the top reason for each source
- List the campaigns inside each source that carried the most blocks
- Compare against the trailing seven day average so a normal day reads as normal
Done when The blocked install digest by media source is in Teams.
-
3
Telegram - ping you when a partner spikes
telegram.org
WebRun opens Telegram to ping you when a partner spikes. - Send a short alert when a source's blocked share rises well above its own trailing average
- Name the source, the reason, the volume, and the campaigns involved
- Include the spend attached to the blocked traffic so the clawback case is quantified
- Leave partner conversations and campaign changes to you. WebRun never contacts a network
Done when You know which partners spiked and by how much.
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 contact media partners or raise a claim?
No. WebRun builds the internal digest and stops there. Opening a clawback, pausing a source, or emailing a network is a conversation you have with the numbers in hand.
Does it change AppsFlyer settings or validation rules?
No. It only reads reports. Fraud protection rules, blocklists, and campaign settings stay exactly as your team configured them.
How does it avoid crying wolf?
Each source is compared against its own trailing seven day average, so a partner that always blocks a steady share stays quiet and only a genuine spike triggers the Telegram alert.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.