Detect Marketpath CMS

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

• Cookies

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

• _mp_permissions: session

Establishes

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

Does not establish

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

A confirmed Marketpath CMS match also implies these technologies are present.

AzureZURB Foundation

Can PluginView detect Marketpath CMS without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Marketpath CMS — typically cookies. It does not bypass authentication or paywalls.

What category is Marketpath CMS?

Marketpath CMS is classified under CMS in the PluginView directory.

How many fingerprint rules cover Marketpath CMS?

This reference currently tracks 1 fingerprint rule across cookies. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Marketpath CMS?

Illustrative public indicators for Marketpath CMS include _mp_permissions: session. A live scan may match additional proprietary rules beyond these examples.