Detect WebEngage

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.

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 or notification

1. 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest WebEngage signals (prefer: All pages; trigger event or notification).
2. 2. PluginView reads only public responses and scores them against proprietary WebEngage fingerprints. Rule bodies and identifiers are not published.
3. 3. Review the confidence score and text explanation for WebEngage on the results page.

Can PluginView detect WebEngage without logging in?

Yes. PluginView only reads publicly accessible responses when checking for WebEngage. It does not bypass authentication or paywalls.

What category is WebEngage?

WebEngage is classified under Marketing automation, Personalisation, Marketing, CDP, Email & Push in the PluginView directory.

Does PluginView publish WebEngage fingerprint rules?

No. Detection uses proprietary fingerprint rules that are not published. Scan results explain matches in plain language without disclosing rule bodies or identifiers.

Which pages are best for detecting WebEngage?

For WebEngage, start with: All pages; trigger event or notification.