Kite features Kite alerts notifications push notification email alert alert log browser notification

Kite alert notifications

From WebNotes, a public knowledge base. Last updated 21 June 2026. Reading time ~10 min. Level: Beginner.

Key facts

Notification channels	An in-app or browser notification on Kite, plus an email to the registered address, when an alert triggers
Email trigger events	Sent when an alert fires, and separately when an alert is auto-disabled (Zerodha support, June 2026)
ATO notifications	Push and email on both the trigger and the order placement of an Alert-Triggered Order
The authoritative record	The Alerts section at kite.zerodha.com/orders/alerts; a fired alert moves out of the active set there
Server-side firing	Alerts fire on Zerodha's servers; a missed notification does not mean the alert did not trigger
No extra cost	Notifications are free; no setup beyond enabling push or browser permission

Kite alert notifications are the messages Zerodha sends when a price alert fires: an in-app or browser notification on the Kite interface, plus an email to the address registered with your account. The alert itself is evaluated and fired on Zerodha’s servers, so a notification that never reaches your screen does not mean the alert failed; it means the delivery failed, and the Alerts section still records the trigger. Understanding that split, server-side firing versus device-side delivery, is the key to diagnosing every “my alert didn’t notify me” case.

This article sets out the notification channels Kite uses, the events that generate an email (a trigger, and separately an auto-disable), how Alert-Triggered Orders add a second placement notification, how to enable push and browser notifications on each platform, where the authoritative log of fired alerts lives, and the common reasons a notification does not arrive. It is the reference companion to the add-an-alert how-to and to the alerts-disabled fix.

Conflict-of-interest disclosure. This guide is published by the WebNotes Editorial Team for informational purposes and is written independently. WebNotes operates a Zerodha account-opening referral programme, disclosed on the pages that carry the referral link; this guide does not carry it and earns no referral commission from the procedure described here.

The notification channels

Kite delivers a triggered alert through two channels, and an ATO adds a third event.

Channel	When it fires	Depends on
In-app or browser notification	The moment an alert triggers	Push permission on the app, or notification permission for kite.zerodha.com in the browser
Email	When an alert triggers, and separately when an alert is auto-disabled	The email address registered with the Zerodha account; no setup
ATO placement notification	When an ATO’s linked orders are placed on the exchange	Push and email; in addition to the trigger notification

The in-app or browser notification is the fast channel: it appears on the device you are using the instant the alert fires, if the device has permission and is reachable. The email is the durable channel: it goes to your registered address regardless of which device, if any, is open, so it is the one that reaches you when you are away from the screen. For an ATO, Zerodha sends push and email notifications on both the trigger and the order placement, so you get separate confirmation that the alert fired and that the basket reached the exchange.

Server-side firing versus device-side delivery

This is the single most useful fact about Kite notifications: the alert fires on Zerodha’s servers, not on your device. Zerodha’s monitoring evaluates your condition against the live tick feed centrally. When the condition is met, the server fires the alert, moves it out of the active set, sends the email, and pushes the notification. The push notification is the only part that depends on your device being online and permitted.

The practical consequence is that a missing notification almost never means the alert failed to fire. If you set an alert, the price clearly crossed your level, and you saw nothing, the first check is the Alerts section at kite.zerodha.com/orders/alerts: if the alert has moved out of the active list, it fired, and only the notification delivery to your device fell through. This is also why a closed app or browser does not stop an alert: the server fires it and the email lands either way. The one genuine case where an alert does not fire, a missed tick, is covered separately in the alert-not-triggered diagnosis.

Enabling push and browser notifications

A notification only reaches your device if the channel is permitted. Each platform handles this in its own settings, not inside Kite.

Kite app on Android. Open Settings, then Apps, then Kite, then Notifications, and enable the notification categories. Android can also throttle background apps under battery optimisation; exempt Kite from aggressive battery saving if notifications arrive late or not at all.

Kite app on iOS. Open Settings, then Notifications, then Kite, and enable Allow Notifications along with the alert styles you want. iOS Focus modes and the Scheduled Summary can hold or batch notifications; check those if alerts arrive delayed.

Kite web in the browser. On your first alert, Kite prompts to allow notifications; click Allow. If you previously denied it, open the browser’s site settings for kite.zerodha.com and switch notifications to Allow. Some browsers periodically revoke notification permission for sites you have not visited recently, so this can need re-enabling.

Email. Email notifications need no setup; they go to the address registered with your Zerodha account. If trigger emails are missing, check the spam or promotions folder and confirm the registered email is current in your profile.

The notification log: where fired alerts are recorded

There is no separate notification inbox inside Kite; the Alerts section is the log. A triggered alert leaves the active list, which is itself the record that it fired. For an ATO, the orders the alert placed appear in the order history page, identified by a bell icon, so the placement is logged alongside your other orders. The two emails, the trigger email and, for an ATO, the placement email, form a dated trail in your inbox that you can search after the fact. Together these are the authoritative record; treat the on-screen push as a convenience, not the system of record.

Why a notification may not arrive

A notification can fail to reach you for several reasons, none of which mean the alert did not fire.

Push permission is off or revoked. The most common cause. The app or browser permission was never granted, was turned off, or, on the web, was auto-revoked. The alert still fired and emailed; only the push fell through.

The device was offline or the app was killed. A device with no connectivity cannot receive a push at the moment of firing. The email still arrives when the device reconnects, and the Alerts section still shows the alert as fired.

Battery optimisation or a Focus mode held it. Android battery saving and iOS Focus or Scheduled Summary can delay or suppress a push. The notification may arrive late or be batched rather than appear instantly.

The email went to spam. Trigger and disable emails can be filed under spam or promotions by the mail provider. The email was sent; the filter hid it.

You expected a notification from a one-time alert that already fired. A simple alert fires once and turns off. If it fired earlier, it will not fire again, and editing it does not re-arm it; see the modify-or-delete guide.

In every case the diagnostic is the same: check the Alerts section. If the alert moved out of the active set, it triggered, and the problem is delivery, which you fix by enabling the channel. If it is still active and the price genuinely crossed the level, the issue is the alert, not the notification, and the missed-tick diagnosis applies.

The auto-disable email

Separately from trigger notifications, Kite emails you when an alert is auto-disabled. The disable events are a corporate action that moves the instrument’s price by more than 2 per cent (extraordinary dividends, bonuses, splits, or rights issues), a derivative contract expiry, a delisting, suspension or series change, and the lapse of the 365-day alert validity. The email is a prompt: a disabled alert no longer monitors, so if you still want the condition watched, you re-enable or recreate it. The full set of disable conditions and the re-enable steps are in the alerts-disabled guide.

External references

References

Zerodha support, What are Kite alerts and how do I use them? (notification on Kite web/app plus email when an alert triggers; as of 21 June 2026).
Zerodha support, Why are Kite alerts disabled? (email notification sent when an alert is disabled; disable conditions; as of 21 June 2026).
Zerodha support, What is Alert Triggers Order (ATO)? (push and email notifications on ATO trigger and order placement, bell icon in order history; as of 21 June 2026).
Zerodha support, Why is a Kite alert not triggered even though conditions met? (server-side firing and missed-tick behaviour; as of 21 June 2026).

Frequently asked questions

How does Kite notify me when an alert triggers?

Kite sends a notification on the web or app interface and an email to your registered address when an alert fires. For an Alert-Triggered Order, you also get push and email notifications when the linked orders are placed on the exchange.

Why didn't I receive a Kite alert notification?

The alert may have fired server-side while your push or browser permission was off. Check the Alerts section at kite.zerodha.com/orders/alerts: if the alert moved out of the active list, it triggered and only the notification delivery failed, not the alert itself.

Do alerts still fire if my phone or browser is closed?

Yes. Kite evaluates and fires alerts on its servers, not on your device. The alert triggers and sends its email whether or not your device is online; only the in-app or browser notification depends on your device being reachable.

How do I enable push notifications for Kite alerts?

On Android, open Settings, Apps, Kite, Notifications and enable the categories. On iOS, open Settings, Notifications, Kite and enable notifications. On Kite web, allow notifications for kite.zerodha.com in the browser’s site-permission settings.

Where can I see a log of my triggered alerts?

The Alerts section under Orders is the record. A triggered alert leaves the active list, marking it as fired. For an ATO, the placed orders also appear in the order history with a bell icon, and the trigger and placement emails form a dated trail.

Why do I get an email saying my alert was disabled?

Kite emails you when an alert is auto-disabled, for example after a corporate action moves the price by more than 2 per cent, a derivative expiry, or the 365-day validity lapse. The email is a prompt to review and, if still wanted, re-enable the alert.

Does an alert notification mean my order was placed?

Only for an ATO. A simple alert notification just tells you the price condition was met; you still place any order yourself. An ATO sends a separate notification confirming the linked orders reached the exchange, which is the placement, not necessarily the execution.

Reviewed and published by

WebNotes Editorial Team

The WebNotes Editorial Team covers Indian capital markets, payments infrastructure and retail investor procedures. Every article is fact-checked against primary sources, principally SEBI circulars and master directions, NPCI specifications and the official support documentation published by the intermediary in question. Drafts go through a second-pair-of-eyes review and a separate compliance read before publication, and revisions are tracked against the SEBI and NPCI rule changes referenced in the methodology section.

Last reviewed: 21 June 2026
Conflicts of interest: WebNotes is independent. No relationship with any broker, registrar or bank named in this article.