Detect Drip

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

• Vendor endpoints

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

• tag.getdrip.com
• api.getdrip.com

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.

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 and signup forms

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

Can PluginView detect Drip without logging in?

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

What category is Drip?

Drip is classified under Marketing automation, Marketing, CDP, Email & Push in the PluginView directory.

How many fingerprint rules cover Drip?

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

Illustrative public indicators for Drip include tag.getdrip.com; api.getdrip.com. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting Drip?

For Drip, start with: All pages and signup forms.