Turn Your PokerTracker Database
Into an Improvement Plan
Keep PokerTracker. This is a performance layer on top of the database you already built — not a replacement HUD.
Keep PokerTracker. Add a performance layer.
REQUEST EARLY ACCESS · ALPHA IN PREPARATION
REQUEST EARLY ACCESS · ALPHA IN PREPARATION
Post-session analysis only. No real-time assistance.
PokerTracker already has the data
The problem is not lack of data. PokerTracker already tracks, stores, filters, and reports. The hard part is deciding which part of that database deserves study time.
- HANDSThe history you already collect.
- SESSIONSPlay, not a single interesting spot.
- POSITIONSWhere the decisions happened.
- STATSFrequencies useful for triage.
- FILTERSA way to look closer — not a verdict.
Those objects stay useful. This page is not an argument for replacing them.
The difficult part is deciding what deserves attention
Aggregate reports answer a different question from a coaching review. A tracker can measure many things. The performance layer narrows attention.
Separate example from the sample review below.
TRACKER OUTPUT
- VPIP21.3%
- PFR16.9%
- 3BET7.6%
- FOLD TO 3BET55.0%
- CBET75.1%
- WTSD28.5%
- bb/100−1.10
THE OPEN QUESTION
What should I fix first?
COACHING OUTPUT
- PRIORITY #1
- PRIORITY #2
- PRIORITY #3
A long stats list is not a study plan. The next useful object is a short, evidenced priority list.
A tracker stat is a frequency. A review asks what built it.
A number such as Fold to 3Bet is useful because it tells you where to look. It does not tell you which decisions created the frequency, or whether those decisions are costing EV.
TRACKER OUTPUT
FOLD TO 3BET
55.0%
What is the frequency?
ADDED LAYER
What decisions built that frequency?
NOT VISIBLE IN THE AGGREGATE
- Position
- Hand class
- Opponent action
- Stack context
- The actual hand decisions
This is context, not a leak. An aggregate frequency is a triage signal until the hands underneath it are inspected.
From PokerTracker stats to actual decision patterns
The intended path starts in the tracker you already use. A signal becomes a filtered hand set, then representative decisions, then a repeating pattern with evidence — or a refusal.
- PT4 SIGNAL
- FILTER / HAND SET
- REPRESENTATIVE DECISIONS
- REPEATING PATTERN
- EVIDENCE / CONFIDENCE
- PRIORITY
Recurrence is not automatically a leak. Confidence and estimated impact still have to support a study target.
What data we use
Designed for PokerTracker 4 exports and hand histories. Aggregate stats help triage. Hand-level decisions are what a claim can be verified against.
- PT4PT4 EXPORT
Aggregate context and tracker data for triage.
Use exports and hand histories from the database you already collect in PT4.
CSV · XML - HHHAND HISTORIES
Decision-level evidence.
Required to inspect the hands underneath a frequency.
TXT · ZIP - CTXSAMPLE / CONTEXT
Confidence is per finding.
Opportunity count in the actual spot matters more than one database-wide verdict.
PER FINDING
The current Analyze preview only checks whether the selected file type looks supported. It does not parse or analyze the file yet. That is weaker than claiming every PT4 export version is compatible.
NOT CLAIMED
- A direct tracker database connection
- Automatic PT4 sync
- A PokerTracker API
- Official affiliation or partnership
How analysis works
This is a post-session workflow, not a live progress indicator. Nothing here implies a running backend on this page.
- 01EXPORT
Export from the PT4 database you already built.
- 02TRIAGE
Stats show where to look.
- 03FILTER
Get to the relevant hand set.
- 04VERIFY
Inspect representative decisions.
- 05PRIORITIZE
Keep only material, evidenced targets.
- 06TRAIN
Study the repeating spot — not every hand.
- 07RE-MEASURE
Check the same filter on new hands.
Example PokerTracker review
This is an illustrative PokerTracker 4 review, not customer data and not a live result from this page.
- HANDS84,281PT4
- CANDIDATES12
- EVIDENCED6
- PRIORITIES3
River Bluff Catching
−0.47 bb/100
RELEVANT DECISIONS
186
of 412 opportunities
HIGH CONFIDENCE
UTG open frequency
Turn probes in position
37 opportunities
Different layers. Complementary jobs.
PokerTracker’s primary job is to track, store, and report. Poker Performance Coach’s primary job is to interpret what deserves attention next.
POKERTRACKER
Tracks, stores, and reports.
- Collect hand history
- Keep the database
- Aggregate statistics
- Filters and reports
POKER PERFORMANCE COACH
Interprets and prioritizes.
- Candidate patterns
- Evidence and confidence
- Estimated impact
- Study priority
- Re-measurement
Where the products can overlap, this page names focus — not a claim that PokerTracker cannot analyze poker.
No need to replace PokerTracker
Keep your tracker. There is no new HUD workflow. Use the data you already collect, then add a review and coaching layer.
- Keep PokerTracker
- No replacement HUD
- Use the export you already have
- Add a performance layer
Export and analyze
Choose PokerTracker 4 on Analyze. Follow the export guide. Select a supported export or hand-history file.
Export from PokerTracker 4
You do not need to move or replace your PT4 database.
- Open PokerTracker 4.
- Select the player and database you want reviewed.
- Export the relevant hand-history or report data.
- Save the export locally.
- Return here and select the file.
The current Analyze preview only checks whether the selected file type looks supported. It does not parse or analyze the file yet. The selected file stays on this device during the current preview.
See what a complete PT4 database review should return
The more transactional next page: review scope, deliverables, confidence, and follow-up.
PT4 LEAK ANALYSISSee how stats become candidate decision leaks
The leak-specific page: statistical leak versus decision leak, composition, and verification.
HOW TO ANALYZESee the educational path
How a poker database is reviewed without turning every frequency into a verdict.
SAMPLE REPORTSee the illustrated PT4 review
The sample report is the proof object: priorities, refusal states, and representative decisions.
Keep PokerTracker.
Add a coaching layer.
Turn the database you already built into a short study plan.
REQUEST EARLY ACCESS · ALPHA IN PREPARATION
Post-session analysis only. No real-time assistance.