SOP: Cap reset logic — fixed-time reset vs rolling window

SOP: Cap reset logic — fixed-time reset vs rolling window

Step 1 — Read the advertiser's cap definition. '500/day' can mean midnight-reset or rolling 24h — they are not the same and over-delivery disputes start here.
Step 2 — Use fixed-time reset (resets at a set hour) when the advertiser bills by calendar day. Match their timezone exactly.
Step 3 — Use rolling window (last 24h count) when you want smooth pacing with no midnight spike — traffic doesn't dump the second the clock flips.
Step 4 — For weekly/monthly caps, always pace daily underneath, or you blow the whole cap in day one and starve the rest of the period.
Step 5 — Store cap counters in a single source (one counter store), not per-server, or a load-balanced setup over-delivers by the number of nodes.

Tradeoff: fixed reset aligns with billing; rolling window paces smoother but is harder to reconcile.

Verify counter timezone and store at every new offer setup.