Detect Clinch
Clinch delivers hyper-personalized creative experiences and consumer intelligence across all channels.
Detection looks at script sources across 1 fingerprint rules among the site's public responses.
01
Websites using Clinch
Loading website list…
02
Signal classes
PluginView evaluates public page signals in these classes when identifying Clinch. Individual fingerprint rule bodies are proprietary and are not published.
- Script sources
03
Example public indicators for Clinch
Illustrative indicators derived from public catalog metadata for Clinch. A live scan may match additional proprietary rules beyond these examples.
- cdn.clinch.co
04
What a detection means
- Establishes
- One or more public signals on the scanned page matched a known Clinch signature (1 rules) at the time of the scan.
- Does not establish
- A sitewide install of Clinch, an active vendor contract, exclusive use, or that Clinch is still in place today.
05
How to check a site for Clinch
- 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Clinch signals.
- 2. PluginView reads only public responses (script sources) and scores them against the Clinch signature set (1 rules).
- 3. Review the confidence score and text explanation for Clinch on the results page.
06
FAQ: detecting Clinch
- Can PluginView detect Clinch without logging in?
- Yes. PluginView only reads publicly accessible responses when checking for Clinch — typically script sources. It does not bypass authentication or paywalls.
- What category is Clinch?
- Clinch is classified under Personalisation in the PluginView directory.
- How many fingerprint rules cover Clinch?
- This reference currently tracks 1 fingerprint rule across script sources. Individual rule bodies are proprietary and are not published.
- What public signals suggest a site uses Clinch?
- Illustrative public indicators for Clinch include cdn.clinch.co. A live scan may match additional proprietary rules beyond these examples.
