Deal versus position
History can include failed fill attempts. Check deal status and actual filled quantity, then preserve deal and position identifiers. Do not count a parent position and its executions twice.
cTrader trade review
Use cTrader’s account history and native analytics to establish what happened. Add your setup, decision process and review notes in Pineify when the record fits its manual Journal workflow.
Pineify import status: Import History is marked Coming Soon. This guide covers manual records, not a cTrader importer or an Open API connection.
cTrader’s History documentation explains deal records and account statements, including CSV saving. The Windows Analyze documentation covers profitability, profit factor, balance drawdown and symbol analysis. These native reports are useful reconciliation evidence.
A journal serves a different review task: preserving what you intended, whether you followed the plan and what you want to investigate next. Avoid replacing the broker’s statement with a reconstructed log before you have checked that the totals agree.
History can include failed fill attempts. Check deal status and actual filled quantity, then preserve deal and position identifiers. Do not count a parent position and its executions twice.
Check whether the source displays units or lots. Preserve the symbol specification before mapping quantity into a generic journal.
Keep gross result, commissions, swaps and other charges separate. Broker and account terms determine costs; a platform name does not establish one fee model.
Compare totals in the same account currency and retain any conversion assumptions. A price change in quote currency is not automatically an account-currency profit.
Keep the original time zone and identify whether a report selects opening or closing activity. Use the same period for comparisons.
Label your own cBot or manual trades consistently and retain the bot version or setup rules. A label helps review records but does not establish causation or risk-adjusted superiority.
Pineify’s Journal is not a substitute for contract specifications or a broker statement. If a record’s units, swaps or currency treatment cannot be represented, retain it externally and document the limitation instead of claiming a reconciled result.
Use History in Trade Watch, select the relevant period and open Statement. The official cTrader History documentation describes saving the statement as CSV. Confirm the controls in your desktop or web version and keep the original statement.
Pineify does not currently provide a cTrader CSV parser. Import History is marked Coming Soon. Use manual entry for compatible records and reconcile them before relying on aggregate results.
Yes. cTrader Analyze includes performance statistics, profit factor, profitability, balance drawdown and symbol-level information, with available views depending on the platform. A separate journal should add useful review context rather than claim these native capabilities do not exist.
No. Entering records manually does not require granting Pineify access to your cTrader account. That is different from an active integration, and it is not a blanket guarantee about the privacy of exported files or account-based Journal storage.
Pineify supports tags, setups and notes that you can use for your own classification. It does not automatically detect cBots from a cTrader account or certify that an automated strategy outperforms a manual one.
Do not assume dedicated cTrader swap import, lot conversion or every CFD contract specification is supported. Check quantity, currency and fee definitions on a small sample. A financing amount saved only in notes is not automatically included in calculated P&L.
Explore Pineify’s Journal and current account access. Review statistics describe the supplied data and do not guarantee better execution or future returns.
Published by Pineify, which sells trading software. Platform steps are based on the linked official documentation; no live cTrader account export or third-party import was tested for this guide.