Detect Dynamic Yield

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; observe decision request

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

Can PluginView detect Dynamic Yield without logging in?

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

What category is Dynamic Yield?

Dynamic Yield is classified under A/B Testing, Personalisation, Experimentation, Search & Personalization in the PluginView directory.

Does PluginView publish Dynamic Yield 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 Dynamic Yield?

For Dynamic Yield, start with: All pages; observe decision request.