What ad blocking is

Ad blocking is the use of software or browser settings to prevent many advertising elements—often including associated tracking scripts—from loading in a website. In practice, it usually works by stopping certain network requests (for example, calls to known ad or tracking domains) or by filtering page content so those elements never render.

How it works (the main approaches)

Most ad blocking solutions fall into a few practical patterns:

  1. Request blocking (network-level): The blocker intercepts web requests and denies ones that match rules (commonly lists of known ad/tracker sources). When those requests fail, the ad content and some trackers never load.
  2. Content filtering (page-level): Instead of blocking every request, the tool may hide or remove matching elements after the page loads. This can reduce what you see, even if some scripts already ran.
  3. Rules and lists: Many blockers rely on rule sets that are updated over time. Rules typically target common ad providers, tracker endpoints, and script patterns.

Because websites are dynamic, the same site may include different ad sources across page views or over time, which affects results.

Limitations and why ads still appear

Ad blocking usually reduces ads and trackers, but it rarely guarantees “no ads.” Common reasons include:

  • Different delivery paths: Ads may be served from the same site domain or through intermediaries not matched by existing rules.
  • Runtime changes: A page can load ad scripts after initial rendering, or switch providers based on geography, device type, or user behavior.
  • Filtering gaps: Content filtering may miss certain embed formats, lazy-loaded elements, or ads that appear only after interaction.
  • False negatives/positives: Rules may not match some trackers, or they may over-match and block site features that rely on similar scripts.

A useful mental model: ad blocking is best seen as selective interference with ad/tracker loading, not as a universal guarantee.

Practical checks you can do

To evaluate ad blocking on your own setup, use small, controlled checks:

  1. Confirm whether requests are blocked: Open the browser’s developer tools (Network tab) and compare a page with and without the blocker. Look for missing requests to ad/tracking-like endpoints.
  2. Check visibility vs. loading: If ads still show, determine whether the elements actually rendered or merely weren’t blocked. This helps distinguish display filtering from request blocking issues.
  3. Test the same page twice: Refresh and scroll; some ads load later. If results differ between loads, the site likely uses runtime ad delivery.
  4. Identify breakage: If buttons, login widgets, or layouts fail, the blocker may be interfering with non-ad resources. Consider narrowing blocking scope or temporarily allowing the site.

If you want fewer “mystery” results, check one variable at a time: enable/disable the blocker, then retest.

Ad blocking often overlaps with other privacy and security ideas, but they’re not identical:

  • Tracking protection: Focuses on preventing tracking behavior (including but not limited to ads), often via browser features.
  • Privacy filtering: May reduce third-party data collection, sometimes using broader heuristics than ad-only lists.
  • DNS filtering: Works earlier in the request path by filtering domain resolution; it can change what you see and also depends on how domains are used.

Because tools vary widely, the “right” setup is the one that matches your goals (fewer ads, fewer trackers, minimal site breakage) without assuming perfect coverage.