Detect AcuityAds

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

• Response headers
• JavaScript globals

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

• content-security-policy: .acuityplatform.com
• acuityAdsEventQueue
• acuityAdsPixelKey

Establishes

One or more public signals on the scanned page matched a known AcuityAds signature (3 rules) at the time of the scan.

Does not establish

A sitewide install of AcuityAds, an active vendor contract, exclusive use, or that AcuityAds is still in place today.

1. 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest AcuityAds signals.
2. 2. PluginView reads only public responses (response headers, javascript globals) and scores them against the AcuityAds signature set (3 rules).
3. 3. Review the confidence score and text explanation for AcuityAds on the results page.

Can PluginView detect AcuityAds without logging in?

Yes. PluginView only reads publicly accessible responses when checking for AcuityAds — typically response headers, javascript globals. It does not bypass authentication or paywalls.

What category is AcuityAds?

AcuityAds is classified under Advertising in the PluginView directory.

How many fingerprint rules cover AcuityAds?

This reference currently tracks 3 fingerprint rules across response headers, javascript globals. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses AcuityAds?

Illustrative public indicators for AcuityAds include content-security-policy: .acuityplatform.com; acuityAdsEventQueue; acuityAdsPixelKey. A live scan may match additional proprietary rules beyond these examples.