Can PluginView detect Treasure Data Web SDK without logging in?

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

What category is Treasure Data Web SDK?

Treasure Data Web SDK is classified under Marketing, CDP, Email & Push in the PluginView directory.

How many fingerprint rules cover Treasure Data 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 Treasure Data Web SDK?

Illustrative public indicators for Treasure Data Web SDK include cdn.treasuredata.com/sdk; in.treasuredata.com. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting Treasure Data Web SDK?

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

Detect Treasure Data Web SDK

Marketing, CDP, Email & Push

PluginView detects Treasure Data Web SDK, a Marketing, CDP, Email & Push, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with Treasure Data Web SDK include cdn.treasuredata.com/sdk, in.treasuredata.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 Treasure Data Web SDK

Loading website list…

Signal classes

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

Vendor endpoints

Example public indicators for Treasure Data Web SDK

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

cdn.treasuredata.com/sdk
in.treasuredata.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: All pages; trigger event

How to check a site for Treasure Data Web SDK

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

FAQ: detecting Treasure Data Web SDK

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