Connecting a provider registers data access; synchronising asks Ufficio to import the data. They are separate actions.
Goal — Obtain an imported sample and show that it matches the original history before reading P&L, equity or the report card.
Documentation boundary — This guide covers the request, wait and visible result. Frequencies, queues, mappings and internal procedures may evolve and are not presented as guaranteed rules.
Start manual synchronisation
- Sign in and confirm that the provider is listed as connected.
- Open Analytics from the sidebar or bottom navigation.
- Find Synchronise on the Analytics page. The Dashboard does not expose the same command.
- If several providers are connected, check which one you are updating.
- Start the request once and wait for its result. Repeated clicks do not deepen history and may encounter provider limits.
- Return to the Dashboard or refresh the view only after completion.
Ufficio also runs periodic background processes. Saving a key does not imply immediate import; queues, rate limits and provider history windows may introduce delays.
Reconcile a sample
Open several closed trades and compare them with the original source. Check symbol and market, long or short side, time and timezone, quantity or position value, available entry and exit prices, P&L, fees, funding and rebates when supplied separately.
Start from one trade, then inspect the total. A different aggregate does not identify which field caused the discrepancy.
Missing data and zero
0 is a value only when the field is present and its source and mapping support a zero. A blank, dash, loading state or period without rows may instead mean that no data was received. Do not turn absence into zero performance.
Observable result
Synchronisation is usable when the table shows the new trades, the request is no longer running, and the sample matches under the declared conventions. Only then move to Dashboard and Analytics.
Sources
- Ufficio Analytics — manual synchronisation surface.
- Connect a provider — data-access prerequisite.
- Cyclepedia technical verification: check on 2026-08-25 of the Analytics sync control, trade loading, profile filters and missing-versus-zero distinction.