Gainsight

Overview

Gainsight operates two primary products: Gainsight CS (Customer Success) for managing customer health and retention workflows, and Gainsight PX (Product Experience) for in-app engagement and product analytics. The browser-side scripts that appear on websites and web applications are almost exclusively from Gainsight PX, which embeds product usage tracking, in-app guides, NPS surveys, and feature adoption analytics directly into web applications.

What This Script Does

Gainsight PX deploys a JavaScript SDK within web applications to track user behavior and deliver in-app experiences:

User Identification and Tracking

• The PX SDK identifies users through an aptrinsic('identify', ...) call that passes user attributes (user ID, email, account ID, plan type) to Gainsight
• A persistent cookie or local storage entry (commonly prefixed with apt. or _gainsight_) tracks the user across sessions within the application
• Anonymous tracking is supported for users who have not yet been identified (pre-login states)

Product Analytics

• Tracks page or screen views within the application, including SPA (single-page application) route changes
• Records feature engagement events: button clicks, module usage, configuration changes
• Captures custom events pushed through the aptrinsic('track', ...) API for business-specific metrics
• Measures time spent on specific features or pages for adoption analysis

In-App Engagement

• Renders guided walkthroughs and tooltips overlaid on the application UI to onboard new users
• Displays NPS and CSAT survey modals at configured trigger points (e.g., after 30 days of usage or after completing a workflow)
• Shows targeted in-app messages, banners, and announcements based on user segment membership
• Manages knowledge center bots and resource centers embedded in the application

Scripts load from web-sdk.aptrinsic.com and api.aptrinsic.com. Data collected is transmitted to Gainsight's cloud infrastructure for analysis, segmentation, and engagement rule evaluation.

Consent & Compliance

Gainsight PX spans both analytics and functional categories. The in-app guides and surveys provide functional value to the user (onboarding help, feedback collection), while the underlying product usage analytics serves the application provider's business objectives.

Under GDPR, identified user tracking through the PX SDK constitutes personal data processing. However, the context matters: Gainsight PX typically operates within authenticated web applications where users have an existing account relationship. The lawful basis is often legitimate interest (product improvement, customer success) rather than consent, though this must be evaluated on a case-by-case basis. Cookies set by the PX SDK are non-essential and technically require consent under ePrivacy, even in authenticated application contexts.

Under CCPA/CPRA, the product usage data and user behavioral profiles Gainsight collects constitute personal information. Business-to-business exemptions may apply depending on the nature of the application and its users, but consumer-facing applications must provide appropriate disclosures.

Should You Block This Without Consent?

Conditional. Gainsight PX combines functional in-app guidance with analytics tracking. In authenticated B2B applications, many organizations rely on legitimate interest as the lawful basis and load the PX SDK without a consent gate, disclosing the tracking in their privacy policy. For consumer-facing applications or when strict ePrivacy compliance is required, the analytics tracking component should be gated behind consent while core application functionality remains accessible.