Live Alerts is where pinned callsigns, alert history, and notification settings come together. Tapping a push notification from Club Log Mobile opens this screen.
Pinned callsigns
The Pinned section at the top holds up to ten bookmarked callsigns for your active callsign. Tap + to add one; the button is disabled when the list is full. Adding a pin also turns Activity alerts on for that station (with Needed slots only enabled by default). The callsign must belong to a Club Log account (for example an active DXpedition).
Each card shows the callsign and, when that station has been active on the air recently, a LIVE badge. Tap LIVE to open the livestream if one is available, or to read a short note when the station is logging but not streaming. Log Inspector opens your logbook filtered to QSOs with that exact callsign. DX Cluster opens the cluster feed filtered to that callsign.
Two kinds of alert on each pin
Pinned cards offer two independent alert types, separated by a divider:
Activity alerts (on-air icon) notify you when that callsign is active — a DX cluster spot, an RBN/Skimmer report, or a QSO uploaded to their Club Log log. Turn this on to “wake me when they show up.” When it is enabled, two optional filters appear underneath (indented, in secondary text):
- Needed slots only — only fire when the activity matches a band or mode you still need for that entity. On by default when you enable activity alerts or add a new pin.
- Only QSOs with my CQ Zone — for real QSO uploads only, further limit alerts to contacts where the other party is in your CQ zone. Off by default. When both filters are on, a QSO must satisfy both.
You’re in the log alerts (bell icon) notify you when your callsign appears in their log — the classic expedition-watch alert. This is separate from activity alerts: you can enable either, both, or neither.
Pinning, activity alerts, and in-log alerts are independent. You can pin without either alert, enable activity from DX Cluster or Live Bands without opening Live Alerts, or turn on in-log alerts from Expeditions without pinning (though enabling the watch there usually pins the callsign too when space allows). Turning in-log alerts off on a pin removes that watch only; activity alerts and the pin itself stay as they were. Use the ⋯ menu or swipe the card to Unpin, which removes the pin and both alert types for that callsign.
Each alert type is capped at ten per active callsign. If the list is full when you add one, the app may remove the oldest entry of that type and tell you what was dropped; you may still see a note if a pin could not be added because the pin list is full.
Recent Alerts
Recent Alerts lists push notifications the app has recorded, newest first. Rows show needed-entity alerts, milestone alerts, activity alerts (for example “3B7A is active” or “3B7A active on 20m CW”), and in-log alerts (“You worked …!”). Each row may offer actions such as View in DX Cluster, View in Log Search, or Check Need, depending on the alert type. Swipe a row to delete it. Pull down to refresh. If you have no history yet, the screen points you to the gear icon for settings.
If you have both a blanket New slots alert (in Alert Settings) and an activity alert on the same callsign, you receive only the activity alert for that event - the more specific pin wins.
Alert Settings
The gear icon opens Alert Settings. Tap Done when finished. Milestone alerts notify you when a QSO is newly confirmed or verified, or when you work a new band or entity for the first time. Under Blanket Alerts, New DXCCs fires when a spot matches an entity you have never worked on any band, and New slots fires when a spot matches a new band or mode on an entity you already have; footer text on that section explains how busy those may be given your confirmed entity count. Specific alerts lists per-entity watches (with optional band and mode); swipe to remove, or tap + to add one by choosing entity, band, and mode. Per-pinned-callsign activity alerts are not configured here - use the pin cards above. The trash icon clears all history after confirmation.
Connection and permissions
Pinned cards and history need a network connection to load; without one you see Device offline or an error. Delivering pushes also requires notification permission for Club Log Mobile in iOS Settings. Pins, watches, and history all follow the active callsign in Settings.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article