Detect Campaign Monitor

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

• Script sources
• DOM selectors

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

• .createsend1.com/
• input, form

Establishes

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

Does not establish

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

Can PluginView detect Campaign Monitor without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Campaign Monitor — typically script sources, dom selectors. It does not bypass authentication or paywalls.

What category is Campaign Monitor?

Campaign Monitor is classified under Marketing automation, Email in the PluginView directory.

How many fingerprint rules cover Campaign Monitor?

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

What public signals suggest a site uses Campaign Monitor?

Illustrative public indicators for Campaign Monitor include .createsend1.com/; input, form. A live scan may match additional proprietary rules beyond these examples.