Coingecko
Coingecko lets target-price alerts trigger once or recur
Coingecko lets you choose Once or Recurring when saving a target-price alert in its mobile app. Once covers a single notification when the selected asset reaches your target. Recurring allows further notifications when it reaches that level again. The target determines the price event; the frequency setting determines whether you want repeat alerts. Saving the rule completes setup, while receiving the matching notification confirms delivery of a triggered alert.
Contents
Key takeaway: A one-time alert covers a single target-price event, while a recurring alert keeps the same level relevant for later notifications.
One target with different behavior after the first alert
A one-time alert suits a level you want brought to your attention once. A recurring alert suits a level you want to keep watching after the first notification. Both choices concern the same kind of event: the selected asset reaching a target price. The difference becomes relevant after that initial event.
Recurring price alerts can notify you again when the selected coin reaches your target price. Recurring describes repeated qualifying events, rather than a calendar schedule for market updates. It should not be read as a promise of a notification every minute the price stays near the target.
The price level and its unit
The target price determines what the alert watches. A custom value gives you direct control over that level, while preset intervals offer a shortcut when creating an alert. Read the resulting target before saving it; a percentage shortcut and the final price level describe different parts of setup.
The currency shown beside an amount gives that amount its meaning. Keep that unit consistent when reviewing the saved target and the price notification. A number without its currency does not identify a usable threshold.
Account access and a compatible mobile app
The mobile setup requires an account and supports iOS and Android. Logging in establishes access to alert creation; notification permissions determine whether the phone can present push notifications. These are separate requirements, so successful sign-in alone does not establish that delivery works.
The alert editor includes the target and frequency settings. A coin page provides access through its bell control. Portfolio tracking also provides a route to alerts for individual coins, although recording holdings serves a different purpose from selecting a notification threshold.
A saved target followed through to notification
For a selected coin, successful setup means saving the intended target with the intended frequency. Assume the mobile app runs on your device, you are logged in, and notification permissions allow delivery.
| Stage | Action or event | Observable result | Required condition |
|---|---|---|---|
| Prepare the alert | Open the selected coin's alert control. | The editor presents target and frequency settings. | Account access in a compatible mobile app. |
| Save the rule | Enter the target, choose Once or Recurring, and save. | The alert is created for those settings. | The selected coin and target match your intent. |
| Receive the alert | The tracked price reaches the target. | A matching price notification arrives. | The saved alert applies, and the device permits notifications. |
Saving an alert for the wrong coin or target will not monitor the price event you intended. A saved rule without a received notification confirms creation, not successful delivery. Compare the notification with the selected asset and target to confirm it matches the saved alert.
The waiting period and notification delivery
A saved target has no predictable waiting time because reaching it depends on market movement. Selecting Recurring does not make that event happen sooner. It changes what notifications you want after the first qualifying event.
Phone settings add a separate delivery condition. When an expected notification is missing, distinguish the saved alert configuration from the device's permission to display notifications. Repeatedly entering new targets changes the monitored condition and makes the original issue harder to isolate.
The price shown after a notification
A notification concerns a price event; the screen you open afterward shows information at a later moment. Market movement between those moments can explain a difference between the alert and the displayed price.
That difference alone does not establish that the wrong threshold triggered. Compare the asset, target unit, and notification time before drawing that conclusion.
Automatic alerts and the end of monitoring
Auto Price Alerts can explain notifications you receive without manually saving a target. With the feature and device notifications enabled, selecting a coin from search can enroll it for alerts about major price movements. This is separate from choosing Once or Recurring for a custom target.
Turning off Auto Price Alerts in Settings, under Notification Center, unsubscribes existing automatic alerts and prevents future enrollment. That control belongs to automatic alerts; it should not be treated as the frequency setting for a saved target.
Automatic subscriptions expire after 45 days, and another qualifying search can renew enrollment. That duration applies to Auto Price Alerts, not a stated expiry period for custom recurring targets.
Coingecko questions worth asking
Can NFT floor price alerts also use Once or Recurring?
NFT floor price alerts support both Once and Recurring. Their target concerns the collection's floor price, so the monitored value differs from an individual item's sale price. The alert editor supports target entry in the chain's native token or USD.
Is a paid subscription required for custom price alerts?
Custom price alerts are available as a free mobile app feature. Account access is part of setup, but choosing a one-time or recurring alert does not itself require a paid subscription.
What happens to automatic alerts after I restore phone notification permissions?
Auto Price Alerts remain off after you restore device notification permissions. Disabling phone notifications unsubscribes you from that feature, so restoring permissions alone does not resume it; the Auto Price Alerts setting also needs enabling. This behavior concerns automatic alerts.
Why does a coin with Price Movement Alerts not send a second automatic notification?
Price Movement Alerts take priority over Auto Price Alerts for the same coin. When both apply, the service suppresses the duplicate automatic notification. This rule concerns those two alert categories and does not establish a general deduplication rule for every custom target.
Will an automatic alert work for a preview coin without price data?
A preview coin can enroll in Auto Price Alerts before price data exists. Notifications can begin once that data becomes available. Enrollment therefore does not mean the service already has a price it can monitor.
Last updated -