TradingView combines charting, alerts, Pine scripts and selected broker connections. Start by separating the chart’s data source, a simulated strategy and the live account. Similar screens can show all three, but a signal drawn by a tester is not a confirmed broker execution.

What exactly is TradingView?

TradingView offers browser charting as well as desktop and mobile applications. A saved layout can support work across devices, subject to the account and plan. A charting account is separate from the broker that holds funds and accepts orders. Check the selected data source and the account shown in the trading panel before using that workflow.

Search results can include currencies, shares, futures and indices from different sources. A cash index, a futures series and a CFD on that index are different products even when their pictures look similar. Record provider, full symbol, product, session and any series or adjustment setting. Access to a displayed instrument does not prove that it can be traded through your linked account.

Choose the inputs for your rule before changing the workspace. Our guide to technical analysis fundamentals explains the concepts. For multi-timeframe analysis, check the chosen plan’s layout limit: a watchlist is not the same as several simultaneous chart panels. The current Basic matrix shows one chart per tab.

Chart time zone does not change Pine's default hour

Before setting a time filter, distinguish chart labels from code values. In our example a bar opens at 2026-10-06, 13:30 UTC, and syminfo.timezone is America/New_York. Local time is 09:30, so Pine's default variable hour is 9. A chart set to Europe/Warsaw displays the same instant as 15:30.

Scroll sideways to see the full diagram

One bar, two displays, unchanged Pine hourA hypothetical bar opens on October 6, 2026 at 13:30 UTC. The symbol time zone is America/New_York, where it is 09:30, so Pine's default hour is 9. A Europe/Warsaw chart shows 15:30; switching it to UTC shows 13:30. Pine hour remains 9.One bar: 2026-10-06Open: 13:30 UTCCHART TIME ZONESYMBOL TIME ZONEEurope/Warsaw15:30America/New_York09:30After chart change:UTC: 13:30Default Pine hour9: still 9New time labels do not change the rule.Specify the filter's zone in the script.
Both branches share one timestamp. The left changes display; the right determines the script's default hour interpretation.

After switching the chart to UTC, you see 13:30, but hour still returns 9. Pine does not read the chart's time-zone setting for calculations. To apply a Warsaw-time rule, specify it explicitly, for example hour(time, "Europe/Warsaw"); this bar gives 15. In the test journal, record full UTC time, symbol zone and filter zone rather than comparing only numbers on two screens.

Assumptions: One hypothetical bar opening and an explicitly chosen symbol-source zone, not an actual trade record. On this date America/New_York is UTC-4 and Europe/Warsaw UTC+2. The hour variable refers to bar opening, not closing time. Official material: Pine Script: time and time zones.

What sets Pine Script and the community apart?

Pine Script supports indicators, simulated strategies and alert conditions, with functions such as RSI. A language name cannot establish that a beginner will finish in half an hour. Define the rule and its timing first. For example, an intrabar threshold crossing and a confirmed candle close are different conditions; code and alert frequency must implement the intended one.

Public scripts are subject to TradingView’s publication rules and moderation. That does not certify a profitable trading edge. Check how a signal uses available information and whether a historical marker was placed only after later confirmation. Closed code limits what you can inspect; likes, a subscription or moderation do not replace a reproducible test.

What does TradingView cost?

The current plan matrix includes Basic, Essential, Plus, Premium and Ultimate. Premium is therefore not the highest plan in the whole offering. Match the required layout, indicator, alert and history limits to your account status. A higher subscription does not by itself include every exchange’s real-time data fee.

Read the source and delay label on the chart. Some stock and futures feeds need a separate entitlement; default US stock data may come from Cboe rather than the primary exchange. Eligible broker data subscriptions can be verified for supported integrations, but the provider’s list specifies which exchanges and accounts qualify.

Check the current TradingView plan matrix
Chart and indicator limitsVerify the chosen plan and layout limits
Alerts and historyVerify alert type, count and historical-data coverage
Intervals and replayVerify the instrument and feature entitlement
Market dataCheck separate exchange subscriptions and delayed versus real-time data

Compare the current plan limits against the specific features you need, including chart layouts, alerts, history, intervals and separate market-data entitlements. Premium is not necessarily the highest available tier. Choose from the current vendor matrix rather than a universal claim that one tier is sufficient for most users.

What does it look like in practice?

Hypothetical example (illustrative)

Use an explicitly hypothetical H1 rule requiring a close above 1.1050. Price reaches 1.1052 at 10:35, but the bar closes at 11:00 at 1.1040. An intrabar threshold condition can become true; the close-above-threshold condition does not. This is our invented timeline, not a historical trade. Record which rule, price series and alert frequency you tested.

TradingView’s strategy emulator applies historical fill assumptions; Bar Magnifier uses available lower-interval data. It may change an execution sequence, but does not establish that a live fill or your queue position would match. Check coverage for the specific period. Alerts run on TradingView’s servers, but their creation stores a separate copy of the script, inputs, symbol and timeframe. Editing the chart later does not update that running copy; recreate the alert for the changed rule.

For a strategy backtest, record the code version, data period, costs, signal timing and fill model. Comparing another tester is useful when those inputs match; a different total does not prove which implementation is right. Our article on divergence explains the signal concept, whose live availability must also be checked.

Where does the convenience end?

Live orders require a supported broker connection for the actual contracting company, account type and product. For example, the OANDA group’s logo alone does not establish support for every local entity. The Polish OANDA TMS instructions separately describe its CFD account route. Elsewhere, use the documentation for your own provider. A missing connection does not mean that MetaTrader is your only alternative.

A Pine strategy does not itself place orders at a connected live broker. External software can interpret webhook alerts, which introduces a separate execution system. Test its state handling. In our fictional duplicate-delivery exercise, a receiver gets the same decision ID twice, each requesting an additional 0.10-lot long. We assume zero initial exposure and full fills, solely to isolate duplication; we do not claim that TradingView always repeats messages.

Same decision twice; illustrative receiver rules, not a complete execution design
Receiver ruleRecognised decisionsFinal long
Execute every message20.20 lots
Remember the handled decision ID10.10 lots

The ID must distinguish the decision and rule version. Using only EURUSD would wrongly block later legitimate signals. Track receipt, submission and confirmed execution separately: “seen” does not mean “filled”. An in-memory set is lost on restart, and a crash between execution and recording leaves an uncertain state. Reconcile the account before retrying. This model tests duplicate processing; it does not guarantee exactly-once live execution.

For the wider context of where these tools sit in a trader's workflow, see our platforms section.

What to do tomorrow

  1. Choose one full symbol and record its provider, product, session and time zone. Compare daily, four-hour and hourly views within the actual plan’s layout limit.
  2. Use an available Bar Replay period to practise a written rule. Keep manual decisions separate from strategy-emulator results and live account executions.
  3. Test one alert with an explicit condition and frequency. For the fictional 10:35 crossing and 11:00 closing price described above, identify which condition was satisfied and which was not.
  4. Verify the actual broker entity, account type and product supported by the connection. Before resubmitting after a disconnect, inspect broker history rather than assuming the first request failed.
  5. Compare a few specific simulated transactions across testers only after matching data, rule timing, costs and fill assumptions. Document the first difference instead of declaring a universal winner.