Coinmarketcap
Reference guides
Coinmarketcap alerts are price thresholds without trade execution
Coinmarketcap alerts are mobile notifications that fire when the service's reference price reaches a selected target. Each saved threshold converts one market level into a prompt for attention without placing a limit order, signing a wallet transaction, or reserving liquidity. The feature suits monitoring Bitcoin, Ethereum, and other listed assets while leaving the venue, order type, position size, and timing of any later action open.
They are mobile price notifications that flag when a tracked asset reaches a chosen threshold.
Coinmarketcap threshold alerts versus Binance stop-limit orders
Equally, Coinmarketcap alerts and Binance stop-limit orders react to price levels through different mechanisms. The alert sends information; the stop-limit instruction creates an order path inside a custodial exchange account.
One saved alert produces 1 notification condition, with 0 order quantity, 0 wallet signatures, and 0 blockchain gas charges. A Binance stop-limit order contains 2 price fields - the stop that activates it and the limit used for the resulting order-book instruction - plus an amount. Reaching the stop activates the limit order, which still requires a matching counterparty before it fills.
| Mechanism | What the threshold starts | Custody or control model |
|---|---|---|
| Coinmarketcap price alert | Mobile notification when the customized target is met | User controls any assets; the alert creates no order |
| Binance stop-limit | Limit order after the stop price is reached | Exchange account holds funds and routes the order |
| Coinbase custom alert | Mobile notification at the selected target | User controls funds; the alert itself creates no order |
| TradingView price alert | Notification from a chart condition | Analysis layer; execution requires a separate connection or action |
Coinbase custom alerts and TradingView chart alerts also function as analytical prompts unless the user separately enters an execution workflow. A notification threshold fits a process that checks spread, liquidity, news, or portfolio exposure before selecting a venue. An exchange order belongs to a different process in which side, size, price constraint, and available balance are already defined. The alert itself neither moves BTC nor changes an ERC-20 allowance.
Set the asset, quote unit, and response before saving
A Coinmarketcap price alert is well-defined when 3 inputs align: the asset listing, the quote unit, and the target. The setup also needs 1 intended response, because the product stores a market level rather than a complete decision tree. The related figures are collected in Coinmarketcap watchlist.
Begin on the intended asset listing in the mobile app, open its alert control, select the preferred fiat or crypto quote unit, enter the absolute target, and save the condition. Confirm that the alert appears among the active conditions. The account-wide delivery control sits under the avatar, Settings, and Notifications, where alert categories are enabled or disabled separately from the asset-level target.
Quote choice changes the meaning of the number. A Bitcoin target expressed in USD tracks a dollar reference, while a BTC-denominated target for Ethereum tracks the ETH/BTC ratio. Tether USDt (USDT) is also distinct from a bank-dollar quote, even when the two values trade close together. A two-sided band requires 2 saved thresholds - an upper condition and a lower condition - rather than one number carrying two interpretations.
Why the Coinmarketcap price can differ from Coinbase or Uniswap
The Coinmarketcap reference price is an aggregate across reported market pairs, while Coinbase spot prices and Uniswap pool quotes describe particular venues. A target is evaluated against the service's aggregate, not the last trade on one exchange or the marginal swap quote from one liquidity pool.
The published market-data process queries exchanges every 1 minute and calculates a cryptoasset price as a volume-weighted average of eligible market-pair prices. Consequently, a brief divergence between BTC/USD on Coinbase and BTC/USDT on Binance does not always pull the aggregate through the same level. Volume gives more influential pairs greater weight, while data-cleaning rules remove prices that do not represent the broader market.
Uniswap v3 is narrower still because a quote reads the state of one pool. Its Ethereum deployment includes fee tiers of 0.01%, 0.05%, 0.30%, and 1%, so separate pools can show different executable quotes and liquidity. The Coinmarketcap methodology marks a non-indicative excluded pair with 1 asterisk and an algorithmically detected outlier with 3 asterisks. Those filters explain why an isolated market print need not become the reference price that activates a notification.
Three notification gates on iOS and Android
Mobile delivery for Coinmarketcap alerts passes through 3 gates: the saved target, the Coinmarketcap notification-category setting, and the operating system's app permission. All 3 must remain enabled for an evaluated condition to become a visible push notification.
The published compatibility floor is Android 5.0 or later and iOS 11.0 or later. Device controls add another presentation layer: Android 8.0 introduced notification channels, while iOS 15 introduced Focus and Scheduled Summary controls that can silence or defer banners. An alert can therefore remain active even when nothing appears on the lock screen. Checking the notification center distinguishes muted presentation from an absent banner, and reopening the active-alert view confirms whether the saved condition still exists.
From a market update to the lock-screen banner
Related details are covered in Using Coinmarketcap. A Coinmarketcap price notification moves through 4 stages: market-data ingestion, threshold evaluation, push queuing, and operating-system presentation. Those stages explain why the chart time and the moment a banner appears need not match exactly.
Crypto markets operate 24 hours per day, 7 days per week, while phones deliberately restrict background activity, network access, and interruptions. Retail price alerts have no published fixed delivery-time service level. The relevant timing inputs are the latest aggregate update, the threshold evaluator, the push queue, the phone's connectivity, and the operating system's delivery policy.
A short movement on one venue can disappear inside the aggregate without meeting the saved condition. If the operating system delivers a queued message after the phone reconnects, that message describes an earlier threshold event rather than a fresh execution quote. Opening the asset view reveals the newer reference price before any separate trading decision is made.
Designing two-sided bands and three-rung ladders
A two-sided Coinmarketcap alert band uses 2 independent thresholds: one above a reference level and one below it. A 3-rung ladder uses 3 alerts, with each notification tied to a distinct observation or review step. One target should represent one condition so that its meaning remains clear when it appears without the surrounding chart.
An upper notification might prompt a review of momentum and liquidity, while a lower notification can prompt a reassessment of the original premise. Percentage-based intent must first be translated into an absolute target in the selected quote unit; that saved number does not float with a changing baseline. CMC AI Alerts are a separate feature that surfaces contextual updates, while TradingView supports indicator-driven conditions such as Relative Strength Index logic. Neither changes the execution boundary of a simple price notification.
Ticker collisions, wrapped assets, and chain migrations
Asset identity is the final control in Coinmarketcap alert maintenance because a ticker is display text rather than a unique on-chain identifier. Bitcoin (BTC), Wrapped Bitcoin (WBTC), and other tokenized representations belong to different listings and mechanisms even when their market values remain closely related.
Ethereum mainnet uses chain ID 1, while BNB Smart Chain uses chain ID 56. Both networks use 20-byte Ethereum Virtual Machine addresses, displayed as a 0x prefix followed by 40 hexadecimal characters; a Solana token mint identifies a 32-byte public key. These figures help distinguish ERC-20, BEP-20, and Solana assets when duplicate symbols or similarly named listings appear.
On-chain decimal precision also differs from the alert's quote precision. Tether USDt uses 6 decimals in its Ethereum ERC-20 contract, while WBTC uses 8, yet neither setting determines the aggregate price target entered in the app. After a contract migration, ticker change, or wrapped-asset switch, review the selected listing, quote unit, and saved threshold. Recreate the condition when the updated listing no longer represents the asset originally intended.
Coinmarketcap alerts: reader questions
Does setting a Coinmarketcap price threshold incur gas or exchange fees?
Setting a Coinmarketcap price threshold requires no blockchain gas payment and creates no exchange fee. Saving the condition does not broadcast a transaction, approve an ERC-20 token, or reserve an exchange balance. Gas, trading fees, and slippage enter only if you later submit a separate Ethereum transaction, Uniswap swap, or exchange order after reading the notification.
Could a Coinmarketcap alert close a leveraged position before liquidation?
A Coinmarketcap alert cannot close a leveraged position or change its collateral. A derivatives venue's liquidation engine monitors margin within that venue, whereas the alert produces a mobile notification based on an external reference price. Delivery and manual response introduce additional time, so liquidation protection requires controls provided by the venue rather than an informational push message.
Are CMC AI Alerts the same as custom price thresholds?
CMC AI Alerts and custom price thresholds are separate notification mechanisms. A custom threshold watches for a selected reference price, while CMC AI Alerts surface contextual, AI-generated market updates within the CMC AI experience. An AI update is not a fixed-price order condition, and neither feature independently submits an exchange order or signs an on-chain transaction.
Are DEX pair trade alerts identical to asset price alerts?
DEX pair trade alerts are separate from asset-level price thresholds. The DEX setting concerns significant trades on subscribed decentralized-exchange pairs, while a custom price alert compares an asset's aggregated Coinmarketcap reference price with a target. A trade in one Uniswap or PancakeSwap pool therefore represents different input from a threshold applied to the broader asset listing.
Can a price threshold monitor transfers to an ERC-20 address?
A price threshold does not monitor transfers, balances, or approvals at an ERC-20 address. It evaluates market-price data associated with a listed asset. Address activity requires an on-chain monitoring tool such as an Ethereum block explorer or wallet notification service, because transfers are blockchain events rather than movements in an aggregated market reference price.
Will stablecoin thresholds catch every USDT or USDC pool deviation?
Stablecoin thresholds do not capture every deviation inside every USDT or USDC pool. The alert follows an aggregated asset price, so a temporary imbalance in one Uniswap, Curve, or PancakeSwap pool might not move that reference through the target. Monitoring a particular pool requires pair-specific data; the aggregate alert is better suited to a broader market-level deviation.
Should a watchlist movement notice replace a fixed target alert?
A watchlist movement notice should not replace a fixed target when an exact level matters. Watchlist notifications flag significant increases or decreases under the service's movement logic, whereas a custom alert stores the absolute threshold selected by the user. The two can coexist: one detects broader movement, and the other marks a predetermined reference level without creating a trade.
Updated 26 July 2026