Implementation

Setup guide

From TradingView invite acceptance to your first live trade. Step-by-step for both Path A (manual alerts) and Path B (full automation via bridge).

Setup Guide

This is the technical companion to How It Works. Read How It Works first if you haven't — it covers what the system does and which path (A or B) to choose. This guide assumes you've made that decision and are ready to set things up.

Estimated time: 15 minutes for Path A. 60–90 minutes for Path B the first time.

Contents

  1. TradingView — setup shared by both paths
  2. Path A — Standalone (manual execution)
  3. Path B — Full Automation

- 3A. TradersPost (futures: MNQ, MGC) - 3B. PineConnector (forex/CFD: NAS, XAU)

  1. Paper trading checklist
  2. Going live
  3. Troubleshooting
  4. Scaling and multi-account
  5. Support

Part 1 — TradingView Setup

1.1 Accept your script invites

After purchase, we send TradingView script invites to the email you used at checkout, typically within 24 hours. Go to TradingView → Profile → Invite-only scripts. The strategies in your tier should appear there.

If they don't appear within 24 hours, verify the email on your TradingView account matches your checkout email. If different, email support with both addresses.

1.2 Verify your plan and data subscriptions

TradingView plan:

  • Path A: TradingView free plan works with limitations (no email alerts, capped notification count). Essential ($14.95/mo) is strongly recommended.
  • Path B: Essential or higher is required — webhook alerts only work on paid plans (or a free trial of one).

⚠ Critical for futures strategies (MNQ, MGC) — real-time data subscription:

TradingView delivers futures data with a 10-minute delay unless you have a real-time data subscription. On delayed data, your strategy fires alerts 10 minutes after the actual market signal — your live results will diverge dramatically from the backtest.

Two ways to get real-time CME data:

  • Option A: Subscribe to CME real-time on TradingView for $7/month (non-professional rate). In TradingView → Profile → Manage Subscriptions → Market Data → CME Group. This covers CME, CBOT, COMEX, NYMEX — everything for MNQ + MGC.
  • Option B (free, recommended for prop firm users): Connect your futures broker to TradingView. Tradovate (used by Apex, Topstep, MyFundedFutures, Lucid Trading, Tradeify), Interactive Brokers, NinjaTrader Brokerage, and Optimus Futures all stream real-time CME data into TradingView at no extra cost. In TradingView → Profile → Brokers → find your broker → authorize.

Most Puravida Edge customers on prop firm challenges already use Tradovate — Option B is the default. If you trade futures only on a personal account without a TradingView-integrated broker, you need Option A.

Forex / CFD strategies (NAS, XAU): real-time data is included with TradingView Essential and higher. No extra subscription needed.

See Master Configuration Sheet §2 for the full data-subscription decision tree.

1.3 Add the strategy to your chart

Open the chart of the instrument the strategy targets (your config sheet specifies which one). Indicators (fx icon) → Invite-only scripts tab → click the strategy name.

Do not change the timeframe. Each strategy is locked to a specific TF defined in its config sheet.

1.4 Apply the preset from your config sheet

Click the gear icon next to the strategy name on your chart. Set Preset to the value listed in your config sheet. Presets combine account size (50K, 100K, 150K for futures; 100K for forex/CFD) with risk regime (Conservative or Aggressive). The strategy automatically sizes positions based on the preset — no manual scaling needed.

The matched preset for your situation is the value on your config sheet. Apply that. Save.

Aggressiveness fine-tuning (advanced):

You can cross-apply presets to dial aggressiveness up or down independently of the Conservative/Aggressive binary:

  • Apply a LARGER-size preset to your account → more aggressive. Example: $50K account with 100K Conservative preset → strategy trades 4 contracts (vs 2 for matched 50K Conservative). Roughly 2× effective risk because position size doubled but your DD buffer didn't.
  • Apply a SMALLER-size preset to your account → more conservative. Example: $100K account with 50K Conservative preset → strategy trades 2 contracts (vs 4 for matched 100K Conservative). Roughly 50% effective risk.

This gives you a continuous aggressiveness knob on top of the Conservative/Aggressive toggle. Useful for:

  • Building confidence early (start with lower-size preset → trade smaller than matched)
  • Squeezing faster progress on EOD-trailing firms when you're confident in the system (use higher-size preset → trade larger than matched)

Important caveats:

  • The mismatch is on YOUR risk side. The strategy doesn't know your actual account size or DD buffer — it just executes whatever preset you select. You're responsible for the math.
  • Don't cross-apply more than one size tier unless you understand the math. Going from 50K preset to 150K preset on a $50K account is ~3-4× position size on the same DD buffer — high blow probability.
  • Cross-applying to larger presets does NOT make the Real-time/Aggressive combination safe. The compatibility matrix in §1.5 still applies regardless of size-cross-application.

1.5 Verify the preset matches your prop firm's drawdown model

Read this before going live, even if your config sheet specifies a preset. The config sheet preset is tuned for a primary use case; if your actual prop firm uses a different drawdown calculation method, you may need to override.

The presets are calibrated for different drawdown regimes:

| Your prop firm's drawdown model | Conservative | Aggressive | |---|---|---| | End-of-Day (EOD) Trailing — floor updates only at session close | ✅ Works | ✅ Works | | Real-time / Intraday Trailing — floor updates continuously during session | ✅ Works | ❌ Do not use | | Static — fixed dollar floor that never updates | ✅ Works | ⚠️ Use with caution; default to Conservative |

How to identify your firm's model: check your prop firm's rule sheet or terms page. Look for explicit language:

  • "End of Day," "EOD trailing," "trailing drawdown updates at close" → EOD
  • "Intraday trailing," "real-time," "continuous trailing" → Real-time
  • "Static drawdown," "fixed drawdown," "maximum loss limit" with no trailing mention → Static (common on 2-phase swing forex evaluations)

⚠️ Critical warning. Aggressive sizing on a real-time trailing firm has a high probability of intraday floor breach and account loss. This is a structural mismatch between firm rules and preset, not a strategy defect. Use of the Aggressive preset on a real-time trailing firm is not covered by the money-back guarantee — see the Risk Disclosure section on preset compatibility for the full statement.

Default rule: when in doubt, use Conservative. It works on every drawdown model.

Account size note: the preset choice is determined by your firm's rule regime, not by your account size. Whether you have a $25K, $50K, or $150K account, the same compatibility table applies. Account size affects contract or lot quantity, which is handled separately — covered in Part 2.4 for Path A (manual scaling), and handled automatically by the strategy's built-in alert message for Path B.

1.6 Understand what the strategy shows on your chart

After applying the strategy and preset, you should see entry markers, a stop loss line, and a take profit line painting at each historical signal on the chart. This is your visual signal source. Both Path A and Path B use the same underlying signals; they differ only in how the trade gets placed.

Part 2 — Path A — Standalone

2.1 Create the alert

Alarm clock icon (top-right) → Create Alert.

Settings tab:

  • Condition: your strategy → "Alert() function calls only"
  • Trigger: Once per bar close
  • Expiration: Open-ended

Notifications tab: check the channels you want — Notify in app (mobile push), Show pop-up, Play sound, Send email. Pick at least two so you don't miss signals.

Message tab: paste exactly:

{{strategy.order.alert_message}}

That's the entire message. The strategy code generates the readable alert text (action, ticker, price, stop loss, take profit, size) inside that placeholder when the alert fires.

Save the alert.

2.2 Test the alert

Manage alerts → click your alert → use TradingView's test alert button. Confirm mobile push arrives, email arrives, sound plays. If anything is missing, check Profile → Settings → Notifications.

2.3 Execute the trade when an alert fires

When a real alert fires:

  1. Open your broker's platform
  2. Place a bracket order in the direction of the signal: market entry + stop loss at the SL price from the alert + take profit at the TP price from the alert
  3. Verify all three orders show as working in your position panel
  4. Walk away — the broker handles TP and SL automatically

Always place the stop loss as a working order at the broker, not as a mental note. This caps your loss even if you lose internet or fall asleep.

2.4 Position sizing

The alert tells you a contract or lot quantity calibrated for the preset you applied (account size × Conservative/Aggressive). The strategy handles sizing automatically — you don't need to do per-trade scaling math.

If you applied the matched preset (e.g., 50K Conservative preset on a $50K account, with your firm's drawdown model), trade exactly the contract count the alert specifies. Done.

If you cross-applied a different-size preset for aggressiveness fine-tuning (see §1.4):

  • The alert reflects the cross-applied preset's size. Trade what it says.
  • You're already accepting different effective risk via the cross-application.
  • Don't additionally scale on top of that — you'd be applying the same multiplier twice.

Rounding rule (Path A specific):

For fractional sizes (rare on futures, common on forex):

  • Round down, never up. 1.5 contracts → trade 1, not 2. 0.07 lots → trade 0.05 or 0.10 depending on your broker's minimum.
  • Path B handles fractional rounding automatically inside the strategy's alert message.

Forex minimum lot size:

Some MT5 brokers require 0.10 lots minimum. If the strategy alert says 0.05 lots and your broker won't accept anything below 0.10, you have three options:

  1. Switch to a broker with smaller lot minimums (most ECN brokers support 0.01)
  2. Use a higher-size preset to push the lot count above the minimum (effectively more aggressive)
  3. Skip the trade until the strategy fires at a size your broker accepts

Part 3 — Path B — Full Automation

🧭 Don't replicate UIs from screenshots in this guide. TradersPost and PineConnector occasionally adjust their interfaces; their own docs always have current screenshots. This guide tells you what to do and which decisions matter; their docs show the exact buttons.

3.0 Which bridge for which instrument

| Instrument | Bridge | Why | |---|---|---| | MNQ, MGC (futures) | TradersPost | Routes to Tradovate / ProjectX backends used by Apex, Topstep, MFFU, Lucid, Tradeify | | NAS, XAU (forex/CFD) | PineConnector | Routes to MT5 brokers used by Forex Prop, The Funded Trader, FundedNext |

If you purchased a tier with both futures and forex strategies, you'll use both bridges.

3.1 Verify your prop firm's rules

Before paying for any bridge subscription, read your prop firm's terms on automated trading, news event windows, minimum trading days, and capital allocation. If anything doesn't fit your intended use, switch that strategy to Path A.

Part 3A — TradersPost (for MNQ/MGC futures)

📖 TradersPost docs are excellent and current. This section gives you the orchestration; their docs cover the UI. - Getting started - Broker connections - Strategy subscriptions - Webhook reference

Steps in order:

  1. Sign up at traderspost.io — free trial included. Plan: Starter ($49/mo) for one live account. Add slots at $10/mo each for additional accounts.
  1. Connect your broker under Brokers → Connect New Broker. For Apex / Topstep / MFFU / Lucid / Tradeify, choose Tradovate and OAuth with your prop firm credentials. For prop firms on the ProjectX backend (e.g., The Trading Pit), choose ProjectX. For other prop firms, check your firm's docs to confirm which backend they use.
  1. Create a Strategy in TradersPost. Name it descriptively (e.g., "Pivot MGC Conservative"). Asset class: Futures.
  1. Copy the webhook URL from your new strategy. Format: https://webhooks.traderspost.io/trading/webhook/[uuid]/[password]. You'll paste this into TradingView in step 6.
  1. Create a Subscription linking your strategy to a specific broker account. Critical settings:

- Use signal quantity: YES - Use signal stop loss: YES - Use signal take profit: YES - Default order type: Market - Account: start with a paper account for testing; switch to live/funded after verification

  1. Create the TradingView alert. Alarm icon → Create Alert. Settings: your strategy → "Alert() function calls only", once per bar close. Notifications tab: enable Webhook URL and paste the TradersPost URL from step 4. Message tab: paste exactly:

`` {{strategy.order.alert_message}} ``

That's the whole message. The strategy code generates the correct JSON payload internally.

  1. Test on paper for at least 5 trades before switching the subscription to a live or funded account. See Part 4.

Part 3B — PineConnector (for NAS/XAU forex/CFD)

📖 PineConnector docs cover the UI in detail. This section gives you the orchestration. - Getting started - MT5 EA setup - Alert syntax - VPS options - Symbol mapping - Troubleshooting

Steps in order:

  1. Sign up at pineconnector.com — 14-day free trial, no credit card. Basic plan $26/mo for one connection.
  1. Note your License ID (13–14 digit number from your portal). This is what authenticates alerts to your account. Keep it private — never paste it in public screenshots.
  1. Decide where MT5 will run. Three options, simplest first:

- Your own computer (free) — Windows 10/11 or macOS. Works for daytime trading. Risk: sleep mode, restarts, internet drops. - PineConnector Cloud (~$30/mo) — hosted by PineConnector near broker servers. 24/7, no management. Easiest for non-technical users. - Third-party VPS ($15–30/mo) — BeeksFX, QuantVPS, ForexVPS, Contabo. Most control, requires you to manage it.

For getting started, your own computer is fine. You can upgrade to a VPS later if reliability becomes a problem.

  1. Install MT5 from your broker's site, log into your account.
  1. Download the PineConnector EA from your portal → install into MT5 (File → Open Data Folder → MQL5 → Experts). Restart MT5. Enable Tools → Options → Expert Advisors: Allow Algorithmic Trading + Allow DLL imports. Toolbar Algo Trading button must be green.
  1. Attach the EA to any chart in MT5. In the EA settings dialog: Common tab → Allow Algo Trading ✓; Dependencies tab → Allow DLL imports ✓; Inputs tab → paste your License ID. Green smiley face appears on the chart = connected.
  1. Test from the PineConnector portal before involving TradingView. Portal → Connections → Send Test Alert → small test trade. Confirm MT5 opens the position. Close it.
  1. Create the TradingView alert. Alarm icon → Create Alert. Settings: your strategy → "Alert() function calls only", once per bar close. Notifications tab: enable Webhook URL and paste:

`` https://webhook.pineconnector.com ``

Message tab: paste exactly:

`` {{strategy.order.alert_message}} ``

That's the whole message. The strategy code generates the PineConnector-formatted command internally, including your License ID, risk parameters, and stop/TP values.

  1. (Optional) Symbol mapping. Some MT5 brokers use non-standard symbol names (e.g., XAUUSD.x instead of XAUUSD, or US100 for Nasdaq). If alerts fire but orders reject with "symbol not found," add a mapping in PineConnector portal → Settings → Symbol Mapping.
  1. Test on demo for at least 5 trades before going live. See Part 4.

Part 4 — Paper Trading Checklist

Don't skip. This catches configuration errors before they cost real money.

Minimum criteria:

  • [ ] Alert fires correctly on at least 5 signal occurrences
  • [ ] Position size matches expected (within rounding tolerance)
  • [ ] Stop loss is a working order at the broker, not a mental note
  • [ ] Take profit is a working order at the broker
  • [ ] Exits execute correctly on both TP hit and SL hit, no orphaned orders
  • [ ] No alerts fire on weekends (if they do, something is misconfigured)
  • [ ] Strategy fires at the intended session times — not 6 hours off due to a timezone mismatch

Duration: at least 5 complete trade cycles per strategy. Better: until you've seen at least one cluster of losses, so you've verified the system handles drawdowns cleanly.

Part 5 — Going Live

Pre-flight checklist:

  • [ ] Paper trading criteria all passed
  • [ ] Funded/live account connected and verified
  • [ ] Risk parameters confirmed (correct contract/lot size for your account size)
  • [ ] You understand outage behavior (next section)

Switching from paper to live:

  • Path A: just place your next signal in your funded account
  • Path B / TradersPost: edit your Subscription, change Account from paper to funded, save
  • Path B / PineConnector: attach the EA on your live MT5 (License ID auto-roams)

First week: check positions twice daily, don't add a second strategy, email support immediately if something doesn't match expected behavior.

Outage behavior to understand:

The crucial guarantee: TP and SL are placed as working orders at your broker in Path B (this is why "Use signal stop loss / take profit" was set to YES in the TradersPost subscription; the PineConnector flow handles this automatically through the strategy's built-in alert message). If TradingView, the bridge, your VPS, or your internet drops, your already-open positions still have their TP/SL working at the broker. You can only miss new entries during an outage, not exits.

For Path A users: this only works if you placed the SL as a working order at the broker — which you should always do.

Part 6 — Troubleshooting

Alert not firing in TradingView

  • Top-right alarm icon → Manage alerts → status is Active?
  • Trigger is "Once per bar close" (not "Every tick")?
  • Condition is "Alert() function calls only"?
  • Alert hasn't expired?

Path B — webhook fires but no order at broker

  • Webhook URL pasted exactly, no trailing spaces?
  • (TradersPost) URL includes both uuid and password segments?
  • (PineConnector) EA shows green smiley on chart? License ID correct?
  • (PineConnector) Computer or VPS online, no firewall blocking outbound?
  • TradingView plan supports webhooks (Essential or higher)?

For deeper diagnostics, check the bridge's own logs first:

  • TradersPost → Dashboard → Logs (shows every webhook received and its disposition)
  • PineConnector → Portal → Connections → your account → Logs

Path B — order rejected by broker

  • (PineConnector) Wrong symbol name? Set up Symbol Mapping.
  • Account near drawdown limit? Position size too large?
  • Outside trading hours?
  • (TradersPost) Subscription routed to suspended/disconnected account?

Wrong position size

  • (TradersPost) "Use signal quantity" checked on the subscription?
  • (PineConnector) Wrong preset applied on the chart? Conservative and Aggressive size differently — verify it matches your config sheet.
  • (Forex) Your broker's minimum lot size? Some require 0.10 minimum; smaller calculated sizes may round up or reject.
  • (Path A) Did you apply the matched preset for your account size? Or are you cross-applying a different-size preset for aggressiveness adjustment (in which case the alert's size is correct — it's a different preset, not your account's matched preset)?

Live results diverge from backtest

  • 10–20 trades: statistical noise, expected
  • 50–100 trades: meaningful divergence — email support with your live trade log
  • Win rate off by 10+ percentage points OR avg win/loss off by 30%+: likely a configuration error, not slippage

Part 7 — Scaling and Multi-Account

Multiple strategies on one account

  • Path A: create one alert per strategy, execute manually as they fire
  • Path B / TradersPost: one Strategy in TradersPost per Pine Script strategy, each with its own subscription pointing to the same broker account
  • Path B / PineConnector: same License ID across all alerts; each alert specifies its own symbol and parameters

Same strategy on multiple accounts

  • Path B / TradersPost: multiple Subscriptions under the same Strategy, each routing to a different broker account (parallel execution)
  • Path B / PineConnector: load the EA on multiple MT5 instances with the same License ID (auto-roaming license)

Considerations

  • Correlated drawdown: running the same strategy on 3 accounts means 3× exposure on a bad day
  • Diversification: consider running different strategies on different accounts
  • Prop firm rules: some firms cap capital allocation per strategy across accounts (Forex Prop's $400K limit, for instance) — check your firm's terms

Part 8 — Support

Email support if anything doesn't match documented behavior, if you hit a wall on bridge configuration, or if you have questions about strategy logic.

Include in your email:

  • Your TradingView username
  • Which path you're setting up (A — Standalone, or B — TradersPost or PineConnector)
  • Screenshots of any error messages
  • Specific timestamps if you're asking about an alert that didn't behave correctly

Response time: typically under 24 hours weekdays, longer on weekends.

What's not supported:

  • Custom Pine Script modifications (we keep every customer on the same audited strategy version)
  • Broker-specific issues (contact your broker)
  • TradingView account issues (contact TradingView support)
  • Prop firm rules and challenges (contact your prop firm)

Authoritative External Documentation

When in doubt about a specific UI element or feature in TradersPost or PineConnector, their official docs are the source of truth:

We monitor both bridges and update this guide when their UI or behavior changes materially.

Setup Guide version 1.0 — May 2026. Companion to the How It Works page.