Appcues

Overview

Appcues is a no-code product adoption and user onboarding platform that enables product teams to build in-app tours, tooltips, checklists, announcement modals, and NPS surveys without engineering resources. Product managers configure flows in the Appcues Studio using a visual builder; the Appcues script then injects those UI overlays onto the live application at runtime for targeted user segments. Appcues is primarily used by B2B SaaS companies to improve new user activation, drive feature adoption, and collect in-product feedback. Customers include Loom, Wistia, and various mid-market SaaS platforms.

What This Script Does

The Appcues script (fast.appcues.com/<account-id>.js) loads on every page of the host application and evaluates targeting rules to determine which flows to display to the current user.

Script loading:

• The main Appcues bundle loads from fast.appcues.com, Appcues' CDN
• On initialization, the script fetches flow configurations from api.appcues.com based on the account ID and current user properties
• Flow assets (images, video, custom HTML) may load from cdn.appcues.com

User identification:

• The host application passes user identity to Appcues via Appcues.identify(userId, { plan: 'pro', createdAt: '2024-01-15', ... })
• This links all Appcues interactions to the authenticated user's internal ID
• User properties (plan tier, signup date, feature flags, company size) are transmitted to Appcues' servers to power flow targeting rules

Flow injection:

• Tours: step-by-step modals and tooltips anchored to specific UI elements in the host application
• Checklists: persistent onboarding task lists rendered as a side panel or widget
• Announcements: full-page modals or slideouts for product update notifications
• NPS surveys: in-product Net Promoter Score prompts with follow-up open-text questions

Cookies and storage:

• appcues_<account-id> — persistent cookie or localStorage entry tracking which flows a user has seen, completed, or dismissed, typically with multi-month expiry
• Session state cookies for managing active multi-step tour progress
• No third-party advertising cookies; all storage is scoped to the host application's domain

Behavioral tracking per interaction:

• Flow seen: which flows were shown to which user
• Step completion: progress through each tour step
• Completion rate: how many users finish versus abandon each flow
• Button clicks, form submissions within Appcues-rendered UI elements
• NPS scores and free-text responses

Consent & Compliance

Appcues falls primarily under the functional consent category when used for its core purpose: delivering in-app onboarding and guidance within an authenticated user session. The flows are part of the product experience — helping users learn features they have signed up to use. The legal basis is typically legitimate interest or contract performance, as onboarding directly supports the service the user has engaged.

However, Appcues also collects engagement analytics (flow completion rates, NPS scores, step-by-step drop-off data) that constitute personal data under GDPR when linked to authenticated user IDs. If this engagement data is shared with marketing tools (e.g., pushed to Salesforce or HubSpot for lifecycle marketing triggers), the processing extends into marketing, requiring appropriate legal basis or consent.

Under CCPA/CPRA, in-product analytics linked to user IDs constitute personal information collection requiring disclosure. Appcues is a US-based company; EU data transfers rely on Standard Contractual Clauses.

Should You Block This Without Consent?

Conditional. If Appcues is used purely for in-app onboarding and guidance within the user's authenticated session, it can be treated as functional and loaded without separate consent. If engagement analytics are exported to marketing platforms for retargeting or lifecycle campaigns, those downstream flows require consent. Block the Appcues marketing integrations, not necessarily the core onboarding script.