Welcome to ProfitView, enabling automated indicator & script based trading on TradingView

— using the exchange of your choice!

This page will give you an overview of the steps required and guide you through the setup process, getting you started as quickly as possible.

Note: To be able to communicate with the respective Exchange that you want to use, you need to grant ProfitView the permission to connect to the Exchange's website — do that by simply clicking on the corresponding ON button below and confirming the following permission prompt!

➔ continue to Setup: Unlock PRO features

➔ continue to Setup: ProfitView Alerts

Note: For your studies on TradingView to be able to place and cancel orders etc. on an Exchange through ProfitView you have to create an alert on TradingView with either the name of a ➔ PV Alert or some of the following commands in its Message section!

➔ End of this page for examples    ➔ Click here for Unified Alerts    ➔ See IF / ELSE    ➔ See Custom Plots / Vars

ex=bitmex-testnet sym=xbtusd
acc=bitmex:acc1,acc2,acc3

Note: Any of the parameters a (Account), e (Exchange), s (Symbol), p (Price), q (Quantity), l (Leverage), d (Disabled), retries, timeout, minb (min balance), maxb (max balance), bc (Balance Cached), pc (Price Cached), jd (Jump Delay), err (Error Handling), pr (Price Reference), qr (Quantity Reference), y (Yield), pm (Position Mode), sv (Save Order) can be specified in a line by themselfes to set new defaults to be used for the following commands in the same alert, overwriting previous defaults or prefilled values coming from TradingView!

Unified Alerts / Placeholders

Unified alerts are supported since version 1.2.21 – this feature allows you to define one single ➔ PV Alert for both long and short (or buy and sell) conditions!

This is made possible by using the following placeholders in your syntax instead of specifying long/short or +/- for price offsets directly.
These placeholders are then resolved to the correct values before the syntax is run when triggered (pre-processor).
Note: They can also be used in notifications and jump marks!

The direction of long/short or buy/sell for the placeholders is determined in the following way:

• If OHLCV data is present in the TradingView alert message and contains a side parameter – useful for single alert entries, see Custom Plots / Vars below! (since 1.2.90)
• If the Detect Side checkbox is enabled for the triggered ➔ PV Alert or the OHLCV side parameter is set to auto, the first occurence of exchange/symbol/account in the triggered syntax (or as fallback the chart symbol that triggered the alert or configured defaults) will be used to check for an open position and use its side (since 1.2.90)
• Checking the name that triggered the alert for occurrences of long, short, buy or sell (case insensitive) and afterwards also for any of the letters L, S or B

For example: Create one ➔ PV Alert with the name XBT1H LONG, XBT1H SHORT and then create two alert conditions in TradingView, with the one for long entries having XBT1H LONG as message text and the other one for short entries with XBT1H SHORT as message text.

Important: The field Alert Name in TradingView will be ignored – it is currently only used for display purposes within TradingView!

Note: Since version 1.3 calculations are supported within placeholders!
Valid operators are + (addition), - (subtraction), / (division), * (multiplication), % (modulo) and ^ (power of) – besides the listed pre-defined placeholder variables below you can also use all of your custom plot variables, see Custom Plots / Vars below!
eg. price=[close - (_myplot * 2)] – keep in mind that all placeholder expressions are evaluated before the syntax is actually run!

IF / ELSE  (Preprocessor)

Since version 1.3 it is also possible to use the new conditional placeholders [IF condition] ... [ELSE] ... [END] to run parts of your syntax only when the specified conditions are met!

The [ELSE] ... (shorthand [] ...) part of the construct is optional.
A condition can be preceded by they keyword not to invert its evaluation result.
Multiple conditions can be combined by using the keywords and / or (outside of brackets only!) with and being inner binding.

The condition is a simple comparison – supported comparison operators are < (less than), <= (less than or equal), = / == (equal), <> / != (unequal), >= (greater than or equal) and > (greater than).

For the right-hand side of the comparison, calculations/expressions are supported including grouping in brackets – valid operators are + (addition), - (subtraction), / (division) , * (multiplication), % (modulo) and ^ (power of)
(same as in the Unified Alerts section above for placeholder calculations!)

All placeholder variables in the table above and also OHLC data (if sent with the TradingView alert message) can be used in a condition – including custom plots (_name).

If the left-hand side variable of the comparison is a string (mainly the name or id placeholders) then only = / == (equal), *= (starts with), <> / != (unequal) and !*= (doesn't start with) comparison operators are allowed.
Furthermore the right-hand side of the comparison in that case can either be a single string literal or a comma separated list of strings – wildcards (*) are supported and comparisons are always case insensitive!
(eg. [if name=bitmex*entry,bitmex*exit] will match all of the following: Bitmex XBTUSD Entry, Bitmex XRP Entry, Bitmex Some Exit)

Note: For exact non-wildcard string comparisons enclose the string in double quotes! (eg. [if acc=test,*] will ALWAYS match EVERYTHING while [if acc=test,"*"] will only match the account names test and *)

Example Syntax:

[if not _myplot >= (close + _otherplot) / 2]
# myplot is below the mid point of OHLC close and otherplot
notify=log:warning:"we are below!"
[else]
notify=log:success:"we are above! (and in the else part)"
[end]

[if date > 1115 and time > 530]
notify=log:warning:"the date is after november 15th and the time after 5:30 am!"
[end]

[if long]
echo="this alert was run with side being buy or long!"
[end]

Note: These pre-processor conditionals are evaluated before the syntax is run, so they can only check the state/conditions of variables (custom plots) at that time!

Custom Plots / Variables

Since version 1.2.62 custom plot data (price plots, quantity, leverage etc.) can be sent with the TradingView alert message to be referenced later in your syntax commands!

For this to work the TradingView OHLC data and your indicator plot data has to be received in a certain format at the end of your alert message.
The following screenshot is showing the default entry alert for one of our indicators as an example:

Add the following text as the last line in a TradingView alert:
#{{open}},{{high}},{{low}},{{close}},{{volume}} – optionally add ,{{plot_0}} or ,somename:{{plot_0}} for custom plots that you can later reference in syntax!
(click on the question mark icon under the Message text box in TradingView to learn more about how to use TradingViews plot placeholders)

Note: The [side] placeholder for unified alerts can also be controlled this way, making a single TradingView entry alert possible!
Simply add a custom plot reference with the name side (as shown in the screenshot above) – the following variants are supported:
side:1:0 / side:0:1 (useful for two boolean plots, one per side)
side:1 / side:-1 (used in the screenshot above)
side:long / side:short
side:buy / side:sell (useful for strategy alerts)

After everything is set up correctly, upon receiving an alert message containing valid OHLCV/custom data you can use it in price reference syntax options by name:
open, high, low, close: OHLCV data from the candle that triggered the alert
oc: Average price between open and close
hl: Average price between high and low
custom<number>: Custom data/plots added via ,{{plot_0}},{{plot_1}},...
_somename: Custom data/plots when given a name

Since version 1.3 instead of using the price reference options (prref etc.) you can specify custom plot variables directly in the original parameters –
eg. q=_myquantity, optionally with a multiplier (*) or divider (/) eg. q=_myquantity*3 or interpreted as percantages eg. q=_myquantity% (allowed operators for q= and l= are * and /, for all other parameters + and -!)

Since version 1.3.0.2 custom plot defaults can be defined in the first line of a ➔ PV Alert via #var1:value,var2:value,... – use ! to overwrite a received OHLC/plot value eg. #!_sl=123,!close=456

Since version 1.3.3 custom plot data or values can also easily be sent to a ➔ PV Alert in the form of PVALERT(var1=value1,var2=value2,...) –
reserved keywords for parameters in this case are e / ex, s / sym, a / acc, ap / par as they can be used to set default exchange, symbol and account for the alert being triggered! (or in the form a=ex:sym:acc or ap=ex:sym:acc in one of them)

Example TradingView Alert Message:

PV_ALERT_ONE(ex=bitmex,sym=xbtusd,myExit={{plot("Take Profit")}})
PV_ALERT_TWO(acc=binanceft:btcusdt:test)
#{{open}},{{high}},{{low}},{{close}},{{volume}}

➔ See our Wiki for an example how to use custom plots in Syntax!

Note: OHLCV data and custom plots can easily be added to your TradingView alert message through the ProfitView addon context menu – simply right-click into the Message section of your TradingView alert as shown below and select Insert OHLCV:

Examples

Note: For more examples and standard syntax visit the syntax section of our Wiki !

Note: All settings on this page are always stored locally and never synced –
notification options in syntax always override configuration below, even if Notify on is unchecked!

Lorem Ipsum

Note: All settings on this page are always stored locally and never synced!    TradingView    Legacy Filters