Tags, Widgets & Dashboard Metrics

Dashboard widgets show the numbers you see first when you log in: today’s P&L, win rate, trade count, discipline or Quants-style scores. Trade tags turn subjective labels — “A-setup,” “expiry fade,” “revenge” — into rows in a report that you can rank by net P&L and expectancy. Used badly, widgets become mood amplifiers; used with a controlled tag vocabulary and a fixed review calendar, they become the fastest path from raw NSE fills to a single weekly decision. This guide covers how to design tags for Indian trading books, interpret widget metrics without overreacting, and wire both into TradeLyser alongside Reports & metrics and the methodology strategies pillar.

Tags are data fields, not sticky notes

A tag attached to every relevant trade lets you answer: which setup actually pays after brokerage on Nifty and Bank Nifty? which mistakes correlate with largest losses? which session context — opening drive vs midday chop — deserves smaller size? Tags fail when traders create forty names, use twelve inconsistently, and leave half of trades untagged. Cap live tags at roughly ten to fifteen you will apply on every qualifying trade. Freeze the list monthly; add new tags only after retiring unused ones.

Separate strategy tags (playbook identity) from context tags (expiry, news, revenge, A vs B setup). Strategy tags map to Strategies pillar — one tag per edge you want measured. Context tags explain variance inside the strategy. Mixing both into one label like “Nifty-scalp-revenge-expiry” destroys clean strategy stats. Use two fields where the product allows, or a consistent prefix convention your reports can filter.

Building a tag vocabulary for NSE books

• Strategy: OR-breakout-nifty, weekly-iron-condor, swing-20ema — one per playbook.
• Setup quality: A-setup, B-setup, unplanned — compare win rate and expectancy.
• Behaviour: revenge, FOMO, boredom-trade — cut what fails the data test.
• Session: open-15m, midday, last-hour — critical for index scalpers.
• Event: budget-week, RBI-day, expiry-Thursday — explain outliers honestly.

Run tag performance monthly: net P&L, trade count, expectancy (Expectancy), profit factor (Profit Factor) per tag. Retire tags with persistent negative expectancy after thirty or more trades unless you are deliberately testing a rewrite in sim. The win rate glossary (Win Rate) reminds you to pair hit rate with payoff — tag dashboards that only sort by win rate mislead options sellers with fat-tail risk.

Widgets vs reports: snapshots vs autopsy

Widgets are snapshots for a chosen date filter — often today, this week, or this month. They answer “where am I right now?” Reports answer “why?” with exportable tables, symbol splits, and tag breakdowns. Never promote a widget number to a strategy decision without opening the matching report. A green P&L widget on expiry Thursday can hide a broken rule on three of five trades; a red widget on a low-trade Tuesday can be noise.

Align widget filters with your review window

Misaligned filters cause false alarms. If your weekly review compares Monday–Friday sessions, set widgets to the same range before glancing — not “today only” on a slow Wednesday. For multi-account or multi-broker setups common among Indian traders (Zerodha plus Angel for backup), confirm widget scope includes the account you actually traded. After auto-sync (Auto-sync), refresh before reading — stale widgets have caused unnecessary size cuts.

Worked example: Meera’s tag and widget review

Meera trades Bank Nifty options with three strategy tags and two behaviour tags. Friday routine: she sets dashboard to “this week” and scans P&L widget — slightly green. Win rate widget shows 62%, above her 55% baseline. Discipline score dipped on Wednesday. She opens Reports & Metrics (Reports & metrics), filters by week, sorts tags by net P&L.

Finding: “range-iron-condor” tag +₹14,200 on eight trades; “open-breakout” tag −₹9,800 on six trades with three marked revenge in notes. Widget win rate looked fine because condor wins dominated count. Tag-level expectancy shows breakout tag negative for third consecutive week. Widget alone suggested “good week”; tag report drove the decision: pause open-breakout live for two weeks, sim only, while keeping condor tag at planned size. One change, written in journal per Weekly review — not a dashboard panic.

Daily, weekly, and monthly dashboard rhythm

• Monday pre-open: widget glance — P&L cap reminder, no strategy changes.
• Post-close daily (optional): trade count vs max-trades rule, discipline flag only.
• Friday weekly: widgets plus full tag and symbol reports — one process change.
• Month-end: export widget ranges archived with CSV reports for coaching or CA.

The insights methodology page (Insights pillar) recommends reading expectancy per tag before touching indicators — widgets sit earlier in the funnel as alarms, not conclusions. Pair widget trends with AI analytics (AI analytics) only after tags are clean; Elysia summaries on untagged books amplify garbage.

Tag hygiene and untagged trade audits

Untagged trades poison tag analytics. Weekly rule: if untagged closed trades exceed 10% of volume, stop reviewing performance and fix tagging first. Batch-tag from broker notes where possible; use consistent spelling — “expiry” and “Expiry” split samples. For partial exits on NSE, follow one policy (single trade vs multiple legs) documented in your notebook and applied before comparing tag win rates month over month.

Indian context: tags for costs, expiry, and symbols

Scalpers should tag high-fee days when STT and brokerage exceed 20% of gross — widget P&L can look flat while fee tag explains bleed. Expiry tags separate Thursday gamma from ordinary Wednesdays. Symbol tags or reliance on symbol reports prevents one Reliance or HDFC Bank trend trade from masking weak mid-cap experiments. Budget and election weeks get event tags so widget spikes are not mistaken for skill upgrades.

TradeLyser workflow: tags, widgets, reports together

Onboarding: define strategy tags in Strategy Board (Strategy Board), link to rules in Rules pillar. Daily: sync trades, apply tags before end of session. Login: widgets for cap and count only — no tag edits from mood. Friday: set widget range to week; note P&L, win rate, discipline trend; open reports for tag ranking, symbol top five, largest losers with journal cross-check. Document one change. Monthly: prune tag list, compare tag expectancy to prior quarter, adjust capital allocation.

Common tag and widget mistakes

• Creating a new tag after every loss instead of using mistake log fields.
• Checking P&L widget every fifteen minutes — provokes early exits and revenge.
• Trusting win rate widget without payoff ratio on options books.
• Mixing demo and live on the same tag filters — keep sim tags separate.
• Changing dashboard date range to maximise green before screenshots.
• Letting AI scores override negative tag expectancy without opening trades.
• Forty-tag taxonomy where each tag has three trades — no statistical power.

Designing a minimal dashboard layout

Pick three widgets maximum for daily glance: net P&L this week, closed trade count, discipline or adherence proxy. Hide win rate from the daily view if it triggers early exits — keep win rate for Friday tag reports where sample size is meaningful. Pin strategy tag filter to your core playbook so widgets reflect edge, not experimental noise. Change layout monthly at most; dashboard churn is procrastination dressed as optimisation.

Tag lifecycle: create, test, promote, retire

New tags start in research bucket with capped rupee risk and explicit end date for evaluation. After minimum sample and positive rolling expectancy, promote to core dashboard filter. Retire tags with persistent negative expectancy — keep them in history for quarterly audit but remove from active dropdown to prevent nostalgic re-use after one lucky expiry. Document promote/retire dates in journal so widget trends remain interpretable.

Widget alerts should never create new tags mid-week — they should send you to reports on existing tags. If a widget spikes trade count, open the impulsive or untagged bucket in reports before inventing “Tuesday-scalp-v2.”

Friday report ritual: rank tags by net P&L and expectancy, then rank by violation count if discipline fields exist. If top P&L tag has rising violations, widgets are lying kindly — fix behaviour before celebrating green.

Closing: widgets alert, tags explain, reports decide

Set your dashboard to this week, write down the three widget numbers you actually use — P&L, trade count, discipline — and ignore the rest until Friday. Then run tag performance for your top two strategy tags and compare expectancy to last month. If widgets say “fine” but a tag says “bleeding,” trust the tag. That single habit separates traders who react to colours from traders who run a book like a small business on NSE. Tags turn language into math; widgets tell you when to open the spreadsheet; reports tell you what to change next week.

Audit your tag list this month: retire any tag with fewer than fifteen trades unless it is an active research experiment with an end date. Statistical power beats taxonomy pride.

Name your three widgets aloud on Friday before opening reports — if you cannot remember them, your dashboard is too crowded. Simplicity is a risk control on volatile NSE sessions.