Can PluginView detect Brevo Tracker without logging in?

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

What category is Brevo Tracker?

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

How many fingerprint rules cover Brevo Tracker?

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 Brevo Tracker?

Illustrative public indicators for Brevo Tracker include sibautomation.com/sa.js; in-automate.brevo.com. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting Brevo Tracker?

For Brevo Tracker, start with: All pages; observe visit.

Detect Brevo Tracker

Marketing, CDP, Email & Push

PluginView detects Brevo Tracker, a Marketing, CDP, Email & Push, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with Brevo Tracker include sibautomation.com/sa.js, in-automate.brevo.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 Brevo Tracker

Loading website list…

Signal classes

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

Vendor endpoints

Example public indicators for Brevo Tracker

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

sibautomation.com/sa.js
in-automate.brevo.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; observe visit

How to check a site for Brevo Tracker

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

FAQ: detecting Brevo Tracker

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