Stay Informed Without Being Overwhelmed
A well-configured notification system is one of the most valuable but most underappreciated aspects of running trading bots effectively.
Get it wrong in one direction — too few alerts — and you miss critical events. A bot stops working at 3am due to an API error. Your drawdown limit triggers during a market crash. A position opens that’s ten times larger than expected. You find out hours later when the damage is already done.
Get it wrong in the other direction — too many alerts — and notification fatigue sets in. You start ignoring them. The critical alerts get buried among dozens of routine notifications. You dismiss them without reading — and miss exactly the event you set up notifications to catch.
The goal is precision: immediate awareness of events that require your attention, calm silence for everything else.
This guide walks through every notification type available on BitcoinEra, the correct configuration for each, how to set up different channels effectively, and how to build a notification system that keeps you genuinely informed without consuming your attention.
Notification Channels — What’s Available
BitcoinEra delivers notifications through four channels. Each has different characteristics that make it appropriate for different types of alerts.
Email Notifications
Characteristics:
- Delivered to your registered email address
- Persistent — stored in your inbox until deleted
- Suitable for detailed, information-rich alerts
- Not instantaneous — typical delivery within 1–3 minutes of the triggering event
- Can include full trade details, performance summaries, and formatted data
Best for:
- Performance summaries and reports
- Non-urgent informational alerts
- Detailed event notifications where context matters
- Records you want to keep for future reference
Worst for:
- Time-critical alerts requiring immediate response (API errors, large position opens)
- High-frequency bots — email for every trade would flood your inbox
Push Notifications (Mobile App)
Characteristics:
- Delivered directly to your phone’s lock screen and notification center
- Near-instantaneous — typically within 15–30 seconds of the triggering event
- Persistent until dismissed
- Suitable for brief, high-priority alerts
- Requires BitcoinEra mobile app installed and notification permissions granted
Best for:
- Critical alerts requiring immediate attention — API errors, drawdown limits, large position events
- Status change notifications — bot stopped, bot error
- Time-sensitive events where delay matters
Worst for:
- Detailed performance data (screen space limited)
- High-frequency alerts that would constantly interrupt your day
Telegram Notifications
Characteristics:
- Delivered to your Telegram account via the BitcoinEra bot
- Near-instantaneous delivery
- Supports rich text formatting — more context than push notifications
- Available on all devices where you have Telegram installed
- Can send longer messages with full trade details
Best for:
- Traders who use Telegram regularly and want trading alerts integrated into their existing messaging
- Detailed real-time alerts with full context
- Critical and important alerts alike
- Users who prefer Telegram over email for ongoing communication
How to set up: Account Settings → Notifications → Telegram → Click “Connect Telegram” → Follow the bot setup instructions → Verify connection with test message
Webhook Notifications (Advanced)
Characteristics:
- HTTP POST request sent to a URL you specify when an event occurs
- Enables integration with custom applications, automation tools, or third-party services
- Full event data sent as JSON payload
- Suitable for technically advanced users building custom notification or automation workflows
Best for:
- Developers building custom dashboards or monitoring applications
- Integration with tools like Zapier, Make (Integromat), or custom code
- Forwarding alerts to custom channels (Slack, Discord, SMS services)
- Building automated responses to specific bot events
How to set up: Account Settings → Notifications → Webhooks → Add Webhook URL → Select triggering events → Verify with test payload
Webhook payload example:
json
{
"event_type": "DRAWDOWN_LIMIT_TRIGGERED",
"timestamp": "2024-03-15T14:23:41Z",
"bot_name": "GridMaster X",
"bot_id": "bot_a7f3k2",
"allocated_capital": 1000.00,
"current_value": 850.00,
"drawdown_percentage": 15.0,
"drawdown_limit": 15.0,
"exchange": "binance",
"action_taken": "BOT_STOPPED"
}Notification Categories — Complete Reference
BitcoinEra organizes notifications into six categories. Here’s every notification type, what triggers it, and the recommended configuration for each.
Category 1 — Security Alerts
These notifications are triggered by security-relevant events on your BitcoinEra account. They cannot be disabled — they are mandatory for all accounts.
New Login Detected
Trigger: A successful login from a device or IP address not previously seen on your account.
Delivery: Email (immediate) + Push notification
What to do when you receive it:
- If it was you logging in from a new device — no action needed.
- If you don’t recognize the login — change your password immediately, revoke all active sessions, and contact support.
Cannot be disabled: Yes
Password Changed
Trigger: Your account password was successfully changed.
Delivery: Email (immediate)
What to do when you receive it:
- If you changed it — no action needed.
- If you didn’t change it — your account has been compromised. Contact support immediately.
Cannot be disabled: Yes
Two-Factor Authentication Changed
Trigger: 2FA was enabled, disabled, or modified on your account.
Delivery: Email (immediate)
What to do when you receive it:
- If you made the change — no action needed.
- If you didn’t — contact support immediately.
Cannot be disabled: Yes
API Key Connected or Removed
Trigger: An exchange API key was added to or removed from your account.
Delivery: Email (immediate)
What to do when you receive it:
- Verify the change was intentional.
- If you didn’t make this change — investigate immediately.
Cannot be disabled: Yes
Category 2 — Critical Bot Alerts
These are the most important operational notifications. Configure them for immediate delivery on all available channels — particularly push notifications and Telegram if you use them.
Drawdown Limit Triggered
Trigger: A bot’s drawdown has reached its configured limit. The bot has automatically stopped.
Why it’s critical: Your most important risk safety net has activated. The bot has stopped to prevent further losses. You need to review the situation before deciding whether to restart.
Information included:
- Bot name
- Current drawdown percentage
- Configured limit
- Capital value at trigger
- Number of open positions remaining (if any)
- Link to trade history for the period
Recommended delivery: Email + Push + Telegram (all channels, immediate)
Configuration: Notifications → Critical Bot Alerts → Drawdown Limit → Enable All Channels → Save
Daily Loss Limit Triggered
Trigger: A bot has lost its configured maximum for the current day. It has stopped trading until the next daily reset.
Why it’s critical: A significant adverse event has occurred within a single day — possibly a flash crash, major news event, or unusual market condition.
Information included:
- Bot name
- Loss amount and percentage for the day
- Configured daily limit
- Time of trigger
- Estimated resume time (next daily reset)
Recommended delivery: Email + Push + Telegram (all channels, immediate)
Bot Status — Error
Trigger: A bot has entered an Error state — something has gone wrong technically and the bot has stopped operating.
Why it’s critical: The bot is not running. It’s not protecting your positions or executing its strategy. Immediate investigation required.
Information included:
- Bot name
- Error type and code
- Error description
- Timestamp
- Last successful operation before the error
- Link to troubleshooting guide for this error type
Recommended delivery: Email + Push + Telegram (all channels, immediate)
API Connection Lost
Trigger: The connection between BitcoinEra and your exchange has been lost and was not automatically re-established within a defined timeout period (typically 5 minutes).
Why it’s critical: The bot cannot read market data or place trades. Any open positions cannot be managed. If the market moves significantly while disconnected — your risk parameters cannot protect you.
Information included:
- Exchange name
- Time connection was lost
- Bot(s) affected
- Last successful connection timestamp
- Suggested diagnostic steps
Recommended delivery: Email + Push + Telegram (all channels, immediate)
Unexpected Bot Stop
Trigger: A bot has stopped without a known cause — not triggered by drawdown limit, daily loss limit, or manual stop. May indicate a technical issue.
Why it’s critical: Something unexpected has caused the bot to stop. This may be a platform issue, exchange issue, or configuration problem.
Information included:
- Bot name
- Last known status
- Timestamp of stop
- Any available diagnostic information
Recommended delivery: Email + Push + Telegram (all channels, immediate)
Category 3 — Important Bot Alerts
These notifications are significant but not requiring immediate response in the middle of the night. Configure for push notification delivery during waking hours or email delivery for review at your next scheduled check.
Large Position Opened
Trigger: A bot has opened a position above a threshold you configure — expressed as a percentage of allocated capital.
Why it matters: Alerts you when the bot is making an unusually large trade relative to its normal behavior. May indicate a one-time opportunity the strategy has identified — or may indicate a configuration issue producing oversized positions.
Recommended threshold: 25–30% of allocated capital per position. Set higher (40–50%) if your bot regularly uses large positions by design.
Information included:
- Bot name
- Position size (USDT and %)
- Entry price
- Direction (long/short)
- Strategy reasoning (if available from bot)
Recommended delivery: Push notification (immediate awareness without requiring action)
Large Position Closed
Trigger: A bot has closed a position above your configured threshold — at any exit reason.
Why it matters: Significant result in either direction. Lets you know a meaningful trade has completed — whether profitably or at a loss.
Information included:
- Bot name
- Position size
- Exit reason
- Net P&L (amount and percentage)
- Trade duration
Recommended delivery: Push notification or email
Unusual Market Conditions Detected
Trigger: BitcoinEra’s monitoring system has detected unusual market conditions — high volatility, abnormal spread widening, exchange order book anomalies.
Why it matters: Unusual conditions can affect bot performance. This alert gives you awareness to review your bot’s behavior during the abnormal period.
Information included:
- Exchange affected
- Condition type detected
- Severity assessment
- Bots currently active that may be affected
Recommended delivery: Push notification
Bot Reconnected After Outage
Trigger: A bot that was previously disconnected has successfully re-established its exchange connection.
Why it matters: Tells you the automatic recovery has worked — or gives you awareness that recovery occurred and you should review what happened during the disconnection period.
Information included:
- Bot name
- Duration of disconnection
- Time of reconnection
- Any trades missed or affected during disconnection
Recommended delivery: Email (informational — no immediate action required)
Category 4 — Performance Notifications
These notifications provide regular updates on how your bots are performing. Configure based on how actively you want to monitor performance.
Daily Performance Summary
Trigger: Sent once per day at a time you configure — summarizing the previous day’s trading activity.
Information included:
- Net P&L for the day (per bot and combined)
- Number of trades executed
- Win rate for the day
- Current drawdown level
- Open positions at end of day
Recommended delivery: Email (review at your convenience)
Recommended schedule: 8:00 AM local time — start your day knowing where your bots stand.
Weekly Performance Summary
Trigger: Sent once per week on a day you configure.
Information included:
- Net P&L for the week (per bot and combined)
- Week’s win rate vs historical average
- Current drawdown vs historical maximum drawdown
- Notable trades (largest win, largest loss)
- Market conditions summary
Recommended delivery: Email
Recommended schedule: Monday morning — review last week’s performance to start the new week informed.
Monthly Performance Report
Trigger: Sent on the 1st of each month covering the previous month.
Information included:
- Full monthly performance statistics
- Month-over-month comparison
- Year-to-date performance
- Fee summary
- Detailed trade count and distribution
Recommended delivery: Email with PDF attachment
Performance Milestone Alerts
Trigger: When a bot reaches a predefined performance milestone — configurable thresholds.
Examples:
- Bot reaches 10% cumulative return
- Bot reaches break-even after a drawdown period
- Bot’s monthly return exceeds its historical average
- Bot completes its 100th trade
Why it matters: Positive reinforcement and awareness of meaningful progress milestones. Also useful for tracking when a bot has recovered from a drawdown.
Recommended delivery: Push notification or email (low priority — informational)
Performance Below Threshold Alert
Trigger: A bot’s performance metrics drop below thresholds you configure.
Examples:
- Monthly return below -5%
- Win rate drops below 40% over a rolling 2-week period
- Profit factor drops below 1.2 over a rolling month
Why it matters: Systematic underperformance is more meaningful than a single bad day. These alerts help you identify when a bot is experiencing a sustained difficult period that warrants review.
Recommended delivery: Email (review at your next scheduled check)
Category 5 — Trade Notifications
These are notifications about individual trades. Configuration depends heavily on your bot’s trading frequency — what’s appropriate for a low-frequency trend following bot is completely inappropriate for a high-frequency scalping bot.
Trade Opened
Trigger: A bot opens a new position.
Information included:
- Bot name
- Direction
- Entry price
- Position size
- Stop loss level
- Take profit level
Recommended configuration by strategy:
| Strategy | Recommendation |
|---|---|
| Scalping (100+ trades/day) | Disable — notification fatigue |
| Grid (20–50 trades/day) | Disable or digest only |
| DCA (1–5 trades/week) | Enable — informational |
| Trend Following (1–5 trades/week) | Enable — meaningful event |
| Breakout (1–10 trades/week) | Enable — meaningful event |
Trade Closed
Trigger: A bot closes a position.
Information included:
- Bot name
- Exit reason
- Net P&L (amount and %)
- Trade duration
- Running cumulative P&L
Recommended configuration by strategy: Same as Trade Opened — disable for high-frequency bots, enable for low-frequency bots.
Stop Loss Triggered
Trigger: A trade closed specifically because the stop loss was hit.
Why separate from general Trade Closed: Some users want to know specifically when losses occur — even if they don’t want notification of every trade close.
Recommended delivery: Email or push notification (depending on frequency)
Take Profit Reached
Trigger: A trade closed specifically at the take profit level.
Why separate from general Trade Closed: Positive reinforcement — knowing when profits are being realized.
Recommended delivery: Email or push notification (depending on frequency)
Category 6 — Platform and System Notifications
These notifications relate to the BitcoinEra platform itself — not your specific bots.
Exchange Maintenance Scheduled
Trigger: A supported exchange announces scheduled maintenance that will affect API availability.
Why it matters: Gives you advance notice to decide whether to pause bots before the maintenance window to avoid position management issues during downtime.
Information included:
- Exchange name
- Maintenance window (start and end time)
- Expected impact on bot operation
- Recommended action
Recommended delivery: Email (advance notice — not urgent)
Platform Update Notification
Trigger: BitcoinEra deploys a platform update — particularly updates that may affect bot behavior or configuration.
Recommended delivery: Email
Bot Catalog Updates
Trigger: New bots added to the catalog, or significant updates to bots you’re running.
Why it matters: If a bot you’re running has been updated by its author — you should review the changes before they affect your running configuration.
Recommended delivery: Email
New Knowledge Base Articles
Trigger: New articles published in the knowledge base — particularly in categories relevant to your running strategies.
Recommended delivery: Weekly digest email (optional — disable if you prefer to browse the knowledge base directly)
Building Your Notification Configuration — Recommended Setup
Here is a complete recommended notification configuration for different user types. These are starting points — adjust based on your actual monitoring capacity and preferences.
Beginner Running One Bot (Low-Frequency Strategy)
Goal: Stay informed about important events without complexity.
Channels to set up: Email + Push notifications (mobile app)
Configuration:
| Notification | Push | |
|---|---|---|
| Security alerts (all) | ✅ Immediate | ✅ Immediate |
| Drawdown limit triggered | ✅ Immediate | ✅ Immediate |
| Daily loss limit triggered | ✅ Immediate | ✅ Immediate |
| Bot status error | ✅ Immediate | ✅ Immediate |
| API connection lost | ✅ Immediate | ✅ Immediate |
| Large position opened (>25%) | ❌ | ✅ Immediate |
| Daily performance summary | ✅ 8am | ❌ |
| Trade opened | ✅ | ❌ |
| Trade closed | ✅ | ❌ |
| Weekly performance summary | ✅ Monday | ❌ |
Intermediate User Running Multiple Bots (Mixed Frequency)
Goal: Granular awareness of critical events across all bots without being overwhelmed.
Channels to set up: Email + Push + Telegram
Configuration:
| Notification | Push | Telegram | |
|---|---|---|---|
| Security alerts (all) | ✅ | ✅ | ✅ |
| Drawdown limit triggered | ✅ | ✅ | ✅ |
| Daily loss limit triggered | ✅ | ✅ | ✅ |
| Bot status error | ✅ | ✅ | ✅ |
| API connection lost | ✅ | ✅ | ✅ |
| Large position (>20%) | ❌ | ✅ | ✅ |
| Performance below threshold | ✅ | ❌ | ❌ |
| Trade opened (low-freq bots only) | ✅ | ❌ | ✅ |
| Trade opened (high-freq bots) | ❌ | ❌ | ❌ |
| Daily summary | ✅ 8am | ❌ | ❌ |
| Weekly summary | ✅ Monday | ❌ | ❌ |
| Monthly report | ✅ | ❌ | ❌ |
Advanced User Running Portfolio (High Frequency Included)
Goal: Critical event awareness with zero noise from high-frequency activity.
Channels to set up: Email + Push + Telegram + Webhook (custom dashboard)
Configuration:
| Notification | Push | Telegram | Webhook | |
|---|---|---|---|---|
| Security alerts | ✅ | ✅ | ✅ | ✅ |
| Critical bot alerts (all) | ✅ | ✅ | ✅ | ✅ |
| Large position (>15%) | ❌ | ✅ | ✅ | ✅ |
| Performance below threshold | ✅ | ❌ | ✅ | ✅ |
| All individual trades | ❌ | ❌ | ❌ | ✅ (custom processing) |
| Daily summary | ✅ | ❌ | ✅ | ✅ |
| Weekly summary | ✅ | ❌ | ❌ | ✅ |
| Monthly report | ✅ | ❌ | ❌ | ✅ |
Notification Digest — Batching Non-Critical Alerts
For users running high-frequency bots who still want some individual trade awareness — the Notification Digest feature batches multiple notifications into a single delivery.
How it works: Instead of sending each trade notification immediately — the system collects them over a defined interval and sends a single summary message.
Available intervals:
- Every 15 minutes
- Every hour
- Every 4 hours
- Daily (all trades from the past 24 hours in one summary)
Example digest content:
BitcoinEra Trade Digest — Last Hour
GridMaster X — 8 trades
✅ 6 winners: +$12.40 net
❌ 2 losers: -$3.20 net
Net for period: +$9.20
TrendRider Pro — 1 trade
✅ 1 winner: +$34.70 net
Net for period: +$34.70
Combined net: +$43.90How to configure: Notifications → Trade Notifications → Delivery Mode → Digest → Select interval → Save
Managing Notification Fatigue
Notification fatigue is the state where you’ve received so many notifications that you stop reading them — creating exactly the blind spot you were trying to avoid.
Signs You Have Too Many Notifications
- You routinely dismiss notifications without reading them
- Your email inbox is regularly flooded with bot-related emails
- You feel anxious when your phone buzzes because of how many notifications arrive
- You’ve started marking bot notification emails as read without opening them
Signs You Have Too Few Notifications
- You regularly discover problems only when you actively check the dashboard
- You’ve missed a drawdown limit trigger and only found out hours later
- You don’t know what’s happened with your bots until you log in
Recalibrating Your Notification Setup
If you’re experiencing fatigue — run through this process:
Step 1: Audit your last 30 days of notifications. Categorize each as:
- Critical (I needed to know immediately): Keep on immediate delivery
- Useful (I wanted to know, timing didn’t matter): Move to digest or email
- Noise (I didn’t need to know this): Disable
Step 2: Disable all noise notifications. They add no value and reduce your attention to valuable alerts.
Step 3: Move useful but non-urgent notifications to digest or daily summary format.
Step 4: Verify all critical notifications remain on immediate delivery.
Step 5: Run the new configuration for 2 weeks. Adjust further if needed.
Testing Your Notification Setup
After configuring notifications — always verify they’re actually working before relying on them.
Test Methods
Test Notification Button
Available in Notifications settings for each channel — sends a test message immediately.
How to use: Notifications → [Channel] → Send Test → Verify receipt within expected timeframe
Test every channel you’ve configured — email, push, Telegram, and webhooks.
Verify Email Delivery
Check that notification emails:
- Arrive in your inbox (not spam folder)
- Display correctly on your email client
- Contain the expected information
Spam filter check: Add BitcoinEra’s sending email address to your contacts or allowlist to prevent important notifications from being filtered.
Verify Push Notification Permissions
On your mobile device:
- iOS: Settings → BitcoinEra → Notifications → Allow Notifications
- Android: Settings → Apps → BitcoinEra → Notifications → Enable
Test by sending a test notification and verifying it appears on your lock screen.
Verify Telegram Bot Connection
Send a message to the BitcoinEra Telegram bot — it should respond confirming your connection is active. If it doesn’t respond — go through the connection setup process again.
Troubleshooting Notification Issues
Not Receiving Email Notifications
Check spam folder: Most commonly, notification emails are filtered to spam. Add the sender to your allowlist.
Check email address: Verify the email address in your account settings matches your active email.
Check email server: Some corporate or ISP email servers aggressively filter automated emails. Try a personal email address (Gmail, Outlook) if using a corporate address.
Check notification settings: Verify the specific notification type is enabled in your settings.
Not Receiving Push Notifications
Check app permissions: Verify notification permissions are granted in your phone’s settings.
Check Do Not Disturb: Your phone’s Do Not Disturb or Focus mode may be suppressing notifications.
Check app version: Ensure you’re running the latest version of the BitcoinEra mobile app.
Re-enable push in settings: Notifications → Push → Disable → Re-enable → Test.
Not Receiving Telegram Notifications
Verify bot connection: The BitcoinEra Telegram bot must be active and connected to your account.
Check if bot was blocked: If you accidentally blocked the bot — unblock it in Telegram settings.
Re-connect: Account Settings → Notifications → Telegram → Disconnect → Reconnect.
Webhook Not Delivering
Verify URL is accessible: The webhook URL must be publicly accessible — localhost addresses won’t work.
Check SSL certificate: BitcoinEra requires HTTPS webhooks with valid SSL certificates.
Review server logs: Check your server’s receive logs to see if webhook payloads are arriving but being rejected.
Verify payload format: Test with the BitcoinEra webhook simulator (available in Notifications settings) before going live.
Summary
Here’s everything we covered in this guide:
- The four notification channels — email, push, Telegram, webhook — and when to use each
- Complete reference for all six notification categories — security, critical bot, important bot, performance, trade, and platform alerts
- Recommended configuration for each notification type — when to enable, when to disable, which channel
- Three complete notification setups for different user types — beginner, intermediate, advanced
- The Notification Digest feature — how to batch high-frequency alerts into manageable summaries
- Recognizing and fixing notification fatigue
- Testing your notification setup — how to verify every channel is working
- Troubleshooting guide for when notifications don’t arrive as expected
⚠️ Important: Notifications are a monitoring tool — not a substitute for regular dashboard reviews. Critical events require your active response. Always verify the current state of your bots directly in the dashboard when responding to any critical notification.
