pnclPULSEGet API access

DROP ALERT NOTES

Why your alert fired on a quarter, not the match

Drop alerts carry a period field, and a full-match line is not the only market that moves. Reading period and sect so the right alerts reach you.

You set a rule for match drops and your phone buzzes over a third-quarter total. The alert is not wrong; the feed prices more than one market per event, and every alert carries the field that tells them apart. That field is period, and learning to read it is the difference between an alert stream and a noise pipe.

The field that names the scope

Each alert names the market in sect and the side in outcome, and carries period when the market has one, as the drop alerts guide lists the event's fields, checked 2026-10-12. The full-match market is period 0; numbered periods are the quarters, halves or maps inside the match. The documented example alert on the SSE setup page shows exactly this: a moneyline alert carrying period 4, a fourth-quarter market, not the match.

A fall in a period market and a fall in the full-match market are different events that happen to share a match. Your rule should know which one it is reading.

When period markets are the ones you want

Period and quarter markets move with the live game's rhythm, faster and noisier than the match line. If your product prices quarters or you model in-play segments, period alerts are the feed you actually want, filtered the other way: keep period above zero, drop the rest.

The same field, two products. What changes is the comparison you run against it.

When to filter them out

If your rule cares about the match, the check is one comparison: keep period 0, drop everything else. Put that check before your dedupe and your cooldowns, because a quarter's alert should not spend the match's cooldown budget. The dedupe guide builds its keys from id, sect, outcome, period and alerted together, precisely because the period is part of what makes two alerts different alerts.

Log it before you tune it

As with thresholds, the honest way to set the period rule is from your own log. A week of alerts grouped by period tells you how much of your stream is period-market traffic: on live basketball it can be most of it. Then the rule writes itself: if period alerts dominate and none are acted on, filter them at the top of the pipeline and let the match alerts through clean.

The period field is the difference between a match alert and a market alert. Read it first, and the stream stops surprising you.