Automated Kochava Spend Anomaly Alerts
Every hour, WebRun opens Kochava, checks each active campaign's spend pace and fraud flag rate against the thresholds you set, and the moment one crosses the line it texts the on-call marketing ops lead through Twilio with the campaign and the numbers, then saves the flagged campaign's report to Google Drive as a record.
How do I get alerted to install fraud or spend spikes in Kochava?
WebRun checks your active Kochava campaigns every hour for a spend spike or a fraud flag rate above the threshold you set. The moment either appears, it texts the on-call marketing ops lead through Twilio with the campaign and the numbers, and saves the flagged report to Google Drive, so wasted or fraudulent spend gets caught within the hour.
- Spend spikes and fraud flags get caught within the hour instead of at month end
- The marketing ops lead gets the exact campaign and numbers, not a vague alert
- Flagged reports build a record in Drive for spotting repeat offenders
Built for Mobile marketing teams · User acquisition teams · Performance marketing teams · Marketing operations
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
app.kochava.comin a real browser with your saved login - no setup, no API keys. -
1
Kochava - check spend and fraud rate
- Open Kochava and read each active campaign's hourly spend
- Read the fraud flag rate for each campaign
- Compare both against the thresholds you set
Done when Every active campaign has been checked against its spend and fraud thresholds.
-
2
Twilio - text on-call marketing ops
twilio.com
WebRun opens Twilio to text on-call marketing ops. - Text the on-call marketing ops lead naming the campaign and which threshold it crossed
- Include the current figure against the threshold
- Send only while the anomaly is still active
Done when The on-call marketing ops lead has been texted about the anomaly.
-
3
Google Drive - save the flagged report
drive.google.com
WebRun opens Google Drive to save the flagged report. - Save the flagged campaign's report to the anomaly tracking folder
- Name the file with the campaign and the date
- Keep prior flagged reports in place for pattern review
Done when The flagged campaign's report is saved to Drive.
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
Does WebRun pause the campaign itself?
No. It only detects and reports the anomaly. Pausing spend or disputing fraudulent installs stays a decision for your marketing ops lead.
What counts as a fraud flag rate anomaly?
Whatever rate you set as the threshold. Only campaigns whose flagged install share crosses that line get texted about.
How far back does the saved report go?
Each report covers the specific campaign and window that triggered the alert, and prior flagged reports stay in Drive so you can compare patterns over time.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.