Good habits

A Trading Journal for Bot Sessions

Automated sessions produce details you will not remember later: which settings were on, what happened, why the bot paused. A simple journal turns a blurry week into something you can review and compare.

Why journal automated sessions

  • You cannot judge settings from memory. Without records you cannot tell whether a settings change helped or just coincided with a lucky or unlucky stretch.
  • A losing streak is information. A journal shows whether it came from one pair, one timeframe, or plain variance.
  • Problems need evidence. If a result or a stake looks wrong, a timestamped record of settings, stakes, results and pauses is the fastest way to diagnose it — and to get help from support.
  • It keeps expectations honest. Your own logged wins, losses and paused cycles beat hindsight.

What to record per trade

  1. Date and time the trade was placed.
  2. Market / pair.
  3. Direction (up / down).
  4. Timeframe (trade expiry).
  5. Stake.
  6. Payout shown at entry.
  7. Martingale position: which trade of the cycle it was (1, 2, 3…), the multiplier (2x to 3x) and the Steps value set in the panel.
  8. Result (win or loss).
  9. Balance before and after.
  10. Mode: Martingale or Avalisa Bot (Pro only).
  11. Notes: anything unusual — pauses, a minimised tab, connection problems.

The dashboard shows your trade history (basic on Demo, fuller on paid plans); copy what you need into your own journal. What no tool records for you is why — the notes column is yours.

What to record per session

  • Settings snapshot at the start: mode, timeframe, Minimum payout %, Pair Scan, multiplier and the Steps value set in the panel. Change one thing at a time between sessions, or the journal cannot tell you what made the difference. The full list is in the settings guide.
  • Account type: demo or real — never mix them in one review.
  • Environment: was the Pocket Option tab visible the whole time? A background or minimised tab can delay trade-result detection.
  • Pauses: when and why the bot stopped — for example, the next stake would have exceeded the balance.
  • Totals: trades, wins, losses, net change, longest losing streak.

The cost of a Martingale losing cycle

Martingale raises the stake by your multiplier after each loss, so a losing cycle costs far more than its first trade. Steps = N allows N + 1 trades in a losing cycle; at 2x, Steps 3 costs 15 times the base stake. There is no separate stop-loss or daily-loss-limit setting — limiting Steps is the cap. That is why every session entry records the Steps value: it is your worst-case cost per cycle. Try your numbers in the Martingale calculator.

Practical steps

  1. Start on a demo account and build the habit with no money at risk — see how to test a trading bot on demo.
  2. Copy history into the journal after every session, not when it “feels done”.
  3. Log every settings change: date, what changed, from what to what.
  4. Review weekly. Compare each settings combination with the break-even win rate for its payout, 1 / (1 + p) — explained in honest win rates and break-even. A combination below break-even is the journal doing its job.

Risk statement

Binary options are high risk, and a system that multiplies stakes after losses can lose more than you expect. Use only money you can afford to lose. Trading involves risk. Avalisa does not guarantee profits. Start on a demo account.

Frequently asked questions

Do I need a paid plan to keep a journal?

No. The free Demo plan includes basic trade history, which is enough to learn the habit. The free Demo plan includes 10 Martingale trades. Basic is $69 one-time; Pro is $119 one-time or $29/month (a recurring subscription) — you choose at checkout on pricing.

What if I can’t tell why the bot paused?

Write down what you suspect at the time and mark it with a question mark. An unconfirmed note beats a confidently invented reason.

Can a journal predict whether a settings change will work?

No. It measures what already happened; it is your history, not a forecast.

How detailed does it need to be?

Enough that someone else could reconstruct the session: settings snapshot, copied history, interruptions and totals.

Start your first logged session on demo

Install Avalisa PO Bot from the Chrome Web Store, follow the setup guide, and keep every session journaled from the first demo run.

Next reads: Free Pro access when you open a new Pocket Option account through our link · Moving from a demo to a real account: the checklist

Related guides: Pocket Option Withdrawals: Do Trading Bots Affect Them? · Pocket Option Bot Listings on the Chrome Web Store · Execution Delay in a Browser Trading Bot: What It Means