Detect AdCalls

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

• Response headers
• DOM selectors

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

• content-security-policy: .adcalls.nl
• link

Establishes

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

Does not establish

A sitewide install of AdCalls, an active vendor contract, exclusive use, or that AdCalls 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 AdCalls signals.
2. 2. PluginView reads only public responses (response headers, dom selectors) and scores them against the AdCalls signature set (2 rules).
3. 3. Review the confidence score and text explanation for AdCalls on the results page.

Can PluginView detect AdCalls without logging in?

Yes. PluginView only reads publicly accessible responses when checking for AdCalls — typically response headers, dom selectors. It does not bypass authentication or paywalls.

What category is AdCalls?

AdCalls is classified under Analytics in the PluginView directory.

How many fingerprint rules cover AdCalls?

This reference currently tracks 2 fingerprint rules across response headers, dom selectors. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses AdCalls?

Illustrative public indicators for AdCalls include content-security-policy: .adcalls.nl; link. A live scan may match additional proprietary rules beyond these examples.