Can PluginView detect Convert.com without logging in?

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

What category is Convert.com?

Convert.com is classified under Experimentation, Search & Personalization in the PluginView directory.

How many fingerprint rules cover Convert.com?

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 Convert.com?

Illustrative public indicators for Convert.com include cdn-4.convertexperiments.com/js; convert.com. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting Convert.com?

For Convert.com, start with: All pages; observe experiment activation.

Detect Convert.com

Experimentation, Search & Personalization

PluginView detects Convert.com, a Experimentation, Search & Personalization, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with Convert.com include cdn-4.convertexperiments.com/js, convert.com. 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 Convert.com

Loading website list…

Signal classes

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

Vendor endpoints

Example public indicators for Convert.com

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

cdn-4.convertexperiments.com/js
convert.com

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: All pages; observe experiment activation

How to check a site for Convert.com

1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Convert.com signals (prefer: All pages; observe experiment activation).
2. PluginView reads only public responses (vendor endpoints) and scores them against the Convert.com signature set (2 rules).
3. Review the confidence score and text explanation for Convert.com on the results page.

FAQ: detecting Convert.com

Can PluginView detect Convert.com without logging in?: Yes. PluginView only reads publicly accessible responses when checking for Convert.com — typically vendor endpoints. It does not bypass authentication or paywalls.
What category is Convert.com?: Convert.com is classified under Experimentation, Search & Personalization in the PluginView directory.
How many fingerprint rules cover Convert.com?: 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 Convert.com?: Illustrative public indicators for Convert.com include cdn-4.convertexperiments.com/js; convert.com. A live scan may match additional proprietary rules beyond these examples.
Which pages are best for detecting Convert.com?: For Convert.com, start with: All pages; observe experiment activation.