Frequently asked questions for the paid invite-only version. For Lite questions, see the Lite FAQ.
Visit MyB2B.ca/pricing and select your plan — Monthly (USD 29/mo) or Annual (USD 249/yr). You will be directed to a Stripe checkout page. Enter your TradingView username when prompted. This is required to activate access.
TradingView access is granted within one business day of purchase. You will receive a confirmation email when access has been activated on your account.
Email TradingView@MyB2B.ca immediately with your order number and the correct TradingView username. We will update the access record. This is not grounds for a refund.
Use the billing portal link in your original Stripe receipt email to manage or cancel. Cancellation takes effect at the end of the current billing period. TradingView access is revoked on the day the subscription ends.
No. Access is granted per TradingView username. Each username requires a separate subscription.
TradingView Essential is the minimum for real-time alerts. If you intend to use the JSON alert payload with a webhook, you need a TradingView Premium plan or above, which supports webhook alert delivery.
| Row | What It Shows |
|---|---|
| Engine | READY = correct scope. Error = wrong symbol or timeframe |
| H1 Bias / M15 Structure | Multi-timeframe trend alignment |
| Long/Short Core & Quality | Live scores for current candidates |
| Next Resistance / Support | Nearest key level above and below price |
| Location / Late | LOC OK = not blocked by key level. LATE = entry distance exceeded |
| Confirm Window | Bars remaining in the confirmation window |
| Pending Reason | Which filter is blocking a candidate from confirming |
| Live Setup | P LONG/SHORT = candidate armed. LONG/SHORT = confirmed. NONE = none |
| Validation | ON = outcome tracking active. OFF = disabled |
| Last Outcome | Most recent validation result |
| Lot / Stop Guard | Configured lot size range and stop pip range |
| Risk / Setup | Dollar risk per setup and percentage of account |
| Max Risk Cap | Hard dollar ceiling per position. OFF if not set |
| Account | Account size used for position sizing calculations |
The engine calculates a recommended lot size per setup based on three inputs:
The calculated lot size appears in the alert payload and status panel. It is for reference only — the indicator does not execute trades.
No. Risk settings control position sizing only. They do not affect whether a setup is detected, scored, or confirmed. Two users with different account sizes see identical signals.
A potential setup (candidate) is a setup that has passed initial scoring but not yet received full confirmation. The engine arms the candidate and waits for the confirmation bar. During this window, the candidate is drawn in orange on the chart with projected entry, stop, and target levels.
If the confirmation window closes without a valid bar, or if price invalidates the setup, the candidate lines are dimmed and labeled EXPIRED or INVALID. The engine resets and waits for the next qualifying candidate.
Validation Mode is a post-entry tracking system. Once a setup is confirmed, the engine monitors it and records the terminal outcome. It does not change how signals are generated — it only tracks what happens after entry.
| Outcome | Meaning |
|---|---|
| TP1_HIT | Price reached the first profit target |
| TP2_AFTER_TP1 | Price reached TP2 after already hitting TP1 |
| SL_HIT | Price hit the stop loss before any target |
| BE_AFTER_TP1 | After TP1, stop moved to break-even and was hit on reversal |
| BE_CANDIDATE | Price has held long enough to justify a break-even stop move |
MFE (Maximum Favorable Excursion) — how far the trade moved in your favour before it closed.
MAE (Maximum Adverse Excursion) — how far it moved against you before it closed.
Both are tracked in R multiples and included in the validation alert payload.
Every Premium entry alert and validation alert contains a machine-readable JSON payload. This allows alerts to be received by a webhook endpoint, parsed programmatically, and logged to a trade journal, database, or execution bridge — without manual data entry.
You need a TradingView Premium plan or above for webhook delivery.
The alert message field is automatically populated with the JSON payload from the indicator.
| Alert | When It Fires |
|---|---|
| Long Entry | Long setup confirmed on bar close — full JSON payload |
| Short Entry | Short setup confirmed on bar close — full JSON payload |
| Long Invalid | Confirmed long failed follow-through |
| Short Invalid | Confirmed short failed follow-through |
| Long Validation Outcome | Tracked long trade reached terminal state — validation JSON payload |
| Short Validation Outcome | Tracked short trade reached terminal state — validation JSON payload |
This is expected behaviour on many sessions. The engine requires all confirmation filters to pass simultaneously at the same bar. On lower-volatility days or sessions with unclear structure, the thresholds may not be met. An absence of signals is a valid outcome.
The Pending Reason row shows which filter is currently blocking confirmation for the armed candidate. Common causes are a location block (price too close to a key level), a late-entry flag, or a score drop since the candidate was armed. The engine will confirm or expire the candidate within the confirmation window.
Email: TradingView@MyB2B.ca
Website: MyB2B.ca
Response time: within one business day, Monday to Friday, Eastern Time.
Always include your TradingView username and order number in support emails.
Terms of Use and Refund Policy are available on this site and linked from your Stripe receipt email.