LogoLogo
Analytics HelperSirdata CMPA propos de Sirdata
English
English
  • Sirdata Server-Side
  • Installation
    • GTM Server Container
    • DNS Configuration
      • OVH
      • Netlify
      • Cloudflare
      • Gandi.net
    • Configuration GA4
    • Facebook Conversions API Setup
    • Data Processing
      • Hosting Only
      • GTM Helper Layer
  • Prices
    • Sirdata Server-Side
    • Configuration of GTM Server Side
  • GTM Server-Side Services
    • sGTM Set-up
  • F.A.Q SERVER SIDE
    • Pricing
      • Do you offer a free trial?
      • Do I need to enter a payment method for the free trial?
      • What payment methods do you accept?
      • What do you mean by “request”?
      • What is the cost per request?
      • Can I cancel my subscription?
    • Why use Server Side GTM
    • sGTM Portal
      • Access to the sGTM Portal from the Sirdata CMP Portal
      • Container Hosting
    • Tracking
      • Campaigns
      • Bypassing Adblockers
      • Hit Volume
    • Server-Side Operation
      • Tag Manager
      • Hosting
      • Google Tag Manager Access
      • DNS
      • GTM-Helper Without Hosting
      • Commitment
    • Performance
      • Script Loading
      • Optimization of CMP and GTM Loading
    • Google Analytics 4
      • GA4 Compatibility
      • Configuration GA4
      • GA4 Proxyfication
    • Facebook CAPI
      • Facebook Conversion API vs. Facebook Pixel
      • Facebook Conversions API Setup
      • Facebook CAPI Token Retrieval
    • Matomo
      • Matomo Compatibility
      • Matomo Token Retrieval
    • Linkedin
      • LinkedIn Compatibility
    • TikTok Events API
      • TikTok Compatibility
      • TikTok Token Retrieval
      • TikTok Events API
      • Outsourcing TikTok Events API Installation
    • Ad-blocking
      • Definition of Ad-Blocker
      • Ad-Blocker Operation
      • Bypass Ad-Blockers
Propulsé par GitBook
Sur cette page

Cet article vous a-t-il été utile ?

  1. F.A.Q SERVER SIDE
  2. Ad-blocking

Ad-Blocker Operation

How Does an Ad-Blocker Work?

An ad-blocker analyzes all requests sent by the web browser and compares them to specific criteria to decide whether they should be blocked. When a request matches these criteria, it is intercepted and blocked before reaching its destination.

Request Evaluation Process

  1. Request Inspection: Each HTTP/HTTPS request sent by the browser is examined in real-time.

  2. Comparison to Block Lists: The ad-blocker refers to block lists maintained by communities or specialized organizations. These lists, constantly updated, contain rules to identify requests related to tracking and advertising.

Block Lists

Block lists are files that define the criteria for recognizing malicious or undesirable requests. For example, the EasyPrivacy list is often used to block requests related to user tracking. Here’s a link to this list: EasyPrivacy.

Examples of strings in these lists:

  • .js?id=GTM-

  • googletagmanager.com

  • /gtag/js?

These strings primarily target tracking services such as Google Tag Manager and Google Analytics. If no action is taken to avoid blocking, these services will be systematically blocked by ad-blockers.

Updates and Bypasses

Block lists are regularly updated to adapt to new bypass techniques deployed by advertisers or tracking platforms. As a result, innovation in bypassing ad-blockers is a constant challenge. Each new version of the lists requires monitoring and adjustments to restore tracking or advertising functionality.

PrécédentDefinition of Ad-BlockerSuivantBypass Ad-Blockers

Dernière mise à jour il y a 5 mois

Cet article vous a-t-il été utile ?