Manual logging is honest — and slow. If you already execute on Delta Exchange India or Shark Exchange, your fills exist on the broker. A journal should import that history and actual P&L so you can review performance without CSV exports or spreadsheet formulas. Add R later only when you want risk-normalized analysis.
This guide covers the full workflow: which journal to import into, how to connect API keys safely, how Delta Exchange and Shark Exchange differ, how INR conversion works, how to avoid duplicate rows, and what to do after import so the data actually improves your expectancy. Full broker list: supported brokers.
Why import beats CSV (and memory)
Crypto futures sessions run around the clock. Batch-logging on Sunday drops scratches, fees, and the exact sequence of a tilt cluster. Broker import pulls fills for a date range you choose, including trades you would rather forget. Those are usually the ones that change expectancy.
- No spreadsheet export or column mapping
- Re-import the same range without duplicate trades
- PnL lands in INR so overview, diary, and tags stay consistent
- Imported rows use the same analytics as trades you log by hand
Step 1 — Create the right journal first
Do not dump every exchange into one catch-all book. Expectancy is only meaningful when the sample shares a strategy or session. Create (or pick) a journal named after the edge you are testing — for example “Delta BTC trend” or “Shark ORB scalps” — and write three rules in the description: entry trigger, invalidation, and when you will not trade.
Step 2 — Connect the broker with a limited key
In Traderizz, open Brokers after sign-in. You will see Delta Exchange India and Shark Exchange. Use an API key and secret from the exchange. Prefer a read-capable or trade-history key when the broker offers one — import only needs history, not order placement.
Delta Exchange India
- Create an API key in your Delta India account with permission to read trade / fill history.
- If Delta asks for an IP whitelist, add the server IP shown in the connection error — whitelist errors are IP, not a bad signature.
- Paste key and secret into Traderizz → Brokers → Delta Exchange India → Connect.
- Pick the journal and a date range, then import. PnL is stored in INR.
Shark Exchange
- Create a read-capable Shark API key and secret.
- Connect Shark Exchange in Traderizz Brokers.
- Import trade history for today, yesterday, last 7 days, or a custom range.
- USDT PnL and fees convert to INR using Shark’s live rate; prices stay in quote units.
You can disconnect either broker anytime. Keys are stored only for your account so Traderizz can sync fills — they are not used to trade on your behalf.
Step 3 — Import a range, then re-import safely
After a session, import today or yesterday. After a week away, use last 7 days or a custom from/to. Re-importing the same range updates existing trades and only adds new fills — you do not get duplicate rows if you sync twice.
- Today / yesterday — daily habit after the session
- Last 7 days — Sunday catch-up
- Custom range — backfill a month when you first connect
Step 4 — Tag and note after import (do not skip this)
Broker fills give you prices, size, fees, and PnL. They do not know your setup name or whether you followed the plan. After import, open the journal and add the fields that make review useful:
- One primary setup tag per trade (breakout, VWAP fade, news fade — keep 3–5 tags max)
- A mistake tag when you broke rules (revenge, size creep, late entry)
- A one-line note if execution differed from the plan
- Screenshots only when the note is not enough
If you import without tags, overview still shows total R and win rate — but you cannot see which pattern paid. Ten minutes of tagging after import is cheaper than another month of mixed, unlabelled crypto futures. Follow the trade tags and setup analytics guide to keep setup, context, and mistake labels consistent.
Step 5 — Review imported P&L, then add R when useful
Start with the actual P&L imported by the exchange. If leverage or changing position size makes cash results hard to compare, define 1R as the cash you planned to lose at invalidation and add the R result during review. The trading diary calendar shows which days clustered red after a liquidation scare or funding print—journal those losing clusters instead of deleting them.
Fees matter more on crypto futures than on many FX books. Imported fee conversion (Shark USDT → INR; Delta PnL in INR) keeps profit factor honest. If a scalp tag is +0.15R before fees and flat after, the journal is doing its job — stop taking that scalp or widen the edge.
Common import mistakes
- Importing both exchanges into one journal when strategies differ
- Using a full-trade API key when a read-only key exists
- Skipping tags so every BTC fill looks the same in analytics
- Judging a setup after 8 imported trades (wait for ~30+ per tag)
- Deleting losing imports — that hides the R cost of tilt
- Changing 1R definition mid-sample without noting it
How Traderizz helps
[Traderizz](/) supports broker integration for Delta Exchange India and Shark Exchange. Connect keys under Brokers, import fills and P&L into a private trading journal, and review with overview, trader diary, tags, and Edge. Add R to a trade only when you want risk-normalized comparison. See supported brokers for the current list.
Sign in with Google, create one journal, connect one broker, and import yesterday. Then tag the session and review the actual P&L. That is the whole loop—import, label, review.