/settings, administrator only, blocked until the product license is active) configures every backend integration. Most changes apply immediately on save; the one exception (secure cookies) needs a service restart.
PADS4 connection
Base URL, service account username/password, domain (defaults toPADS if blank), and a system-info batch size (used when fetching per-device metadata for Distribution). Test PADS4 connection validates the credentials against the entered base URL before you save. This is required for PADS4 user login and every background monitor.
Status monitor
How often the connectivity background poll runs — toggle between seconds (minimum 10) or minutes. This drives Dashboard freshness indirectly (via snapshots) and directly powers History.CMS monitor
Poll interval in minutes (minimum 1, default 5) for the CMS 2.0 background collector. History is retained for 3 months regardless of interval.Proof of play
- API base path — the OData path segment PADS4 exposes proof-of-play logs under.
- Sync interval (minutes) — how often the background sync checks for new/updated days.
- Keep history for (days) — retention window; older events are purged automatically. Total stored volume plateaus once this window is full (older data ages out as new data comes in).
- Max query range (days) — the widest date range a single report or page query is allowed to request at once. This is what keeps query performance flat regardless of how much history is retained overall.
- Sync concurrency — how many days are fetched from PADS4 in parallel during a sync/backfill pass.
- Earliest selectable date — floor for the date pickers on Proof of Play and Reports.