MT5 Alerts And Notifications Setup

I missed a 120-pip GBPUSD breakout in September 2025 because my laptop went to sleep. I had done everything right on paper: price alert set at 1.3410, MT5 mobile app installed, push notifications "enabled." Then I went for a forty-minute run, the laptop lid closed, Windows suspended the terminal, and the alert that should have fired at 11:42 sat in a dead queue until I opened the lid at 12:30. Price was at 1.3530. The move I had waited nine days for happened while my notification system was technically perfect and practically useless. That afternoon I rebuilt my entire mt5 alerts and notifications setup from zero — and I mean from zero, assuming every default setting was lying to me.

This guide is that rebuild, documented. You will get the exact setup that now delivers alerts to my phone in under ten seconds, the latency measurements that proved which parts matter, the mistakes that cost me real money, and the math for sizing the trades those alerts trigger. No theory. Just the infrastructure between you and the next move.

The Night My Phone Stayed Silent and My Stop Didn't

Let me give you the full damage report, because "missed alert" sounds minor until you price it. I was short EURJPY from 162.40 with a stop at 163.10 — a clean 70-pip risk on a $12,000 account, 0.5 lots, roughly $350 at risk. My plan was to move the stop to breakeven if price broke 161.80. I set a price alert at 161.80, left the desk for dinner, and trusted the push notification. The terminal was on a home PC. The home PC decided 7:40 PM was a good time to install Windows updates and reboot.

The trade itself was fine. The plan was fine. The infrastructure failed, and infrastructure failures are the most expensive kind because they ambush your best plans. That night ended my era of running alerts on a home PC. If your alerts live on hardware that sleeps, updates, or reboots, they are decorative. The MT5 VPS setup guide is the permanent fix — a terminal that never sleeps is the foundation everything below assumes.

What I Measured: Alert Latency Across Three Setups

After the reboot disaster I stopped guessing and measured. I set identical price alerts on three setups, triggered them with a known price touch, and timed how long the notification took to reach my phone with a stopwatch. Ten trials each, averaged:

Two findings that changed my setup. First, push beats email by an order of magnitude — 4 seconds versus 47. Email alerts are a backup channel, not a primary one. Second, the VPS missed zero alerts across all trials while the home PC missed two out of ten simply from sleep states. That 20% miss rate on a home PC is not a configuration problem. It is a physics problem: consumer hardware is designed to sleep. For the phone-side half of the equation, the MT5 mobile monitoring guide covers the MetaQuotes ID registration that makes push work at all.

Notification Mistakes That Cost More Than Missed Pips

Mistake one: alert spam until I ignored everything. In early 2025 I had fourteen alerts armed across six pairs — every support touch, every MA cross, every RSI extreme. My phone buzzed forty times a day. Within two weeks I had trained myself to swipe every MT5 notification away unread, which meant the one alert that mattered got swiped too. Forty buzzes a day, zero attention. I now run a hard cap: five alerts maximum, each tied to a written trade plan. An alert without a plan is noise with a ringtone.

Mistake two: push notifications without the MetaQuotes ID. For three weeks I believed push was "enabled" because the checkbox was ticked in MT5 options. It was not working because I had never entered my MetaQuotes ID from the mobile app into the desktop terminal's Notifications tab — the checkbox enables the feature, the ID tells it where to send. Test every alert path with a deliberately triggerable alert before you trust it. This takes ninety seconds and I skipped it for three weeks.

Mistake three: no redundancy on the one alert that mattered. The EURJPY dinner disaster had a single point of failure: one PC, one channel. Now critical alerts run dual-channel — push as primary, email as backup — from a VPS that does not sleep. Redundancy feels paranoid until the night it pays for itself. Paranoia is cheap. Reboots are expensive.

Setting Up MT5 Alerts That Actually Reach You

The manual, step by step, in the order that prevents the mistakes above. This assumes your terminal runs on a VPS or an always-on machine — if it does not, fix that first, because no settings page overcomes a sleeping computer.

First, register the destination. Open MT5 on your phone, go to Settings → Messages, and copy your MetaQuotes ID (eight characters). On the desktop terminal: Tools → Options → Notifications → check "Enable Push Notifications" → paste the ID → click Test. Your phone should buzz within seconds. If it does not, the ID is wrong or the phone has notification permissions off — fix this before continuing.

Second, create the alert. In the Toolbox window (Ctrl+T), open the Alerts tab, right-click → Create. Set the symbol, the condition (Bid >, Bid <, Ask >, Ask <), the price, and — this is the field everyone ignores — the timeout. Timeout is how long the alert waits before it can fire again; set it to at least the duration of your typical move, or one breakout will buzz you twelve times as price oscillates around the level. I use 60 minutes for H1 levels, 240 for daily levels.

Third, add the email backup for critical alerts only. Same Options → Notifications flow, but the Email tab: your SMTP server, login, and a test send. Gmail users need an app password, not the regular password — that detail cost me an hour the first time.

The Alert Math Nobody Does

Here is a small piece of arithmetic that decides whether your alert system is an asset or a slot machine. Every alert has a total latency budget — the time from the price touching your level to you seeing it — and you should know yours:

The sleeper variable is Phone Wake. Android's battery optimization can delay push delivery by up to thirty seconds — an eternity on a news spike. Whitelist the MT5 app from battery optimization (Settings → Apps → MT5 → Battery → Unrestricted). iPhones are generally faster here but check that Focus modes are not silencing the app. MetaTrader 5's official help pages document the Notifications tab options if you want the vendor's version of these steps.

Running Alerts Like Infrastructure, Not Gadgets

The mindset shift: alerts are infrastructure, like your broker connection or your VPS. Infrastructure gets checklists, redundancy, and periodic testing — not vibes. My weekly routine takes four minutes: every Sunday I fire one test alert per channel (push + email) and confirm both arrive. If the VPS terminal shows as disconnected in my monitoring, alerts are dead and I know before the market opens, not after a missed fill.

Execution discipline around alerts matters as much as the tech. Every armed alert maps to a written plan: the level, the trigger condition, the position size (pre-computed in the DarkWolf MT5 Signal Calculator), and the invalidation. When the phone buzzes, I am executing a decision I already made, not making one under adrenaline. The alert that fired without a plan in early 2025 got swiped away; the alert with a plan gets acted on in under a minute. That is the entire difference between infrastructure and gadget.

One more rule from experience: alerts arm scenarios, not predictions. "EURJPY breaks 161.80 → move stop to breakeven" is a scenario. "Gold looks strong → buy the dip maybe" is a horoscope. If you cannot write the alert's action in one sentence, delete the alert.

Sizing the trade the alert is about. Every alert in my system has its position size computed before the alert ever fires — because the moment the phone buzzes is the worst moment to do arithmetic. The DarkWolf MT5 Signal Calculator is where that math lives:

Write the resulting lot size directly into the alert's plan note. When EURJPY broke 161.80 that night, the only decision left should have been "move the stop" — not "how big was this position supposed to be." Pre-computed size turns a 3 AM phone buzz from a panic into a procedure. For multi-account traders running the same alerts across accounts, the multi-account setup guide covers keeping those sizes consistent.

MT5 Alerts Setup: Real Questions

Why are my MT5 push notifications not working?

Nine times out of ten, the MetaQuotes ID is missing or wrong. Open the mobile app → Settings → Messages, copy the eight-character ID, then on desktop go to Tools → Options → Notifications, enable push, paste the ID, and hit Test. The other common killer is phone-side: Android battery optimization delaying the push, or Focus modes on iPhone. Test every path with a deliberately triggerable alert before trusting it.

Can MT5 send alerts when my computer is off?

No — and this is the single most misunderstood fact about MT5 alerts. Alerts are evaluated by the desktop terminal, so if the PC is off, asleep, or rebooting for updates, nothing fires. The fix is a VPS: an always-on virtual server running your terminal 24/7. My measurements showed a home PC missing 20% of test alerts from sleep states versus zero misses on a London VPS.

What is the difference between an alert and a pending order?

An alert notifies you; a pending order executes without you. Alerts are for scenarios needing judgment — "price reached my level, now check structure before entering." Pending orders are for fully mechanical entries. I use alerts for discretionary setups and pending orders for breakout entries I would take sight unseen. Mixing them up is how traders either miss entries waiting for a buzz or get filled on setups they would have rejected.

How many alerts should I have active at once?

Five maximum — my hard cap after the forty-buzzes-a-day era trained me to ignore everything. Each alert must map to a written trade plan with entry, stop, and size pre-computed. More alerts do not mean more opportunities; they mean less attention per alert. If you genuinely need more than five scenarios watched, you need automation (an EA), not more buzzing.

Are MT5 email alerts reliable enough as a backup?

As a backup, yes; as a primary channel, no. My tests showed email averaging 47 seconds versus 4 seconds for push — fine for slow scenarios, useless for breakout scalps. Set it up with an app-specific password (Gmail requires this). The FCA's scam warnings are worth a read too — fake "MT5 alert" phishing emails are a real thing.

Do alerts work on the MT5 mobile app by itself?

Not the desktop-style price alerts — those need the desktop terminal running. But the mobile app has its own push notifications for trade events (fills, stop-outs, margin calls) under Settings → Messages, and those work standalone. I rely on them as a safety net: even if every price alert failed, I would still get buzzed the moment a stop-loss filled. Set those up first; they are the last line of defense.