Choose a refresh cadence based on when your team needs new source data. Manual and scheduled executions that transfer primary records create usage. Updating a chart from data already in the worksheet is a different operation.
Set a useful cadence
Start with the decision that needs the report. A weekly planning session and a daily follow-up queue have different freshness requirements. Avoid choosing the fastest cadence simply because it appears in a menu.
Daily, hourly, and shorter refresh capabilities require their actual production entitlements and acceptance. The sample’s controls illustrate the reporting experience; they do not establish a live scheduling service or an SLA.
Understand what is counted
Every execution counts its successfully transferred primary records. Repeated transfer of the same contact in a new execution adds another unit. The 250-transfer monthly allowance and volume bands apply to accumulated account usage.
Supporting lookups and embedded invoice/order line items are bundled with their parent records. A retry of the same delivery operation must not create a duplicate charge. Do not treat a job retry and a fresh scheduled execution as equivalent.
Separate saving from running
Changing an import’s name, schedule, or update permission uses a settings save. Field and filter edits need a current preview before Save & Run. The interface should show which action actually runs the source data job.
Pause stops scheduled transfers while retaining existing worksheet values and already accrued usage. A frozen sheet can remain useful, but it should not claim to be current after its schedule is paused.
Plan for higher volumes
The pricing calculator uses records per execution and executions per month to estimate base usage. The exact rate ladder remains readable outside the calculator. Applicable markup and taxes can change the final amount.
For frequent large transfers, Talk to Sales about a subscription with more predictable costs. Bring the approximate records per run, frequency, and number of accounts so the discussion reflects the real workload.
Related: data and availability · transfer pricing · all documentation