# Froomle Diagnostics Overlay

> Current Froomle documentation · [View canonical page](https://docs.froomle.com/froomle-doc-main/v2/diagnostics/index.html)

<a id="DiagnosticsOverview"></a>

## Overview

Froomle Diagnostics Overlay is the standalone diagnostics section for Froomle browser integrations.

Use this page when you need to:

-   use the Froomle Diagnostics Overlay Chrome extension
    
-   gather support details before opening an issue or review request
    
-   understand what the overlay checks and how to use it during reviews
    

For the extension privacy policy, see [Privacy Policy](https://docs.froomle.com/froomle-doc-main/v2/diagnostics/privacy-policy.html).

The SDK runtime object is documented under [SDK > Diagnostics](https://docs.froomle.com/froomle-doc-main/v2/js_lib/jslib.html#BrowserRuntime).

<a id="OverlayCapabilities"></a>

## Overlay Capabilities

The Froomle Diagnostics Overlay is the browser support tool for Froomle browser integration reviews.

It is designed for:

-   SDK implementation reviews
    
-   consent and identity troubleshooting
    
-   request-domain and traffic validation
    
-   event source-attribution diagnostics such as UTM and browser referrer enrichment state
    
-   benchmark and recommendation rendering checks
    
-   support verification on both SDK and legacy browser integrations
    

At a high level, the overlay:

-   detects Froomle SDK/runtime signals on pages you open
    
-   inspects `window.FroomleFrontendSdkRuntime` when available
    
-   observes browser-side Froomle traffic for legacy or manual integrations
    
-   highlights detected recommendation elements on the page
    
-   surfaces support-facing status for runtime, consent, identity, traffic, source-attribution, and benchmark behavior
    

For Chrome Web Store and extension-specific privacy behavior, see [Privacy Policy](https://docs.froomle.com/froomle-doc-main/v2/diagnostics/privacy-policy.html).

<a id="DiagnosticsSupport"></a>

## Support

When filing a support request or internal implementation review, include:

-   the page URL being inspected
    
-   the extension version or SDK version visible in diagnostics
    
-   screenshots of the Diagnostics Overlay when relevant
    
-   the observed request domain, page type, consent level, and current identity state
    
-   whether the issue reproduces on a real customer page, a staging page, or a sample page
    

If the page is a browser integration without the runtime object, also include:

-   whether recommendation requests were observed
    
-   whether events were observed
    
-   the relevant `request_id`, `list_name`, and `user_group` values when available