How synchronization works
PartnerKits captures source records in the background. A new sync prioritizes recent data before moving through the older history selected during setup. You do not need to keep Overview open for the sync to continue.
Saving a Partner connection and starting an app sync are separate actions. Use Data sync for the selected app to inspect its progress.
Smart updates
Your first import defaults to the last 90 days. Choose all available history or a custom start date if needed. Recent income becomes available first; older history continues separately.
After your first sync, PartnerKits schedules updates automatically:
| Data | Typical cadence |
|---|---|
| Recent income and merchant events | About every 30 minutes for recently viewed apps; every 4 hours for inactive apps |
| Current metered usage | Every 2–6 hours, rotating through known customers |
| Other active subscriptions | Daily |
| Customers without an active managed-pricing contract | Weekly, or sooner after new merchant events |
All updates run as background jobs. Timing depends on the app's size, pending work and shared API capacity. Opening a dashboard shows cached data immediately and can request a background update when stale. It does not wait for Shopify.
In Data sync, use Sync recent data, Pause automatic updates or Resume automatic updates. Manual requests are coalesced and have a short cooldown. Pausing prevents new automatic work; jobs already in progress can finish. Resuming after a long pause fills missed periods independently of fresh income updates.
Recent updates continue from the last complete source capture with a 30-minute overlap. Without a complete capture checkpoint, they recheck the previous 48 hours. Daily and weekly reconciliation revisit the last 7 and 30 days to recover delayed records; overlapping due windows share the widest eligible job.
Customer discovery and current usage
Older installation records are scanned separately to discover shops outside your chosen income-history range. This does not import their full financial history. Subscription progress covers known customers, not a guarantee that all historical shops have been discovered.
Current contract and usage data are fetched together, with one job per app/shop pair. Previously captured amounts stay visible during a refresh. Check their capture timestamp; unbilled costs are provisional and current-cycle snapshots cannot reconstruct all historical usage.
Read the current status
| State | What to do |
|---|---|
| Not connected | Complete app details, save your Partner connection and start a first sync |
| Queued or running | Let the background work continue and check the progress view |
| Partial coverage | Review which periods or streams are missing before interpreting totals |
| Paused or error | Review the reported issue, check credentials and use the available retry action |
| Synced | Review the captured period and individual metric notes; this is not a guarantee that the source exposes every possible business record |
Missing is different from zero
A value of zero can be meaningful when the source has been checked for the relevant period. A dash means that PartnerKits cannot produce a value from the current evidence.
Charts preserve missing intervals rather than drawing a continuous line across them. Some metrics, such as recurring subscription state, require evidence beyond transaction totals and may remain unavailable while that state is incomplete.
Review an issue
Open the sync view from the top bar or Settings → Data sync. Review the source, affected period and access issue shown there. If credentials changed, update the saved Partner connection before retrying.
Recent merchant events and detailed reports help you check the business context, but they do not prove full historical coverage on their own.
Historical availability
The selected history start date controls the requested range. The actual history available still depends on the source, permissions and captured records. A completed job should be read alongside its coverage information.
Future traffic coverage
Google Analytics is not currently synchronized. Its connection and traffic reporting are planned for the next release, separately from the existing Shopify Partner sync.