Can PluginView detect Formbricks without logging in?

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

What category is Formbricks?

Formbricks is classified under Forms, Scheduling & Surveys in the PluginView directory.

How many fingerprint rules cover Formbricks?

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 Formbricks?

Illustrative public indicators for Formbricks include formbricks.com/js; app.formbricks.com. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting Formbricks?

For Formbricks, start with: In-product and website surveys.

Detect Formbricks

Forms, Scheduling & Surveys

PluginView detects Formbricks, a Forms, Scheduling & Surveys, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with Formbricks include formbricks.com/js, app.formbricks.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 Formbricks

Loading website list…

Signal classes

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

Vendor endpoints

Example public indicators for Formbricks

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

formbricks.com/js
app.formbricks.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: In-product and website surveys

How to check a site for Formbricks

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

FAQ: detecting Formbricks

Can PluginView detect Formbricks without logging in?: Yes. PluginView only reads publicly accessible responses when checking for Formbricks — typically vendor endpoints. It does not bypass authentication or paywalls.
What category is Formbricks?: Formbricks is classified under Forms, Scheduling & Surveys in the PluginView directory.
How many fingerprint rules cover Formbricks?: 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 Formbricks?: Illustrative public indicators for Formbricks include formbricks.com/js; app.formbricks.com. A live scan may match additional proprietary rules beyond these examples.
Which pages are best for detecting Formbricks?: For Formbricks, start with: In-product and website surveys.