Case Studies on watchkeeper.net

A Recipe Blog Adds a Data Broker and a Video Ad Network Between Two Visits

Fri, 23 Oct 2026 00:00:00 +0000

Sites change their trackers all the time, and nobody tells their readers. A new ad deal, a new plug-in or a theme update can add a company to every page overnight. The Last visit section is there to catch that.

This case study uses a made-up recipe blog whose page changes between visits. The first time it’s opened in Watchkeeper, the panel counts three other sites: an analytics service, an ad pixel and the ad partner the pixel calls. On the next visit the same soup recipe tells five.

A Shop Page Calls Five Other Sites Before Anyone Answers Its Cookie Banner

Fri, 23 Oct 2026 00:00:00 +0000

Picture the owner of a small clothing shop. She added a cookie banner because her web designer said the law needed one, and she assumes nothing goes out until a visitor clicks Accept. This case study is built on a made-up shop page that behaves the way many real ones do.

Open the product page in Watchkeeper and leave the banner alone. Before you’ve read the first line, the panel lists five other sites.

Sending a Landing Page Report to the Agency That Built It

Fri, 23 Oct 2026 00:00:00 +0000

Say a small software company paid an agency to build its sign-up page, and a customer asks a question nobody in the company can answer: which companies does your sign-up page send my visit to? This case study answers it for a made-up landing page.

Open the page in Watchkeeper and press Save report. You get two files: an HTML page anyone can open and a JSON file for tools. The HTML version starts like this.