FAQ
Answers to the questions SignalWise customers ask most.
Ask an AI
Can't find your answer? On the home page, copy the ready-made prompt and paste it into ChatGPT, Claude, Gemini or Copilot. It includes this whole documentation.
Alerts
The most common reasons:
- The move was below the threshold. A sharp move needs at least 5% (1.5% for forex and commodities) and a move larger than 2 standard deviations, calculated on the last 20 closing prices. On a volatile asset, a 6–8% move can be normal. See How alerts are triggered.
- The move built up over several days. Each rule looks at one trading day. A drop of 3% a day for four days does not trigger a sharp-move alert.
- It happened outside regular trading hours. There are no pre-market or after-hours alerts.
- The same alert type already fired today for this asset.
- The asset or alert type is not in your feed. Check your universe and filters.
Still unsure? Contact support with the asset, date and time.
Each alert type is sent at most once per asset per trading day, but different types are independent. One strong move can trigger a Gap Down at the open, then a Sharp Move Down, then a 50-Day Low. You can exclude some types, or keep only the first alert per asset per day on your side.
13 events: sharp moves up and down, gaps up and down, 52-week and 50-day highs and lows, high and low range breaks, MACD bullish crossover, death cross and RSI overbought. See Alert types.
A sharp move compares the price during the session with yesterday's close. A gap compares today's opening price with yesterday's close. Both need at least 5% (stocks) and a move larger than 2 standard deviations.
The last 50 trading days, about 2.5 months. A High Range Break fires when the lowest price of the day stays above the 50-day high plus a margin of 0.1 standard deviation, so touching the 50-day high is not enough.
Yes. Thresholds can be adjusted per asset class (for example 3% instead of 5% for crypto). They cannot be set for a single asset.
Yes. Any alert type can be excluded (for example all technical alerts), and asset types can be removed (for example ETFs). See Filters & configuration.
RSI Overbought fires when the 14-day RSI has stayed above 70 for 3 consecutive trading days, whatever the direction of that day's move. It is a caution signal (the asset may be overextended), not a buy signal.
No. Assets are skipped on the day of a split or reverse split, so a split alone never triggers a price alert.
A gap is a jump at the market open. Crypto and forex trade continuously, so they have no open and no gap alerts. They still get sharp-move alerts.
Not today. Alerts are generated during regular trading hours only. Crypto and forex are monitored 24/7.
It depends on your universe, the alert types and market conditions: from a few per day on a short list of assets to hundreds per day on a broad universe. Your account manager can run a volume analysis on your universe before you go live.
In near real time. Prices are monitored continuously during trading hours. When your feed includes reasoning, it can add a short delay while the reasoning is generated.
Alerts are triggered on the intraday price, compared with the previous close. The price can move further, or come back, after the alert. The close of the day can therefore differ from the % in the alert.
When a Japanese stock is locked at limit-up or limit-down with no trades, the market data contains no valid trade price, so no alert can be created. This is a known limitation, under investigation.
Not as standalone alerts today. These events appear in the reasoning when they explain a price move. News-based alerts are in development.
Reasoning
SignalWise attaches a reason only when it finds recent, reliable news that explains the move and passes all checks. Otherwise the alert is sent without reasoning, rather than with a weak or invented one. This is expected. See Why some alerts have no reasoning.
Yes. Your feed can be filtered to drop alerts without reasoning. You get fewer alerts, all of them explained.
SignalWise searches vetted news sources in a short window before the alert, uses an AI model to identify the drivers, checks each reason (fact date, right company, right direction, quality, relevancy) and translates it. See How reasoning is generated.
Every reason must cite a fact found in the news search. Automatic checks remove reasons that are about another company, in the wrong direction, too old, undated, generic or weakly linked to the move. Each change to the method is tested on a reference set of alerts before release.
Each reason is checked against the date of the fact it cites, not the date of the article. Facts outside the alert's time window, and undated facts, are removed. If you see an old fact in a recent alert, send us the uniqueEventId.
Sometimes news about a peer or a supplier legitimately moves a stock (sector read-across). Such a reason is kept only when it explains the link to your asset. If the company is simply wrong (for example a similar name), report the uniqueEventId to support.
Each reason is checked to match the direction of the alert. Note that the sentiment of a news item can differ from the price reaction: bad news for an industry can push some stocks up. The reason must then explain why.
It scores how strongly a reason explains the move, from 1 (strongest) to 5 (weakest). Reasons scored 4 and 5 are not delivered by default. Reasons are sorted from the most to the least relevant.
Up to 3, each in a different category, sorted by relevancy.
A curated list of trusted financial news sources in several languages, including leading Japanese financial media for Japanese assets. Crowd-sourced forecast sites and quote pages are excluded. Sources can be added or removed on request, after review.
Reasons are written in English, then translated with finance-specific rules (meaning over literal words, same sentiment, names and tickers unchanged). Japanese and Korean have dedicated style rules. Wording can differ slightly between languages, but the meaning stays the same.
Earnings reasons use the report date and reported or consensus figures. Reasons are being improved so they always say whether results beat or missed expectations; reasons with figures only will be dropped.
There is no dedicated filter today. Contact your account manager if this matters for your users.
Personalization
Yes, with the Personalized plan. You send each user's holdings, and SignalWise sends one message per user who holds or watches the asset. See Personalization.
Check that: the user's portfolio was sent before the alert fired; the user has products including 1; the asset was resolved (unknown ISINs or tickers are skipped silently); and the asset is in your universe.
Personalized alerts are matched to the listing the user holds. If you still see this, send us the userId and uniqueEventId.
A full snapshot of all users once a day, plus individual updates whenever a user changes their holdings.
Integration and data
Kafka for real-time notifications (push). REST API to display alerts on screen (pull). See Integration options.
Bridgewise can forward the stream to AWS SQS, AWS EventBridge, Google Cloud Pub/Sub or your own API. See Cloud connectors.
These are Kafka transaction control records, not alerts. Skip records whose key is 4 bytes and value is 6 bytes, and use a client that supports read_committed. See Kafka best practices.
See Alert message. The schema registered in the Schema Registry for your topic is the source of truth.
eventImportanceLevel is the priority of the alert type, from 1 (high) to 3 (low); for example a 52-week high ranks above a 50-day high. If your feed marks your key assets, an asset importance of 0 means one of your key assets. relevancy_score is the strength of a reason (1 to 5).
Names and texts can be longer than in the examples. Avoid tight length limits on text fields.
logoUrl is a signed, temporary URL. Download and cache the image if you need it longer.
Yes, on request: alerts and reasoning for a past period, as a JSON Lines file over SFTP.
Yes. Staging topics start with stage-, and a separate test topic can be created for you.
Yes, through the Bridgewise Companies API, using the companyId from the alert.
Yes, per feed: short titles with emoji, no exclamation marks, price shown or hidden, and event-specific text when there is no reasoning.
Bridgewise does not see what your users do after you send the notification. Share your click and conversion data with us and we can help analyze it.
Coverage and languages
Stocks, ETFs, crypto, forex, commodities, futures and indices on major exchanges in the US, Europe, Japan, Hong Kong, Israel and Latin America. See Assets & markets.
Yes. Coverage is reviewed every quarter, and individual additions are usually done within about a month, once market data is available.
Alert text in English, Japanese, Korean, French, Spanish, Portuguese, Arabic, Hebrew, Chinese and German, with more on request. Reasoning in more than 30 languages. See Languages.
Alerts follow the instrument's quote currency. Alerts on pairs or listings quoted in your currency (for example BTC/JPY) can be set up on request.
Compliance
No. Alerts and reasoning are general market information, not personal advice or a recommendation. You display them within your own regulatory framework. See Compliance & methodology.
Yes. Compliance & methodology summarizes it, and your account manager can provide a detailed pack.