Coinmarketcap Alerts are price thresholds with push delivery

What does a saved price threshold cost?

A standard price threshold belongs to the app's free core feature set and adds no per-alert fee. Creating one threshold initiates zero trades, zero blockchain transactions, and zero exchange commissions. The rule only watches market data and requests a notification after its condition is observed.

Two cost models matter here. Native push alerts use the mobile app, an internet connection, and the phone's notification service. Custom automation built with the Crypto API adds separate infrastructure costs: the developer must request data, evaluate rules, store state, and deliver messages. API subscription terms and call allowances belong to that separate workflow. They do not turn a saved mobile threshold into an on-chain action.

An alert also locks no collateral and approves no token spending. Gas becomes relevant only after the user separately submits a transaction on Ethereum, Solana, BNB Smart Chain, or another network. Once alerting costs are separated from execution costs, the threshold itself is straightforward to plan.

How should upside and downside levels be spaced?

An upside or downside threshold should represent a decision boundary, not every small candle. Each rule has one quoted level and one of two logical directions: the market approaches it from below or from above. A paired setup uses two targets around the reference price, giving separate notice of strength and weakness.

The arithmetic is fixed. On a unit-free reference value of 100, a level 10% higher is 110 and a level 10% lower is 90. Those calculations use multipliers of 1.10 and 0.90. This symmetric method keeps the percentage distance clear, although the absolute distances look different once a live asset moves away from the original reference.

Tight spacing creates repeated noise around a choppy boundary. Wider spacing reduces notifications but reports only larger moves. Match the interval to the action attached to it: checking liquidity, reviewing exposure, or comparing the move with Bitcoin. Reset stale targets after a redenomination, contract migration, or material change in the asset's trading range.

How does a threshold become a push notification?

A push price alert follows four visible stages. A trading venue publishes a market-pair price, the aggregator imports market data, the saved rule detects a crossing, and the mobile push system presents the message. Coinmarketcap Alerts therefore reflect the first qualifying observation processed by this chain, not every trade printed across every venue.

The target is evaluated against a quoted asset price. It is not attached to an exchange order book, a wallet balance, or a blockchain block. A fast move might cross the level, reverse, and disappear before the next aggregated observation. A lasting crossing is easier to capture because it remains visible through more than one data collection cycle.

Push delivery adds another queue after the rule fires. Apple or Google carries the message to the device, then iOS or Android applies its notification settings. A locked screen, Focus mode, weak connection, or disabled category changes presentation without changing the stored threshold. The next check is the asset identity behind that rule. The related steps are listed in Using Coinmarketcap.

Which asset does the threshold really follow?

Asset identity determines whether the alert watches the intended market. BTC identifies Bitcoin and ETH identifies Ether, while SOL identifies Solana's native asset. Token tickers need more context. Tether's USDT exists on multiple networks, including ERC-20 on Ethereum and TRC-20 on Tron, so a DEX-pair subscription also needs the correct chain and pair.

An Ethereum address contains 20 bytes, displayed as 40 hexadecimal characters after the 0x prefix. The full text therefore occupies 42 characters. Ethereum mainnet uses chain ID 1, BNB Smart Chain uses 56, and Polygon PoS uses 137. Those identifiers separate contracts that share a ticker. Solana accounts use 32-byte public keys represented in base58, which requires a different address check.

Display precision matters at small thresholds. Bitcoin supports 8 decimal places, and one satoshi equals 0.00000001 BTC. Ether uses 18 decimal places, with 1 ETH equal to 10 ¹⁸ wei. These units describe assets, not alert speed. Bitcoin's 10-minute block target and Ethereum's 12-second slot duration do not set the timing of an aggregated price notification.

Which notification type matches the market event?

Four market-facing notification modes cover different events. A custom price threshold watches a numeric target. Watchlist movement notices use platform-defined significant changes, while Bitcoin and Ether milestone notices focus on two named assets. DEX pair trade alerts follow significant trades on pairs the user has subscribed to.

These modes are not interchangeable. A watchlist is useful for broad monitoring, while a custom threshold expresses an exact boundary. DEX trade alerts concern pair activity rather than the aggregate asset price. CMC AI adds AI Alerts for contextual market updates, but that feature answers a different need from a fixed numeric target. Select the mode by trigger, dependency, and asset scope.

Why can a push arrive after the market has reversed?

Market-data cadence and push delivery latency create the gap. The platform queries exchanges for their latest market data every minute, then applies data-cleaning and verification algorithms. A move that begins and ends inside one collection interval might never become a durable crossing in the aggregate. A move observed near the end of an interval still waits for evaluation and mobile delivery.

The displayed cryptoasset price is a volume-weighted average of reported market-pair prices. Higher-volume markets exert more influence. Bitcoin prices shown by Binance, Coinbase, and Kraken therefore do not need to match the aggregate at the same instant. Selected market pairs also leave the calculation when their prices fail the platform's data-quality checks.

After the rule fires, network routing and operating-system queues add time. No alert target reserves the crossed price during that interval. Opening an exchange after the notification shows the venue's latest executable market, including its spread and order-book depth. That distinction matters most during short, sharp moves.

Which phone settings control delivery?

Mobile notification settings operate at two permission layers. The in-app category toggle authorizes the chosen alert type, while iOS or Android controls whether the app displays banners, badges, sounds, and lock-screen notices. Coinmarketcap Alerts need both layers enabled. Changing only one leaves an incomplete delivery path.

The supported mobile baseline starts at Android 5.0 or later and iOS 11.0 or later. Android 13 added a runtime notification permission that the user must grant. iOS 15 introduced Focus modes, which filter or postpone selected notifications. A compatible operating system therefore does not prove that every alert category is currently allowed.

Check the saved rule first, then the in-app notification category, followed by the operating-system permission. Review Focus, notification summaries, silent mode, and Android battery controls last. A visible in-app alert with no banner points to the phone layer. No recorded threshold event points back toward the rule, asset, or market-data path.

When does TradingView or an exchange alert fit better?

TradingView fits chart-based conditions that extend beyond one price boundary. Its alerts support indicators, drawings, strategies, chart patterns, and Pine Script logic. Coinmarketcap Alerts fit simpler monitoring of an aggregated cryptoasset price. CoinGecko offers another target-price workflow, including one-time and recurring alert choices in its mobile experience.

Venue-specific monitoring is better when execution occurs on a single exchange. A Coinbase custom alert follows its supported market workflow, while prices on Binance or Kraken expose the venue where the eventual order would be placed. A conditional order goes further by submitting execution instructions, although fills still reflect liquidity, spread, and order conditions. A push alert never provides that function.

Chainlink Automation serves a different edge case: programmed smart contracts execute supported on-chain upkeep conditions. That route requires contract logic, network fees, and explicit on-chain state. It is excessive for a phone reminder but relevant when the required outcome is automated protocol activity.

The service began as a crypto market-data aggregator in 2013, and that background still shapes its alert workflow. It observes markets across venues and reports a condition. Choose it for broad awareness, TradingView for technical logic, an exchange for venue-level context, and on-chain automation only when code must act without a person opening the notification.