Backfill history

What each source can supply

Asking the GA4 order-attribution worker for an old period returns the recent window again. That is why 2022 to 2025 acquisition data comes from verkoopdump instead.

Before touching verkoopdump

Read-only, without exception. It is the company's only copy of pre-2022 order detail, with no backup story in this repository, and the credential is not read-only. Only the check in the code stands between a statement and a write. Reach it only through the model that performs that check.

Procedure

1. Decide the window and which source covers it.
2. Queue it in slices, typically a year, rather than in one run.
3. Let each slice drain before queueing the next; a large queue blocks everything that depends on the same type.
4. Switch the historic step off again once the window is complete.
5. Read real rows back across the window, at both edges and in the middle.

Verify

Row counts for the period, and a spot check that classification and calculation followed the import rather than stopping at it. A finished batch is not evidence.

Related

• verkoopdump
• Queues and crons
• Data freshness and history

Evidence

Read-only rule from AGENTS.md, Forbidden paths. Slice-and-switch-off pattern and the historic schedule line from AGENTS.md, Jobs and the batches queue. GA4's rolling window from AGENTS.md, The application. The commercetools trailing window from app/jobs/system/resetdaily.php and ingest.trailingqueuedays in config/settings.json. Basis: code-checked against the current implementation.