Play 1
One project per client niche
Keep watches and the webhook scoped. The Discord channel for Client A never sees Client B’s hits.
Project “Northwind shorts.” 20 watches. One webhook.
Agencies
One feed of breakouts across every channel you manage.
Agencies and channel networks already keep competitor lists per client. Spike turns that list into a live feed. One signed POST when any watched upload crosses the line.
The cost of missing it
A spreadsheet of rivals is not a monitoring system.
Account managers cannot refresh fifty channels. Juniors miss the spike. Clients ask “why didn’t we jump on that?” after the weekend.
01
Each client niche has a different rival set — they should not share one noisy inbox.
02
Without a webhook, the first person who happens to be online is your alerting stack.
03
You are billed for channels, not for how many times a desk gets pinged.
Practical plays
Three ways to turn a spike into work.
Each play starts with channels you already know, then a threshold, then a hit in the dashboard — webhook if you want one.
Play 2
Standardize the threshold, customize the list
The view line can be the agency default. The channel list is what the strategist owns.
5,000 in 2 hours on every watch in the project.
Play 3
Scale is a channel cap, not a per-ping fee
Cover a whole niche without thinking about webhook volume. Limits are how many channels you watch.
Scale: 100 channels. Still one signed POST per hit.
On autopilot
Add the channels. Get the spike.
Load the lists you already sold the client. We turn breakouts into one feed.
01
Add the channels.
Paste a URL, @handle, or UC id. No YouTube API key. You pick the list — we do not search the whole site.
02
Set the view line.
Example: 3,000 views in the first hour. One condition per watch. That is what “a spike” means here.
03
We watch new uploads.
The tracker polls those channels. Several people watching the same UC id share the YouTube request.
04
You get a signed POST.
HMAC, retries, delivery log. Point it at Discord, n8n, or your own bot.
Questions about agencies.
Yes. You add the channels per project, set thresholds, and send hits to a webhook the desk already uses — Discord via n8n, Slack, or your own bot.
Yes. Projects keep watches separate. Point each project’s hits at the endpoint that client’s room uses.
No. Plans are channel counts. The trial is 3 channels for 7 days with a real signed POST.
More use cases
Same product. Different desk.
Strategy
Know the hour a rival video takes off.
Watch the channels you already compete with. When a new upload crosses your threshold, you get the ping — not a digest tomorrow.
DesksCopy the idea while it’s still in the first hour.
A threshold hit is a topic that already proved demand. Intercept it before the niche is flooded.
FacelessGet pinged when a format in your niche starts printing.
Compilation, narration, stock — the channels on your list are the research. A spike is the format to clone this week.
Start watching
Put the client rival list on a webhook. Start watching.
Watch a YouTube channel and set a view threshold. 3 channels for 7 days. No credit card.