Appcues is a solution for measuring and improving product adoption.
01
Websites using Appcues
1 hostnames in the PluginView corpus for this technology.
| Hostname | Last seen |
|---|---|
| iubenda.com | 8/3/2026 |
02
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.
03
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: Authenticated app; trigger guidance
04
How to check a site for Appcues
- 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Appcues signals (prefer: Authenticated app; trigger guidance).
- 2. PluginView reads only public responses and scores them against proprietary Appcues fingerprints. Rule bodies and identifiers are not published.
- 3. Review the confidence score and text explanation for Appcues on the results page.
05
FAQ: detecting Appcues
- Can PluginView detect Appcues without logging in?
- Yes. PluginView only reads publicly accessible responses when checking for Appcues. It does not bypass authentication or paywalls.
- What category is Appcues?
- Appcues is classified under User onboarding, Analytics, Product Intelligence & Monitoring in the PluginView directory.
- Does PluginView publish Appcues 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 Appcues?
- For Appcues, start with: Authenticated app; trigger guidance.
