Can PluginView detect Salesforce Embedded Service without logging in?

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

What category is Salesforce Embedded Service?

Salesforce Embedded Service is classified under Chat & Customer Support in the PluginView directory.

How many fingerprint rules cover Salesforce Embedded Service?

This reference currently tracks 2 fingerprint rules across vendor endpoints. Individual rule bodies are proprietary and are not published.

Which pages are best for detecting Salesforce Embedded Service?

For Salesforce Embedded Service, start with: All public pages; open support.

Detect Salesforce Embedded Service

Chat & Customer Support

PluginView detects Salesforce Embedded Service, a Chat & Customer Support, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with Salesforce Embedded Service include service.force.com/embeddedservice, salesforce.com/embeddedservice. 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 Salesforce Embedded Service

Loading website list…

Signal classes

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

Vendor endpoints

Example public indicators for Salesforce Embedded Service

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

service.force.com/embeddedservice
salesforce.com/embeddedservice

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: All public pages; open support

How to check a site for Salesforce Embedded Service

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

FAQ: detecting Salesforce Embedded Service

Can PluginView detect Salesforce Embedded Service without logging in?: Yes. PluginView only reads publicly accessible responses when checking for Salesforce Embedded Service — typically vendor endpoints. It does not bypass authentication or paywalls.
What category is Salesforce Embedded Service?: Salesforce Embedded Service is classified under Chat & Customer Support in the PluginView directory.
How many fingerprint rules cover Salesforce Embedded Service?: 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 Salesforce Embedded Service?: Illustrative public indicators for Salesforce Embedded Service include service.force.com/embeddedservice; salesforce.com/embeddedservice. A live scan may match additional proprietary rules beyond these examples.
Which pages are best for detecting Salesforce Embedded Service?: For Salesforce Embedded Service, start with: All public pages; open support.