Go back to Vantage Signals User Manual
The Vantage Signals platform has several types of indicators and each type of indicator has their own configurations and features. Users can use multiple indicators such as tracking Stoch RSI, price, MACD and a crossover all in a single indicator for example.
Trying to assess what is the right indicators to use together and how they should be configured can take a bit of testing. We enable users to back test a single combination, make adjustments and test again as most platform do but we felt this wasn’t enough. We have also built the Algo-Finder, a brute force back testing engine for testing 1000's or even millions of combinations. The Algo-Finder has the same configurations for each indicator as found under individual indicators with the exception that each field can have multiple selections and multiple ranges of values. For example a user could test RSI for order books on a 15m, 1h and 4h candle and include 2.5%, 5% and 10% depth of market values and test for the asset to drop below 30, 20 or 10 and back over to trigger an alert. The Algo finder will generate every possible combination between all the indicators configured and then test each one.
We do not deep dive the Algo-Finder in this article, it is only important to understand that if you can configure an indicator in an algorithm, you can also configure an indicator in an algo-finder, we will briefly touch on this at the end of this article.
Indicators are broken up into 5 major categories
- Metric Indicators | Raw metric comparison with simple moving average
- TA Indicators | Candle analysis using an array of Technical Indicators
- Crossover Indicators | Track crossovers on an array of like metrics and TA outputs
- Webhook Indicators | Import any webhook as an indicator such as Trading View Webhook alerts
- Large Order Alerts (LOA)
There are an array of raw metrics that can be alerted on with basic metric indicators. Users can look for absolute values to cross thresholds or they can look for a % change in value over a period of time. The following metrics can be tested using metric indicators.
- (Combined) Order books
- % of sell volume <$100
- % of sell volume >$100 but < $50k
- % of sell volume >$50k
- % of buy volume <$100
- % of buy volume >$100 but < $50k
- % of buy volume >$50k
- % of 24hr sell volume witnessed in the last hour
- % of 24hr sell volume witnessed more than an hour ago, less than 6 hours ago
- % of 24hr sell volume witnessed more than 6 hours ago, less than 24 hours ago
- (Combined) Bids
- (Combined) Asks
- xAsks (Executed Asks/Buys volume)
- xBids (Executed Bids/Sell volume)
- Market Depth Ratio (MDR)
- Order Flow Ratio (OFR)
- Price Relative Index (PRI / Global or Sector Market Dominance)
All of the Metric Indicators are configured with the same fashion. There are some exceptions when configuring order book related metrics where as users must specify a market depth.Below we provide a capture of the standard interface for regular metric indicators. At the time of this publication, we do not have an explainer function for this configuration.
- Select what metric you would like to use as an indicator, we use combined bids in the example
- Configure an operater: <,>,<=,=> options let you specify if you want to see these metrics go up or down
- Value specified, this can either be an absolute value or a % change. If the evaluation type is set to absolute value then we would signal if the actual value of this metric goes above or below a certain number. If the evaluation type is Percent Change, then we will signal if the value changes this percent within the timeframe specified.
- Evalutation Type: Choose from absolute value or percent change, functions as outlined above
- Trend Length: This is only vidible if users select the Percent change evaluation type. The trend-length is specified in minutes and represents how far back in the past we should compare the current value to see if we have exceeded the threshold value specified. For example if this is configured for 60 minutes and with a value of 10, and an operator of =>, this indicaor would require the combined bids to increase by 10% compared to its value 1 hour prior to flag an alert.
- The average field allows users to specify in hours, the averaging cycle they want to use for this metric, this is a SMA. Many values would not use averaging however all order book and order flow data is very volatile and needs some type of smoothing to be able to effectivley signal on them. We recommend 1-24 hours averaging when using order book and order flow metrics.
- Market depth: This field is only present when selecting an order book based metric such as asks/bids, orderbooks and MDR. Users must specify what depth of market they want to evaluate, 1%, 2.5%, 5%, 10% or 100%. To see these values charted, see https://coinmarketflow.com
We provide an array of TA indicators which users have an array of options on how they want to configure them with the ability to run multiple options and spreads of values through our Algo-Finder brute force back testing engine. Not only can users change an array of configurations for how the TA Indicator calulates and tests each metric, users can base these indicators on price, volume, orderbooks, orderflow and more. We enable the deep dive of metrics beyond price in a way never explored before. We will continue to add additional indicators over time. Here is the break down of the indicators we offer by type as well as links to helpful videos that explain the indicaors and how to configure them.
- Bollinger Bands
- Parabolic SAR
- Relative Strtength Index (RSI)
- Stochastic RSI (Stoch)
- Moving Average Convergence & Divergence (MACD)
- Money Flow Index (MFI)
- Average Directional Movement Index (ADX)
- On Balance Volume (OBV)
- Library of Candle Patterns
While some of these indicators are configured similarly, most of them have their own exceptions. Instead of filling this section up with a wall of text for each indicator, we provide short explainer videos for configuring each one. In our videos, we also show the indicator on the charts and further explain its usage in conjunction to guidance on how to configure the indicators. Below is a list of currently available explainer videos for TA Indicators.
- TA Indicator | MACD
- TA Indicator | Money Flow Index (MFI)
- Parabolic SAR (PSAR)
- Relative Strength Index (RSI)
- Stochastic RSI (Stoch)
- Candle Patterns
- TA Crossover | Stoch fast/slow
- Aroon | High/Low
- MFI MFI/MFI
Webhook indicators enable users to receive a webhook from any source and use it as an indicator. If the webhook indicator is the only indicator in your Algo or Strategy then once we receive an alert from your webhook, the algo will fire off and we will start tracking its performance. In the case we are using the webhook indicator alongside other indicators, an algo will require all the indicators in the algorithm to pass before sending a flag to take action and tracking performance. The most common integration is Tradign View Alerts, we will focus on using Trading View Webhooks as indicators in this tutorial, however, our webhooks are not limited to receiving inputs from Tradingview Alone, any platform sending webhooks can be used.
The process to use webhook indicators is to configure an inbound web hook channel any inbound webhooks you would like to receive and then assign that webhook channel to an indicator, a simple two step process.
Creating an inbound webhook channel
- Select channels
- Select Webhooks
- Create a new inbound webhook
- Copy the URL provided by Vantage Signals, this is what you will paste on the sending side so they know where to send the webhooks
Once you have generate a webhook adress, we can easily use it to configure Trading View or other Webhook enabled apps.
- Choose one time or re-occuring depending on if you want this alert to trigger every time the condition is met or only the first time
- Select Webhook URL and paste the Webhook URL provided from the Vantage Signals webhook channel you created prior
- Enter a distinct message for this alert, we will look for this message when we receive the alert and signal if we see this specific message. This enables us to use one webhook for all the alerts coming from a single platform.
After the webhook sender is configured, we can now configure an indicator to receive this webhook.
- Open an existing algorithm or create a new one
- Add an indicator, choose webhook indicator
- Select the Webhook Channel to monitor, you created this in the first step
- Enter a filter to lok for, this should match the words you are sending in the alert you are looking for.
- Enter an expiration. This is only needed if you have multiple indicators defined. The expiration/keepalive says that once we receive an alert on this webhook, we should keep it active for this long to give the other indicators this much time to also match their criteria and fire off. Without this, a webhook alert would come in and unless all your other indicators also matched at that exact moment, the algo would not fire.
- Webhook indicators are not available in the Algo-Finder
- Single back testing in an algo with prior received webhooks is a planned future feature