PluginView

Detect Adobe Experience Platform Web SDK

Marketing, CDP, Email & Push

PluginView detects Adobe Experience Platform Web SDK, a Marketing, CDP, Email & Push, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with Adobe Experience Platform Web SDK include assets.adobedtm.com, alloy.js, edge.adobedc.net. 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 3 fingerprint rules among the site's public responses.

01

Websites using Adobe Experience Platform Web SDK

Loading website list…

02

Signal classes

PluginView evaluates public page signals in these classes when identifying Adobe Experience Platform Web SDK. Individual fingerprint rule bodies are proprietary and are not published.

  • Vendor endpoints
03

Example public indicators for Adobe Experience Platform Web SDK

Illustrative indicators derived from public catalog metadata for Adobe Experience Platform Web SDK. A live scan may match additional proprietary rules beyond these examples.

  • assets.adobedtm.com
  • alloy.js
  • edge.adobedc.net
04

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.
05

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

06

How to check a site for Adobe Experience Platform Web SDK

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

FAQ: detecting Adobe Experience Platform Web SDK

Can PluginView detect Adobe Experience Platform Web SDK without logging in?
Yes. PluginView only reads publicly accessible responses when checking for Adobe Experience Platform Web SDK — typically vendor endpoints. It does not bypass authentication or paywalls.
What category is Adobe Experience Platform Web SDK?
Adobe Experience Platform Web SDK is classified under Marketing, CDP, Email & Push in the PluginView directory.
How many fingerprint rules cover Adobe Experience Platform Web SDK?
This reference currently tracks 3 fingerprint rules across vendor endpoints. Individual rule bodies are proprietary and are not published.
What public signals suggest a site uses Adobe Experience Platform Web SDK?
Illustrative public indicators for Adobe Experience Platform Web SDK include assets.adobedtm.com; alloy.js; edge.adobedc.net. A live scan may match additional proprietary rules beyond these examples.
Which pages are best for detecting Adobe Experience Platform Web SDK?
For Adobe Experience Platform Web SDK, start with: All pages; trigger event.