Core Features
Shot Schedules
Shot Schedules define what to capture, when to capture it, and how the capture behaves — all tied to a single web page URL.
Each Shot Schedule is centered on one URL. It controls when captures start, when they stop, how often they run, and which Web Profile and integrations they use.

Core fields
At a minimum, a schedule is defined by:
- Url – the page to capture.
- Auto populated DomainName and optional Description for easier identification.
- A linked WebProfile (how the browser behaves).
- Optional labels and Trigger Windows.
Start & stop behaviour
- Start Immediately – start the schedule immediately.
- Start Date – start at a specific date & time.
- End Date (Optional) – automatically stop after a certain date (e.g. end of campaign).
Frequency & capture time
Schedules can either use predefined frequencies or custom patterns:
- Pre-Defined Capture Frequency – use a built-in frequency (e.g. hourly, daily, weekly). OR
- Custom CaptureMonth / CaptureDay /CaptureTime – for custom one-off or yearly patterns like “1st of January at 00:00”.
Selectors & interactions
For advanced pages, schedules can specify CSS or XPath selectors to interact with elements before capture:
- SelectorXPath – select a specific element for focus or capture.
- SelectorClick – click an element (e.g. open a tab or dismiss a modal).
- SelectorHide – hide elements you don't want in the screenshot (e.g. chat bubbles).
- SelectorHover – hover over elements to reveal menus or tooltips.

