Detect WebEngage
Marketing automationPersonalisationMarketing, CDP, Email & Push
WebEngage is a customer data platform and marketing automation suite.
Detection looks at script sources, javascript globals across 2 fingerprint rules among the site's public responses.
Websites using WebEngage
Loading website list…
Signal classes
PluginView evaluates public page signals in these classes when identifying WebEngage. Individual fingerprint rule bodies are proprietary and are not published.
- Script sources
- JavaScript globals
Example public indicators for WebEngage
Illustrative indicators derived from public catalog metadata for WebEngage. A live scan may match additional proprietary rules beyond these examples.
- .webengage.com?/
- webengage.__v:
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 or notification
How to check a site for WebEngage
- 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. PluginView reads only public responses (script sources, javascript globals) and scores them against the WebEngage signature set (2 rules).
- 3. Review the confidence score and text explanation for WebEngage on the results page.
FAQ: detecting WebEngage
- Can PluginView detect WebEngage without logging in?
- Yes. PluginView only reads publicly accessible responses when checking for WebEngage — typically script sources, javascript globals. 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.
- How many fingerprint rules cover WebEngage?
- This reference currently tracks 2 fingerprint rules across script sources, javascript globals. Individual rule bodies are proprietary and are not published.
- What public signals suggest a site uses WebEngage?
- Illustrative public indicators for WebEngage include .webengage.com?/; webengage.__v:. A live scan may match additional proprietary rules beyond these examples.
- Which pages are best for detecting WebEngage?
- For WebEngage, start with: All pages; trigger event or notification.
