For products that run on customers' sites
Confirm your widget renders on every site that installed it
Load each customer's page, wait for your widget and capture only the widget, or learn that it never appeared.
The problem
Your chat widget, review carousel or booking form runs on hundreds of sites you do not control. A theme update hides it, a consent tool blocks it, a customer pastes the snippet into the wrong template, and the first sign is a support ticket asking why nothing has come in for a month.
How domscout handles it
waitForSelector waits for your widget's root element to appear and captureSelector crops the screenshot to it, so a success is a picture of the widget as visitors on that site see it. When the widget never appears, the request is refused with 400 WAIT_FOR_SELECTOR_TIMEOUT and nothing is charged, so a failed check is both free and unambiguous. Run it per site, or hand a batch the whole list.
Where it shows up
- An onboarding step that confirms a new customer's install.
- A weekly sweep of every site with the widget installed.
- A picture of the widget on each customer's site for the support team.
The request
POST /screenshot. Available on every plan at 1 credit a site, and a refused check is refunded. Checking up to 100 sites in one request with /batch starts at Business.
Go further
More in Testing and QA: Responsive layout checks · Visual regression testing · JavaScript error checks · Signup and checkout flow checks · Hover, focus and dark mode screenshots · Localization screenshots · Unlabelled control checks · A screenshot of every step · Screenshots for support tickets · Ad landing page checks · Before and after hydration · Selectors for test automation · Print layout checks · All use cases
Give your product a browser.
Get clean web content and visual proof into your workflow in minutes.