Can PluginView detect Bloomreach Engagement without logging in?

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

What category is Bloomreach Engagement?

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

How many fingerprint rules cover Bloomreach Engagement?

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 Bloomreach Engagement?

Illustrative public indicators for Bloomreach Engagement include cdn.exponea.com; api.exponea.com. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting Bloomreach Engagement?

For Bloomreach Engagement, start with: All pages; trigger event.

Detect Bloomreach Engagement

Marketing, CDP, Email & Push

PluginView detects Bloomreach Engagement, a Marketing, CDP, Email & Push, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with Bloomreach Engagement include cdn.exponea.com, api.exponea.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 Bloomreach Engagement

Loading website list…

Signal classes

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

Vendor endpoints

Example public indicators for Bloomreach Engagement

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

cdn.exponea.com
api.exponea.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 Bloomreach Engagement

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

FAQ: detecting Bloomreach Engagement

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