Can PluginView detect Google Floodlight without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Google Floodlight — typically vendor endpoints. It does not bypass authentication or paywalls.

What category is Google Floodlight?

Google Floodlight is classified under Advertising, Attribution & Visitor Identification in the PluginView directory.

How many fingerprint rules cover Google Floodlight?

This reference currently tracks 2 fingerprint rules across vendor endpoints. Individual rule bodies are proprietary and are not published.

Which pages are best for detecting Google Floodlight?

For Google Floodlight, start with: Campaign landing/conversion pages.

Detect Google Floodlight

Advertising, Attribution & Visitor Identification

PluginView detects Google Floodlight, a Advertising, Attribution & Visitor Identification, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with Google Floodlight include fls.doubleclick.net/activityi, doubleclick.net/ddm/activity. The listed vendor-controlled browser component was present and active on the scanned page at scan time. Full fingerprint rules remain proprietary; this page summarizes the signal classes and example indicators used for identification.

Detection looks at vendor endpoints across 2 fingerprint rules among the site's public responses.

Websites using Google Floodlight

Loading website list…

Signal classes

PluginView evaluates public page signals in these classes when identifying Google Floodlight. Individual fingerprint rule bodies are proprietary and are not published.

Vendor endpoints

Example public indicators for Google Floodlight

Illustrative indicators derived from public catalog metadata for Google Floodlight. A live scan may match additional proprietary rules beyond these examples.

fls.doubleclick.net/activityi
doubleclick.net/ddm/activity

What a detection means

Establishes: The listed vendor-controlled browser component was present and active on the scanned page at scan time.
Does not establish: It does not prove a sitewide installation, current commercial contract, backend-only use, exclusive use, or production transaction volume.

Minimum proof rule

Observe a live browser request, loaded script, or iframe to the listed unique vendor endpoint. Source-text-only matches do not qualify.

Best pages to check: Campaign landing/conversion pages

How to check a site for Google Floodlight

1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Google Floodlight signals (prefer: Campaign landing/conversion pages).
2. PluginView reads only public responses (vendor endpoints) and scores them against the Google Floodlight signature set (2 rules).
3. Review the confidence score and text explanation for Google Floodlight on the results page.

FAQ: detecting Google Floodlight

Can PluginView detect Google Floodlight without logging in?: Yes. PluginView only reads publicly accessible responses when checking for Google Floodlight — typically vendor endpoints. It does not bypass authentication or paywalls.
What category is Google Floodlight?: Google Floodlight is classified under Advertising, Attribution & Visitor Identification in the PluginView directory.
How many fingerprint rules cover Google Floodlight?: This reference currently tracks 2 fingerprint rules across vendor endpoints. Individual rule bodies are proprietary and are not published.
What public signals suggest a site uses Google Floodlight?: Illustrative public indicators for Google Floodlight include fls.doubleclick.net/activityi; doubleclick.net/ddm/activity. A live scan may match additional proprietary rules beyond these examples.
Which pages are best for detecting Google Floodlight?: For Google Floodlight, start with: Campaign landing/conversion pages.