IFTTT Pro Filter Code Notification Suppression and Run Accounting

IFTTT Pro filter code lets an Applet inspect trigger ingredients and conditionally skip the Notifications action, creating a practical noise-control layer without disabling the automation. The goal is to keep the trigger active for logging or future use while suppressing low-value phone alerts, but the boundary between a suppressed action and a recorded run remains unclear. Applet activity may show an evaluation even when no notification reaches the device, yet the interface does not distinguish whether that entry consumed a Pro run or was silently dropped.

Polling behavior adds further uncertainty. Many IFTTT triggers are polled rather than instant, and filter code only sees what each poll returns. Rapid bursts within one polling window may be collapsed into a single evaluation or missed entirely, so one-notification-per-real-world-event cannot be guaranteed. OS-level controls like iOS Focus or Android Do Not Disturb sit outside IFTTT and can hide a send that the platform recorded as delivered.

Does a filter-code skip that prevents the Notifications action still count as an Applet run in activity history and against Pro limits? How does IFTTT collapse or de-duplicate multiple trigger events that arrive inside a single polling window for a given service? Is there a documented per-Applet mute that keeps the trigger collecting data while suppressing only the phone notification?