Skip to content
Advanced • Oddsmaker • Backtesting workflow

Trade Ideas Oddsmaker tutorial: backtest an Alert Window (the right way)

OddsMaker is where most people either level up fast… or accidentally lie to themselves with a pretty backtest.

This guide shows you my workflow to: - run a clean "Backtest Strategy" - interpret what the report is actually saying - tighten the window without turning it into an overfit mess

Disclosure: some links are affiliate links. Learn more.

Risk + not investment advice

This tutorial is about using software. Trading involves substantial risk. Nothing here is a recommendation to buy or sell any security.

Backtests are not predictions

Backtesting can help you understand how a rule set behaved in a specific period. It does not guarantee future results. Treat it like a filter for “maybe worth watching”, not a promise of profit.

Prerequisite

You need an Alert Window you already built (or at least understand). If you don’t, start here: - Alert Window: build a “buy the dip” alert

What you’ll build

  • A repeatable OddsMaker setup (entry / timed exit / risk / advanced tabs)
  • A simple checklist for interpreting results
  • A “tighten the window” loop (reduce junk alerts without curve-fitting)

Step 1 — Add a “Time of Day” filter (reduce noise)

Before backtesting, I like to restrict the window to the part of the day I actually trade/watch.

Example workflow: - Add Time of Day - Set the window to focus on the early session (use values that match your routine)

Add Time of Day filter before backtesting

Step 2 — Open OddsMaker (“Backtest Strategy”)

In your Alert Window: - Right-click the window - Choose Backtest Strategy

Right click Alert Window and choose Backtest Strategy

Step 3 — Entry tab (start/end time)

On the Entry tab: - Make sure your start/end times match your Time of Day filter (or match the session you care about)

OddsMaker Entry tab configuration

Step 4 — Timed Exit tab (keep it simple first)

When you’re learning, keep exits simple so you can isolate whether the alert/filter logic makes sense.

Example: - time-based exit (e.g., X minutes after entry)

OddsMaker Timed Exit configuration

Step 5 — Risk Management tab (define stop/target)

Set a stop and target that match the idea you’re testing.

Keep it basic: - one stop concept - one target concept - no fancy trailing logic at first

OddsMaker Risk Management configuration

Step 6 — Advanced tab (test window + “use all available columns”)

On Advanced: - choose a test period that gives you a decent sample - enable “Use all available columns” (this gives OddsMaker more to analyze)

OddsMaker Advanced tab configuration

Step 7 — Run it, then read the results like a grown-up

First run is often ugly. That’s normal.

What you're looking for on the first pass: - Do you have enough trades to learn anything? - Are losses coming from the same "type" of symbol (illiquid, ETF-ish, weird float, etc.)? - Does the strategy only "work" because of a couple of huge outliers?

What I check first (in this order)

  1. Trade count / sample size: if it's tiny, you're not learning - widen your lane or test longer.
  2. Equity curve shape: smooth-ish beats "all gains from one day".
  3. Average win vs average loss: if average losses are outsized, tighten the lane before touching entries.
  4. Outliers: one monster winner (or loser) can distort the entire impression.
  5. Regime dependence: if it only works in one market tape, treat it as fragile.

OddsMaker first results

OddsMaker results view (zoom): key metrics and trade count

OddsMaker results view (zoom): where to drill into worst trades/symbols

Step 8 - First fixes (my default checklist)

1) Remove ETFs (common quick win)

One practical trick many traders use is filtering ETFs with EPS $ (not perfect, but it can help).

If you use this approach: - treat it as a rough filter (some symbols won't have EPS data) - validate it by checking the worst symbols list (Step 10)

2) Fix liquidity first

Before you start “optimizing”, tighten the window using liquidity constraints (Dollar Volume, Avg Daily Volume, etc.).

3) Then tighten the lane

Use price/float constraints so the symbols behave more consistently.

Step 9 — Improve the window without overfitting

This is the loop: 1. Identify the worst trades (or worst symbols) 2. Ask: “Would I manually take this setup?” 3. Add one filter/constraint to remove that category 4. Re-run the test

If you keep changing 10 things at once, you'll "optimize" your way into nonsense.

OddsMaker improved results

Step 10 - Use the "worst trades" view to find what to filter (without guessing)

OddsMaker becomes useful when you stop staring at aggregate stats and start looking at what's actually hurting you.

Workflow: 1. Open the tab/view that lists trades or symbols (depending on how you like to diagnose). 2. Sort by worst performers. 3. Pick 5-10 names and ask: what do these have in common? 4. Add one constraint to remove that category (lane first: liquidity, price, float). 5. Re-run. Repeat.

This is where "mentor style" matters: you're not trying to engineer a perfect backtest - you're trying to remove obviously bad fits so the window becomes usable.

Step 11 - Don't forget exclusion lists

Sometimes you'll find one ticker that repeatedly shows up as a problem (or an ETF that slips through).

Instead of building a fragile filter to handle one name, use an exclusion list: - create a "blacklist" for repeat offenders - optionally create a "do-not-trade" list for symbols that don't fit your style (e.g., ultra-thin, constant halts, etc.)

Exclusion lists are also a good way to keep your core logic clean while you learn what you personally want to avoid.

What to watch out for (this saves you money)

  • Tiny sample size: a handful of trades means you learned nothing.
  • Regime dependence: what works in one market can fail in another.
  • Curve-fitting: if it only works with super specific values, it probably won't travel well.
  • Outliers: one monster winner can make a strategy look “amazing”.

FAQ

What is Trade Ideas OddsMaker?

OddsMaker is Trade Ideas’ backtesting workflow (“Backtest Strategy”) that helps you evaluate how an Alert Window strategy behaved over a historical period.

Does a good backtest mean it will work live?

No. Backtesting can be useful, but it doesn’t guarantee future results. Use it to filter ideas and understand behavior, then validate carefully.

How do I avoid overfitting in OddsMaker?

Change one thing at a time, prioritize liquidity and lane constraints first, and be skeptical of results that depend on very specific parameter values.

Next

Disclosure: some links are affiliate links. Learn more.




Next step

Turn this into a repeatable workflow

If you only do one thing next, tighten your lane and reduce noise. That's how Trade Ideas becomes usable.


David
Written by
Updated 2026-01-06 Last tested 2026-01-06
Mentor-style Trade Ideas tutorials focused on workflow, clarity, and repeatable process.