Can PluginView detect Iterable Web SDK without logging in?

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

What category is Iterable Web SDK?

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

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

Illustrative public indicators for Iterable Web SDK include js.iterable.com; api.iterable.com. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting Iterable Web SDK?

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

Detect Iterable Web SDK

Marketing, CDP, Email & Push

PluginView detects Iterable Web SDK, a Marketing, CDP, Email & Push, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with Iterable Web SDK include js.iterable.com, api.iterable.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 Iterable Web SDK

Loading website list…

Signal classes

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

Vendor endpoints

Example public indicators for Iterable Web SDK

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

js.iterable.com
api.iterable.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 Iterable Web SDK

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

FAQ: detecting Iterable Web SDK

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