Published on 2025-06-22T08:31:50Z

What is NoScript Tracking? Examples & Use Cases in Analytics

NoScript Tracking is a fallback method in web analytics to capture visitor interactions when JavaScript is disabled or blocked. It leverages HTML elements like

Illustration of Noscript tracking
Illustration of Noscript tracking

Noscript tracking

Fallback analytics technique using <noscript> image beacons or HTTP requests to capture traffic when JavaScript is disabled.

Why NoScript Tracking Matters

NoScript Tracking fills gaps left by JavaScript-based analytics, ensuring you don’t miss visitors who disable scripts, use ad blockers, or browse in restrictive environments.

  • Coverage for script-blocked users

    Captures basic pageview data from users who have disabled or blocked JavaScript, giving you a more accurate total visitor count.

  • Privacy-friendly data collection

    Often uses simple image requests without cookies, aligning with privacy regulations and increasing user trust.

How NoScript Tracking Works

NoScript Tracking operates by embedding fallbacks that trigger HTTP requests to analytics endpoints when JavaScript cannot run.

  • Image beacon via <noscript>

    A 1x1 transparent image or pixel is loaded within a <noscript> block, sending a GET request to record a pageview.

    • Basic pixel tag:
      <noscript>
        <img src="https://analytics.example.com/pixel.gif?event=pageview&id=12345" width="1" height="1" alt="" />
      </noscript>
      
  • Measurement protocol requests

    Uses direct HTTP calls with query parameters to analytics APIs, ideal for detailed hit data without relying on JavaScript.

Implementing NoScript Tracking with Plainsignal

PlainSignal provides built-in support for cookieless NoScript Tracking. Use the following code snippets:

  • Standard script setup

    Include PlainSignal’s deferred JavaScript snippet to track users with scripts enabled.

    • Example code:
      <link rel="preconnect" href="//eu.plainsignal.com/" crossorigin />
      <script defer data-do="yourwebsitedomain.com" data-id="0GQV1xmtzQQ" data-api="//eu.plainsignal.com" src="//cdn.plainsignal.com/PlainSignal-min.js"></script>
      
  • Noscript fallback pixel

    Add a <noscript> tag to capture pageviews from visitors without JavaScript.

    • Example code:
      <noscript>
        <img src="//eu.plainsignal.com/pixel.gif?do=yourwebsitedomain.com&id=0GQV1xmtzQQ" width="1" height="1" alt="" />
      </noscript>
      

Implementing NoScript Tracking with GA4

Google Analytics 4 doesn’t include a native <noscript> fallback, but you can leverage the Measurement Protocol to send hits manually.

  • Constructing a measurement protocol call

    Create a URL with required parameters (v, tid, cid, t) to record a page_view event.

    • Example code:
      <noscript>
        <img src="https://www.google-analytics.com/g/collect?v=2&tid=G-XXXXXXX&gtm=2oe&cid=555&t=page_view" width="1" height="1" alt="" />
      </noscript>
      
  • Key parameter guidelines

    Ensure you include a persistent client ID (cid), measurement ID (tid), version (v), and event type (t) for accurate attribution.

Best Practices and Limitations

While NoScript Tracking enhances coverage, it has trade-offs in data richness and accuracy compared to JavaScript-based analytics.

  • Limited event data

    NoScript pixel hits typically only capture pageviews, missing out on scrolls, clicks, and custom events.

  • Potential for data discrepancies

    Some hits may be blocked by network policies or reload caching, leading to minor undercounts.


Related terms