Can PluginView detect WonderPush without logging in?

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

What category is WonderPush?

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

How many fingerprint rules cover WonderPush?

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

Illustrative public indicators for WonderPush include cdn.by.wonderpush.com/sdk; web.wonderpush.com. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting WonderPush?

For WonderPush, start with: All pages; initialize push.

Detect WonderPush

Marketing, CDP, Email & Push

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

Loading website list…

Signal classes

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

Vendor endpoints

Example public indicators for WonderPush

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

cdn.by.wonderpush.com/sdk
web.wonderpush.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; initialize push

How to check a site for WonderPush

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

FAQ: detecting WonderPush

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