Can PluginView detect Branch Web SDK without logging in?

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

What category is Branch Web SDK?

Branch Web SDK is classified under Advertising, Attribution & Visitor Identification in the PluginView directory.

How many fingerprint rules cover Branch Web SDK?

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 Branch Web SDK?

Illustrative public indicators for Branch Web SDK include cdn.branch.io/branch-latest.min.js; api2.branch.io. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting Branch Web SDK?

For Branch Web SDK, start with: All pages; trigger event.

Detect Branch Web SDK

Advertising, Attribution & Visitor Identification

PluginView detects Branch Web SDK, a Advertising, Attribution & Visitor Identification, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with Branch Web SDK include cdn.branch.io/branch-latest.min.js, api2.branch.io. 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 Branch Web SDK

Loading website list…

Signal classes

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

Vendor endpoints

Example public indicators for Branch Web SDK

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

cdn.branch.io/branch-latest.min.js
api2.branch.io

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 pages; trigger event

How to check a site for Branch Web SDK

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

FAQ: detecting Branch Web SDK

Can PluginView detect Branch Web SDK without logging in?: Yes. PluginView only reads publicly accessible responses when checking for Branch Web SDK — typically vendor endpoints. It does not bypass authentication or paywalls.
What category is Branch Web SDK?: Branch Web SDK is classified under Advertising, Attribution & Visitor Identification in the PluginView directory.
How many fingerprint rules cover Branch Web SDK?: 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 Branch Web SDK?: Illustrative public indicators for Branch Web SDK include cdn.branch.io/branch-latest.min.js; api2.branch.io. A live scan may match additional proprietary rules beyond these examples.
Which pages are best for detecting Branch Web SDK?: For Branch Web SDK, start with: All pages; trigger event.