TSB 5.0 Product Guide
Find your first trading leak in TSB
Import closed trades, verify the Journal, then use the same dataset across Leak Map, AI Coach, Backtester, reports, and widgets.
First Minute
1
Sign In
Use the purchase email. It is the account key for login, support lookup, and connected services.
2
Import One Source
Choose one source first. Re-imports and syncs merge into the Journal; duplicate groups are skipped instead of double-counted.
3
Verify the Journal
Check close dates, side, account, currency, and P&L before using Dashboard, Review Loop, Backtester, or Coach.
First Run: Journal, Leak Map, Dashboard
Find Your First Leak
After the first import: validate a sample, choose one analysis slice, then save one rule for the next session.
Find the leak after clean import
Play video
1
Verify the batch
Check 10-30 recent rows for close date, symbol, side, account, currency, and realized P&L.
2
Open Leak Map
Use setup, session, account, pair, and mistake filters to find the largest repeatable P&L drag.
3
Ask one sharper question
AI Coach and Backtester need a defined slice: account, date range, setup, session, or tag.
4
Write one next-session rule
Store a concrete rule such as max trades, allowed setup, blocked session, or stop-after condition.
Before reading analytics, verify close date, account, currency, side, entry, exit, size, fees, and stop loss in Journal. All Accounts converts totals into the default display currency.
Access & Notion
TSB keeps the trade database in the app: Journal, Leak Map, AI Coach, Backtester, Prop Tracker, Reports, imports, accounts, and widgets use the same account history. The Notion Template is optional workspace UI around that data.
Notion is not required for analytics. Connect it for Notion pages, embedded widgets, or two-way journal workflow.
Full Access
Complete workflow. Use this first.
- Unlimited trade history, account labels, and manual account records.
- Leak Map, dashboard, reports, AI Coach, Backtester, and Prop Tracker.
- Exchange / broker sync, MT4 / MT5 sync, and CSV / TSV / JSON / HTML upload.
- All Accounts scope plus single-account filtering across app pages.
Included Notion Layer
Optional. Claim later from the access page.
- Claimable template and embeddable widgets.
- Notes, setup pages, planning, and manual journal pages in Notion.
- Can be added later without changing app data.
- Works on the free Notion plan.
Import Trades
Pick the cleanest closed-trade source first. You can combine import methods later.
Choose your import path
Use one source first, then add other sources after the first imported sample is correct.
You have a closed-trade export
Use CSV / TSV / JSON / HTML Upload. Best columns: close date, symbol, side, size, entry, exit, account, currency, and realized P&L.
You trade MT4 / MT5
Use the MT4 / MT5 EA for ongoing sync. Use a detailed statement upload only for one-off backfills or support checks.
You trade crypto
Use exchange sync when your provider is shown in Settings. If not, upload closed trades instead of fills, orders, deposits, or ledger rows.
You trade stocks, options, or futures
Check broker sync first. If your broker is not visible, use CSV / TSV / JSON / HTML with real closed trades or activity history.
Your broker is not listed
Test one closed-trade export first. If TSB blocks the file, use the blocked import guide to choose a safer export.
CSV / TSV / JSON / HTML Upload
1
Upload your file
Upload closed trades or detailed trade history. TSB detects common columns, flags ambiguous dates, and blocks files that do not contain trade lifecycle data.
CSV worked if...
The result shows created, updated, skipped, and failed rows. Journal should show the expected account, close dates, side, symbols, and realized P&L.
If dates look wrong
Your export may use an ambiguous locale format. Re-run the import and confirm DMY or MDY when prompted. Do not analyze the data until the chronology matches the broker history.
If duplicates appear skipped
Repeated uploads can show skipped duplicate groups. That prevents double-counting. Report it only if duplicate trades still appear in Journal.
If the file is blocked
Use closed trades, closed positions, fills with open/close context, or a detailed broker statement. Ledger and raw-order files are blocked.
Why TSB blocked your file
Raw order exports, ledgers, deposits, working orders, cancelled orders, and partial histories do not reliably describe completed trades. TSB blocks them to avoid duplicate, open, or wrong-P&L rows.
| If your file says... | What it probably is | What to export instead |
|---|---|---|
| Pending, working, cancelled, rejected, expired | Order status history | Closed trades, fills with entry/exit context, or trade confirmations |
| Deposits, withdrawals, transfers, balance, cash | Account ledger | Realized P&L or closed-position report |
| Only order id, side, quantity, and status | Raw orders without lifecycle | Executions/fills export that marks open vs close, or broker trade history |
| Only open positions | Current holdings snapshot | Closed positions or account activity after positions close |
Best export names
Look for names like Closed Trades, Trade History, Realized P&L, Closed Positions, Trade Confirmations, Executions, Fills, or Activity Statement with realized P&L.
Still not sure?
Use Report Issue from the import modal. It attaches file context, mapping, and import result for support review.
Exchange & Broker Sync
1
Connect a provider
Settings → Exchanges → connect a supported provider with OAuth, token, or read-only API credentials. The exact options shown in Settings are the source of truth for your account.
Always use read-only API keys. TSB never needs withdrawal or trading permissions.
Sync worked if...
Settings shows the provider as connected, sync completes without an error notice, and closed trades appear in Journal under that account or provider label.
If no new trades appear
Most connectors use the provider's trade-history endpoint. If a result looks incomplete, check the provider date range and permission set first.
If the key is rejected
Check read permission, IP whitelist, passphrase, account id, and whether the provider requires futures or trade-history permission. Never enable withdrawal or live trading permission for TSB.
If sync used to work
Refresh OAuth access or recreate the read-only key. Some providers expire keys or revoke permissions after account security changes.
Exchange sync status messages
| Status | Meaning | Next step |
|---|---|---|
| Connected | The credential test passed and the account is ready to sync. | Click Sync once to pull the first closed trades. |
| 0 synced | The connection worked, but there were no new closed trades to add. | Check date range, closed-trade availability, and whether those trades already exist. |
| No new trades found | The provider returned no new importable trades. | Check the date range, provider permissions, or use a historical export for older data. |
| Connection failed | The provider rejected the token, key, passphrase, account id, or permission set. | Recreate read-only credentials and follow the provider guide shown in Settings. |
| Free cap reached | Your free monthly new-trade slots are filled. | Existing matched trades can refresh; upgrade when you want more new trades this month. |
MT4 / MT5 Expert Advisor
1
Download EA
Settings → Exchanges → MT4 / MT5 Auto-Sync → download the ready-to-install .ex4 or .ex5 file.
2
Install & connect
Copy the EA into the correct Experts folder → attach it to any one chart → paste your current EA Token and the Server URL shown in Settings. The EA scans the terminal's loaded account history and keeps syncing automatically.
3
Backfill or force sync
Use Request Sync Now for a quick check, or Backfill Old Trades to rescan 7, 30, 90, or 365 days of older history already loaded in MetaTrader.
What the EA captures
Closed trades, entry and exit prices, size, gross P&L, commission/fee, swap, account currency, SL/TP when MetaTrader exposes them, and partial closes as execution rows inside one trade.
Partial closes
If MetaTrader sends the first closed piece before the whole position is finished, a later sync or backfill can upgrade that early piece into the full aggregated trade instead of creating duplicates.
Delete and restore
Deleting an MT trade in TSB keeps a sync tombstone, so normal sync and backfill do not bring it back by surprise. Use Restore Deleted MT when you intentionally want deleted MT trades restored.
Multiple MT accounts
Each MetaTrader login/server is treated as a separate source and can map into its own TSB account. For simultaneous syncing, run separate terminal instances per MT account.
MT4 / MT5 worked if...
The EA is attached to a chart, WebRequest is allowed, the token matches Settings, and recent MetaTrader history appears in Journal after Request Sync Now or the next EA cycle.
If nothing sends
Check Tools → Options → Expert Advisors, allow WebRequest to
https://app.traderssecondbrain.com, confirm AutoTrading is enabled, and verify the EA token has not been rotated. If old trades are missing
MetaTrader must have that account history loaded locally. Open account history in the terminal first, then use Backfill Old Trades for 7, 30, 90, or 365 days.
If the result looks incomplete
Check that the terminal has the account history loaded locally, then run Request Sync Now or a wider Backfill window. Backfill is also the safest way to repair an early partial-close fragment after the full position has closed.
MT4 / MT5 status messages
| Status or number | Meaning | What to do |
|---|---|---|
| Waiting for EA | TSB has a token, but the terminal has not checked in yet. | Attach the EA to one chart, allow WebRequest, paste token and the Server URL shown in Settings. |
| Last Check | The last heartbeat from the EA. | If this is old, the terminal, EA, AutoTrading, or internet connection is not running. |
| Found / Received | How many terminal records the EA found and sent to TSB. | If found is zero, load more account history inside MetaTrader and backfill again. |
| Synced / Duplicates | How many new trades were saved versus already known trades. | Duplicates are normal after repeat syncs and protect you from double-counting. |
| Upgraded partial MT trades | TSB found an earlier partial-close fragment and replaced it with the complete grouped trade. | No action needed. This is expected after a backfill or repeated sync on partially closed positions. |
| Request Sync Now | Asks the EA to run a quick incremental check. | Use this after setup or after a trade closes. |
| Backfill Old Trades | Asks the EA to rescan an older local history window. | Use this if the terminal was closed, history was not loaded, or old trades are missing. |
Main platform matrix
Configured sync paths are controlled by Settings. File upload means a closed-trade export can be imported through the CSV / TSV / JSON / HTML path. For the public overview, see the supported brokers and integrations page.
| Platform / source | Markets | Connected sync | CSV / export upload | Notes |
|---|---|---|---|---|
| MetaTrader 5 EA |
Forex
Metals
Indices
Commodities
CFDs
|
Yes | Yes | Auto-syncs MetaTrader 5 account history into TSB with trades, fees, P/L, partial closes, account mapping, and recovery tools. |
| MetaTrader 4 EA |
Forex
Metals
Indices
Commodities
CFDs
|
Yes | Yes | Auto-syncs MetaTrader 4 account history into TSB with trades, fees, P/L, partial closes, account mapping, and recovery tools. |
| Interactive Brokers |
Stocks
Options
Futures
Forex
CFDs
|
Yes | Yes | Imports IBKR Flex trade history across stocks, options, futures, forex, and CFDs with executions, fees, currencies, and realized P/L. |
| Binance |
Spot
Futures
|
Yes | CSV path | Syncs Spot and Futures trade history from read-only API keys, including fills, fees, sizes, prices, and realized P/L. |
| Bybit |
Spot
Futures
|
Yes | CSV path | Syncs Spot and Futures trade history from read-only API keys, including fills, fees, sizes, prices, and realized P/L. |
| OKX |
Spot
Futures
|
Yes | CSV path | Syncs Spot and Futures trade history from read-only API keys, including fills, fees, sizes, prices, and realized P/L. |
| Bitget |
Spot
Futures
|
Yes | CSV path | Syncs Spot and Futures trade history from read-only API keys, including fills, fees, sizes, prices, and realized P/L. |
| Gate.io |
Spot
Futures
|
Yes | CSV path | Syncs Gate.io Spot and USDT Futures history from read-only API keys with fills, fees, prices, sizes, and realized P/L. |
| OANDA |
Forex
CFDs
|
Yes | CSV path | Syncs Forex and CFD account history from read-only OANDA tokens with fills, financing, fees, account currency, and P/L. |
| tastytrade |
Stocks
Options
Futures
Crypto
|
No | CSV path | Pilot connector for tastytrade account transactions across stocks, options, futures, and crypto with fees and contract multipliers. |
| Alpaca |
Stocks
Options
Crypto
|
Yes | CSV path | Syncs stocks, options, and crypto activity with fills, shorts, fractional shares, option multipliers, account currency, and P/L. |
| Tradier |
Stocks
Options
|
No | CSV path | Pilot connector for stocks and options account history with fills, commissions, option multipliers, currencies, and gain/loss replay. |
| Tradovate |
Futures
|
No | Yes | Tradovate exports can be imported today. Native OAuth sync stays in pilot while account-history coverage is validated. |
| CSV / TSV / JSON / HTML uploads |
Stocks
Options
Futures
Forex
Crypto
|
No | Yes | Upload broker exports, journal exports, and migration files when they contain closed trades or fill history. |
| Exchange closed-trade exports |
Crypto
|
No | Yes | Upload crypto trade history, closed-position, realized P/L, and account-history exports for exchange workflows. |
| Broker and futures activity reports |
Stocks
Options
Futures
Forex
|
No | Yes | Upload statements, activity reports, execution reports, and futures performance exports for manual import. |
Unlisted brokers can still work through file upload if the export contains closed trades with date, symbol, side, size, and realized P&L.
Minimum data TSB needs
Required to sync
At minimum: a trade date, pair or symbol, and either broker P&L or enough price / size information to reconstruct the result. Without these, TSB cannot place the trade correctly or build reliable analytics.
Strongly recommended
Entry, exit, direction, size, account, and tags enable better filters in Journal, Leak Map, and Backtester.
Journal
Journal is the editable trade table. It stores imported, synced, and manual trades with accounts, executions, screenshots, notes, setup labels, and review fields.
Clean up a trade after import
Play video
Manual trades and edits
Add or close a trade
Manual trades need symbol, side, date, account, and either realized P&L or execution data. Closed status comes from exit data or close date.
Executions
Use executions for multiple entries/exits. For one-fill trades, entry price, exit price, size, and fees are enough.
R:R and stop loss
R:R uses side, average entry, average exit, and stop loss. A manual P&L override does not replace missing risk fields.
BE and custom sessions
Break-even can exclude scratch trades from win/loss logic. Custom session labels feed timing breakdowns beside Asia, London, and New York.
What to log on every trade
Setup and tags
Setup, session, market condition, and mistake tags are exact labels used by filters, Leak Map, Backtester, and Coach context.
Screenshot
Screenshots attach evidence to the trade. HTF/LTF fields may map separately depending on your Notion/database setup.
One-line note
Notes are plain trade context for later review and AI Coach. Keep the reason, invalidation, and post-trade read in the trade record.
Outcome label
Outcome labels separate execution quality from P&L. A profitable trade can still be a rule break.
Simple review workflow
1
Filter the last 20 to 30 trades
Use a date range or count-based slice before changing tags or rules.
2
Open your losers first
Check repeated mistakes, late entries, oversized risk, and missing evidence fields.
3
Compare tag groups
Compare expectancy, profit factor, drawdown, and trade count for each tag.
Tags are case-sensitive labels in practice. Keep names consistent if you want clean setup/session splits.
Analytics
Analytics reads closed trades from the current account scope and date range. Filters include account, setup, session, pair/symbol, side, tag, and result fields.
Dashboard account scope
Play video
Key Metrics
| Metric | What it means | Read it with |
|---|---|---|
| Win Rate | % of trades closed in profit | Average win, average loss, and BE handling |
| Profit Factor | Gross profit ÷ gross loss | Sample size and whether one outlier is carrying results |
| Expectancy | Average money per trade | Account scope, currency, and trade count |
| Avg R:R | Average reward vs planned risk | Stop loss quality and whether R:R was calculated or entered manually |
| Drawdown | Largest peak-to-trough drop | Prop rules, position size, and recovery time |
| Session / setup splits | How results change by timing or playbook tag | Enough trades in each slice before making rules |
How to read the dashboard
Profitability
Expectancy and profit factor summarize realized closed-trade P&L. Check sample size before using them for rules.
Risk
Drawdown depends on account scope, currency conversion, and selected date range.
Execution quality
R:R needs usable stop-loss and execution data. Session/setup splits need enough trades in each bucket.
Behaviour
Behavior and mistake tags become report dimensions when they are applied consistently in Journal.
Weekly review in 10 minutes
Play video
1
Set a clean date range
Review only the current week or last 20 trades. Mixing old and new data hides recent changes.
2
Find one positive bucket
Sort by expectancy, profit factor, drawdown, and trade count.
3
Find one negative bucket
Compare losing buckets by setup, session, account, pair, and mistake tag.
4
Set one rule for next week
Save one rule tied to a measurable filter: setup, session, max trades, risk cap, or account.
Win rate alone is not enough. Read it with average win/loss, BE handling, drawdown, and sample size.
Notion Widgets
Widgets are tokenized embed URLs for Notion. They render selected TSB data without exposing the full app shell.
1
Copy widget link
Dashboard → Widgets → choose widget, account scope, and theme behavior → copy embed URL.
2
Paste in Notion
In Notion, type
/embed, paste the URL, then resize the frame.| Widget | What it does |
|---|---|
| Morning Briefing | Daily market overview + your stats |
| Equity Curve | P&L chart with drawdown |
| Market Sessions | Live session clocks |
| Economic Calendar | Upcoming events with countdowns |
| Position Calculator | Risk-based position sizing |
| Streak Counter | Win/loss streak tracker |
| Market Overview | Live prices |
| AI Insights | AI-generated daily tips |
| News Wall | Market news feed |
| Chart Terminal | TradingView charts |
| Execution Protocol | Pre-trade checklist |
More specialized widgets are available from the Widgets page as your workflow grows.
Strategy Backtester TSB
Backtester runs filters against your saved trade history. It does not create new market data; it recomputes results from included/excluded trades.
1
Set filters
Pick account, date range, setup, session, pair/symbol, day, side, result, and behavior filters.
2
Read results
Read trade count, P&L, win rate, profit factor, drawdown, expectancy, and excluded-trade impact.
3
Run stress test
Use stress tests and prop-firm replay only after the filtered sample has enough trades.
Good questions to test
Best setup
Compare one setup tag against all trades, then check trade count and drawdown.
Best session
Compare default sessions and custom session labels with the same date/account scope.
Exclude mistake labels
Exclude mistake tags or low-conviction labels and compare P&L, drawdown, and trade count.
Stress test survivability
Use Monte Carlo and drawdown checks to estimate sequence risk from the filtered trade sample.
Do not judge tiny slices. Filtered results need enough trades to make the comparison useful.
AI Coach TSB
AI Coach reads selected trade context from your TSB data: account scope, date range, tags, notes, screenshots metadata, review fields, and performance summaries.
1
Open AI Coach
Open AI Coach from the sidebar. It uses the current account/date context when available.
2
Ask or use quick insights
Ask about a specific account, setup, session, date range, or mistake tag for more precise output.
Prompt examples
| Ask this | Returns |
|---|---|
| What patterns do my losing trades share? | A summary of repeated mistakes, weak sessions, tags, or risk behaviour. |
| Which setup performs best and worst? | A ranking of tags or setups by profit factor, expectancy, or consistency. |
| What changed in my last 20 trades? | A trend summary for the selected recent sample. |
| Build me a review plan for next week. | A checklist based on the current trade sample and tags. |
AI Coach output depends on stored trade fields. Empty notes, missing tags, or wrong account scope produce weaker context.
Notion Template Optional
Duplicate the included Notion template, connect TSB charts/widgets, and sync the Trade Journal database with the app.
Setup flow
1
Duplicate the template
Add the included TSB workspace to your own Notion account before editing pages or widgets.
2
Connect TSB charts
Use the free TSB widget embeds for dashboard charts, summaries, sessions, goals, and review surfaces.
3
Sync trades
Connect the Notion database only when you want trades written into Notion beside the app Journal.
Which Notion database should I choose?
The database picker needs the table where each row is one trade. In the updated TSB template this is usually Trade Log. In older templates it may be called Trade Journal or a custom name.
Choose this
Pick the database with trade rows and fields for date, symbol or pair, and P&L. Account, setup, side, entry, and exit make the sync stronger.
Do not choose this
Do not choose a dashboard page, setup library, calendar, goals database, daily notes page, or widget page. TSB needs the trade-row database.
If no databases appear
Reconnect Notion and share the exact page that contains the trade database. Nested databases may require selecting the top-level page in the Notion permission popup.
If you are migrating templates
Connect the older template first, confirm the data in TSB, then move to the updated template flow. Your old Notion page stays as a backup.
Settings
Settings controls profile, accounts, default currency, Notion connection, import mappings, exchange sync, MT4/MT5 tokens, labels, and data tools.
Profile
Profile controls account email, display name, public handle, avatar, and default display currency.
Accounts and currency
Accounts are unlimited labels/records for prop accounts, personal accounts, brokers, and currencies. Single-account views use that account context; All Accounts converts totals into the default display currency.
Notion Connection
See Notion Template → Setup flow for setup steps and Which Notion database should I choose? if the picker is confusing. For Internal Integration: notion.so/my-integrations → create integration → copy token → paste in Settings.
Play video
Moving from the older TSB Notion template
If you already use the older TSB Notion template, you can move into the updated Notion Template without re-entering your trades manually. The migration flow is designed to preserve your trade history inside TSB, then rebuild the new Trade Log from that data.
Play video
1
Connect the older template first
Let TSB read the older template and confirm that your trades, Setup, and Account values look correct inside the app before starting migration.
2
Click “Move to Updated Template”
This keeps your TSB trade data intact, clears only the old Trade Journal binding, and opens the migration path.
3
Reconnect Notion with both templates shared
In the Notion popup, temporarily grant access to both your old Trader’s Second Brain template page and the updated template copy you want to migrate into, then choose the new Trade Log.
4
Save mapping, then run Setup Library + Trade rebuild
Use Migrate Setup Library first, then Push All Trades to New Template. TSB will also auto-create missing setup pages by name when trade relations need them.
What carries over well right now: trades, setup names, setup relations, accounts, and most setup database fields.
Current limitation: images and rich media inside older setup pages may not migrate cleanly yet. If those are important, plan to re-add them manually after the move.
If your older TSB template is already working correctly for your workflow, you can keep using it. The updated template is the recommended path for the latest structure and formulas, but migration is optional.
Field Mapping
Auto-detected after Notion connect. Minimum required: date, pair/symbol, P&L.
If auto-mapping missed a column, select it manually from the dropdown. Click Save → sync starts.
Must-have fields
Date, symbol, and P&L are the minimum. Without them, reporting and chart placement will be incomplete or wrong.
Nice-to-have fields
Direction, entry, exit, size, setup tag, and notes unlock much better filtering, coaching, and backtesting.
Exchange API Keys
Exchanges tab → paste read-only key. Trades sync automatically.
If an exchange connection looks correct but no new trades appear, check whether the key expired or lost read-trades permission. See Exchange sync status messages for the exact meaning of each state.
MT4/MT5
Settings → Exchanges → download the ready-to-install .ex4 or .ex5 EA → attach it to one chart → paste your current EA Token and the Server URL shown in Settings. The EA reads the terminal's loaded closed-trade history, then you can use Request Sync Now or Backfill Old Trades from Settings. Deleted MT trades stay deleted during normal sync/backfill unless you use Restore Deleted MT. If the status panel is unclear, use the MT4 / MT5 status guide.
Disconnect Notion
Danger Zone at the bottom. Removes connection — your Notion data stays untouched. CSV/manual trades preserved.
If TSB Looks Empty
Empty screens usually come from missing closed trades, narrow filters, or missing required fields.
| Screen | What it needs | Fastest fix |
|---|---|---|
| Journal | At least one saved, imported, synced, or manually added trade. | Import a closed-trade file, connect sync, or add one trade manually. |
| Leak Map | Closed trades with setup labels. Starter ranking unlocks after a small tagged sample. | Open Journal and tag 3 recent closed trades with repeatable setup names. |
| Reports | Closed trades inside the selected week, month, year, and account scope. | Switch to All accounts or widen the date period after importing history. |
| Backtester | Trade history that matches your selected filters. | Clear filters first, then filter one setup/session only after enough data exists. |
| AI Coach | Enough recent trade history to produce evidence-backed observations. | Import or sync more closed trades, then ask about a specific account, setup, or date range. |
| Widgets | Notion widget access plus logged-in TSB browser session. | Open TSB in the same browser, refresh Notion, and verify the embed URL. |
First clear filters
Many empty states are caused by account scope, date window, setup filter, or result filter. Before troubleshooting sync, switch to All accounts and All time.
Then add structure
Leak Map needs setup/session/behavior labels to rank useful buckets. Tag a recent winner/loser sample first.
Check closed dates
Most review pages use completed trade history and the closing date. Future-dated rows may not appear until they fall into the selected range.
If sync is involved
Use Sync, Request Sync Now, or Backfill only after confirming the connected source has closed trades available. Re-running sync cannot create data the broker or terminal has not exposed yet.
Troubleshooting
Check these in order:
1. Make sure the Notion integration has access to the correct page (Settings → Connections in Notion)
2. Re-authenticate: Settings → Notion → Disconnect → Connect again
3. Verify your database has the required fields (at minimum: date, pair/symbol, and P&L columns)
4. Check that you're not hitting API rate limits — wait 5 minutes and try again
5. If using a shared database, make sure the TSB integration is added to that specific page
1. Make sure the Notion integration has access to the correct page (Settings → Connections in Notion)
2. Re-authenticate: Settings → Notion → Disconnect → Connect again
3. Verify your database has the required fields (at minimum: date, pair/symbol, and P&L columns)
4. Check that you're not hitting API rate limits — wait 5 minutes and try again
5. If using a shared database, make sure the TSB integration is added to that specific page
Migration is designed to carry over your trade history into the updated Notion Template structure. In most cases, trades, setup names, relations, accounts, and core setup fields come across well. Setup pages may also be auto-created during trade rebuild if they do not already exist in the new template. Images and rich media from older setup pages may still need to be re-added manually.
1. Verify your API key is still active on the exchange
2. Check that the API key has "read trades" permission
3. Go to Settings → Exchanges and click "Sync"
4. Some exchanges expire API keys after 90 days — create a new one if needed
5. If the provider returns no new records, check the selected date range and export availability.
2. Check that the API key has "read trades" permission
3. Go to Settings → Exchanges and click "Sync"
4. Some exchanges expire API keys after 90 days — create a new one if needed
5. If the provider returns no new records, check the selected date range and export availability.
1. Make sure "Allow WebRequest" is enabled in MT4/MT5 options (Tools → Options → Expert Advisors)
2. Add
3. Check the EA is attached to one chart and running
4. Verify the current EA Token in MetaTrader matches the token in TSB Settings
5. Use Request Sync Now for a quick check, or Backfill Old Trades if the terminal was closed for a while and you need to rescan the missing history window
6. If older trades still do not appear, make sure MetaTrader has that account history loaded locally before running backfill again
2. Add
https://app.traderssecondbrain.com to the allowed URLs list3. Check the EA is attached to one chart and running
4. Verify the current EA Token in MetaTrader matches the token in TSB Settings
5. Use Request Sync Now for a quick check, or Backfill Old Trades if the terminal was closed for a while and you need to rescan the missing history window
6. If older trades still do not appear, make sure MetaTrader has that account history loaded locally before running backfill again
1. Make sure your file is UTF-8 encoded (some brokers export in other encodings)
2. Check that the first row contains column headers
3. If the date format is ambiguous, TSB will ask you to confirm DMY or MDY before import
4. If auto-mapping fails, use manual field mapping — click "Edit Mapping" before importing
5. For HTML files (MetaTrader statements), make sure it's the full detailed statement, not the summary. CSV, TSV, JSON, or HTML is still the most reliable upload path.
6. If the file is really a ledger, raw order history, or metadata export, TSB will stop it on purpose instead of building broken trades from non-trade rows.
2. Check that the first row contains column headers
3. If the date format is ambiguous, TSB will ask you to confirm DMY or MDY before import
4. If auto-mapping fails, use manual field mapping — click "Edit Mapping" before importing
5. For HTML files (MetaTrader statements), make sure it's the full detailed statement, not the summary. CSV, TSV, JSON, or HTML is still the most reliable upload path.
6. If the file is really a ledger, raw order history, or metadata export, TSB will stop it on purpose instead of building broken trades from non-trade rows.
1. Make sure you're using the /embed command in Notion (not /bookmark or /link)
2. Check that you're logged into TSB in your browser — widgets require authentication
3. Try refreshing the Notion page or closing and reopening it
4. On Notion iOS/Android, widgets load after a brief delay — give it 3-5 seconds
5. Clear browser cache if the widget shows an old version
2. Check that you're logged into TSB in your browser — widgets require authentication
3. Try refreshing the Notion page or closing and reopening it
4. On Notion iOS/Android, widgets load after a brief delay — give it 3-5 seconds
5. Clear browser cache if the widget shows an old version
1. Check the date filter at the top — it might be set to a specific range
2. Check the account filter — you might be viewing a single account
3. Click the sync/refresh button to force a data reload
4. If using Notion sync, make sure all trades have the required fields filled in
5. Trades without a P&L value are excluded from most charts
2. Check the account filter — you might be viewing a single account
3. Click the sync/refresh button to force a data reload
4. If using Notion sync, make sure all trades have the required fields filled in
5. Trades without a P&L value are excluded from most charts
Frequently Asked Questions
No. TSB full access is a one-time payment. Current full access also includes claimable Notion Template access for the optional workspace layer.
Yes. CSV / TSV / JSON / HTML, MT4/MT5, supported exchange or broker sync, and broker exports work without Notion. Analytics, AI Coach, Backtester, and Prop Tracker use app data.
No. The included Notion Template works on the free Notion plan.
TSB is market-agnostic once the trade history is in. Forex, crypto, stocks, futures, indices, commodities, options, and CFDs can all be analyzed through supported imports or sync paths. Closed-trade exports are the broadest and most reliable path across markets.
Yes. Current full access lets you claim the included Notion Template later. Existing app data stays intact. Template access page: Notion Template access.
Your app data stays in your TSB account. If you use the Notion Template, your notes and template content also stay in your own Notion workspace.
Need Help?
If the guide does not answer it, send the account email and the page or import path you are using.
Email Support
support@traderssecondbrain.com
We typically reply within a few hours.
We typically reply within a few hours.