# Deploy Strategies to TradingView Found a strategy in Atlas that you want to actually run on a chart? This page walks you through copying an Atlas-found strategy into TradingView and letting the **Backtest – Strategy Builder** indicator run it live. The companion page on the backtester side is Atlas Mode — Strategy Import — it covers the same flow from the TradingView side. *** **Overview** Atlas finds strategies; the **Backtest – Strategy Builder** indicator runs them on your TradingView chart. The two are designed to work together: | Where you are | What you can do | | ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- | | **Atlas chat result** | Read metrics, view the equity curve, and copy the entry/exit rules. | | **Backtest – Strategy Builder on a chart** | Paste those rules into Atlas Mode and watch the strategy run on real bars — same symbol, any symbol, any timeframe you want. | You don't need to wire signals, configure External Signal slots, or rewrite anything. The strategy moves with one copy-paste. *** **Step-by-Step** **Step 1 — Pick a strategy in Atlas** Run an Atlas search and review the matching strategies. Each strategy card shows its metrics (Net Profit, Trades, Win Rate, Max DD, Profit Factor, Sharpe, Overfit %), its equity curve, and its entry/exit conditions. When you find one you want to keep, click the **Copy** or **Copy rules** button on the strategy card (or copy the rules block directly out of the chat message). The copied text looks something like this: ``` Long Entry: Trigger: Smart Signals +▼/▼ Fires (SSA) States: Trend Bias Is Weak Bearish (SSA), TRC Is Trending (SSA) Short Entry: Trigger: Smart Signals +▲/▲ Fires (SSA) States: Trend Bias Is Weak Bullish (SSA), TRC Is Trending (SSA) ``` This is the **rule block**. It's all the backtester needs. **Step 2 — Open TradingView and add the Strategy Builder** In TradingView, open the chart you want to run the strategy on. Search for **"Backtest - Strategy Builder \[AlgoAlpha]"** in the indicators panel and add it to your chart. If you already have it on the chart, just open its settings. **Step 3 — Make sure Atlas Mode is on** In the indicator settings, look for the **"Atlas Strategy Conditions"** group. The **Use Atlas** toggle should be checked (it is by default). When Atlas Mode is on, the Manual Mode settings are hidden — the strategy is driven entirely by the text rules you paste. **Step 4 — Paste the rules** Click into the **"Add Atlas Rules Below"** text area and paste the rule block from Step 1. The backtester parses the text automatically — entries, exits, triggers, and state filters all get wired up for you. **Step 5 — Watch the strategy run** The backtester starts simulating immediately. The on-chart **Strategy Table** shows live status and metrics, and TradingView's **Strategy Tester** panel (bottom of the screen) gives you a full trade-by-trade breakdown. *** **What you can change after pasting** Once the rules are pasted, the strategy is yours to tweak: * **Edit the text directly** in the "Add Atlas Rules Below" box if you want to swap a state, change a trigger, or add a custom direction. The parser re-evaluates every time the text changes, and the Strategy Table's **Atlas Rules** row warns you about typos or unsupported fields. * **Use External Signal 1-6 in text rules** when you need a custom chart source, crossover, threshold, rising, or falling condition. Configure the external signal slot in Condition Setup, then reference it in the Atlas text as `External Signal 1`. * **Try a different symbol or timeframe.** Atlas tested the strategy on a specific asset and bar size, but the rules are portable — drop the same backtester on an ETH chart or a 5m chart to see how the same logic behaves elsewhere. * **Combine with Manual Mode features.** Uncheck **Use Atlas** to reveal the full Manual Mode settings (leverage, sizing, alert rail, TP/SL sources, external indicator wiring). You can keep your Atlas rules in mind while building something more customised. *** **When to stay in Atlas vs go to TradingView** | Use case | Where to do it | | ----------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | | Searching across thousands of pre-computed strategies | **Atlas** | | Comparing several strategies' historical metrics side-by-side | **Atlas** | | Running a strategy live on a chart you actually watch | **TradingView (Backtest – Strategy Builder)** | | Forward-testing on a different symbol / timeframe | **TradingView** | | Setting up real-time alerts when the strategy opens, closes, or flips a trade | **TradingView** — enable the indicator's alert outputs. Alerts fire on actual position changes, not repeated true conditions. | Atlas is great at *finding*; the backtester is great at *running*. The rules format is the bridge between them. *** **Indicator coverage** Atlas Mode parses signal names from **SSA**, **ILPAC**, and **MC (Momentum Concepts)** — exactly the three indicators Atlas searches over. You can paste any rule block Atlas produces without worrying about which indicator family it uses. For the full signal vocabulary (every trigger and state name Atlas can return), see the Signal and Conditions Reference. *** **Troubleshooting** * **"Nothing happens after I paste"** — Make sure the **Use Atlas** toggle is checked. If it's off, the text area is ignored. * **Unknown signal names** — If a trigger or state name is misspelled, the strategy treats it as false and shows a warning in the Strategy Table's **Atlas Rules** row. Double-check spelling against the Signal and Conditions Reference. * **Take-Profit / Stop-Loss in Atlas Mode** — TP/SL source inputs aren't visible in Atlas Mode. To add dynamic TP/SL levels, switch to Manual Mode and link them to plots from SSA's Smart Exits. * **The strategy looks different from Atlas's backtest** — Expected if you changed symbol or timeframe. Atlas's metrics come from a specific test environment (asset + timeframe + 20,000 bars + 0.1% commission); running on a different chart will produce different results. That's actually the point of forward-testing. *** **See also** * Atlas Mode — Strategy Import — the same workflow documented from the TradingView side, with the full rule-text format spec. * Text Scripting Rules — the exact rule grammar for `Trigger:`, `States:`, external signals, parser warnings, and unsupported syntax. * Signal and Conditions Reference — every trigger and state Atlas can emit. * Backtesting Configurations — how Atlas's pre-computed backtests work (asset universe, timeframes, commission, etc.). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://algoalpha.gitbook.io/algoalpha-user-manual/atlas-ai-backtesting-agent/deploy-strategies-to-tradingview.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.