Help & FAQ

uxspire helps you understand how users really experience your digital product – right in the usage context, with no detours. The platform combines first-party event tracking, in-product surveys, proven UX metrics like NPS, CSAT and UEQ, plus clear reporting and CSV export – all in one structured app, organised by projects and workspaces.

uxspire is made for everyone who wants to make digital products better: product teams, UX researchers, marketing teams and digital product owners. You will find your way around quickly even without a technical background. Only for the initial integration of the tracking snippet or the HTTP API is it helpful to briefly bring a developer on board.

The following areas are currently available in the app: managing organisations, workspaces and projects, assigning roles and inviting team members, creating project API keys, capturing events, creating and analysing surveys, customising survey theming, using Target Group Studies, and applying UX metrics like NPS, CSAT and UEQ – including billing and plan management. Not yet available, but already visible in the navigation: Usability Testing as well as Heatmaps, Session Recordings and Funnel Analysis. These areas are marked as "Coming soon".

These features are not yet usable in the current app. Heatmaps, Session Recordings and Funnel Analysis already appear in the dashboard, but are marked there as "Coming soon" and not yet unlocked. A/B testing is also not yet included. We are actively working on it – as soon as something goes live, you will hear about it.

uxspire is built on three levels: your organisation is the top-level unit – within it you create workspaces, for example for different products or teams. In each workspace you then set up individual projects. Every project has its own API keys, surveys, UX metrics, a survey theme and event data. Roles and access rights can be assigned granularly on all three levels.

uxspire is built privacy-friendly from the ground up and respects privacy signals like Global Privacy Control (GPC) and Do Not Track by default. Whether your specific use is GDPR-compliant, however, also depends on your legal basis, your consent solution, the privacy notices on your website and – for enterprise customers – the suitable data processing agreement (DPA). You, as the operator, are responsible for this; uxspire provides the right tools.

The uxspire browser SDK works without third-party cookies. Depending on the surface, it uses localStorage or sessionStorage – for example for pseudonymous user IDs, session IDs, consent status, embed configurations and controlling how often a survey is shown. For hosted public-link surveys, an additional best-effort cookie may be set for deduplication. These technologies can also fall under the consent requirement – please review this as part of your data protection implementation.

uxspire is operated on EU hosting: the app infrastructure runs on Microsoft Azure in an EU region that is set per environment via deployment configuration. Survey assets and consent proof are stored or delivered in Cloudflare R2 with EU jurisdiction. Payment processing is handled by Stripe. For enterprise customers, a data processing agreement (DPA) is part of the contractual arrangement.

How long visitor data is retained depends on your plan. For VoC data: 0.5 months in the demo, 6 months in the VoC plan, 13 months in the Bundle and 25 months in the Enterprise plan. Separate limits apply to tracking data. We have to store invoicing and contract data longer for legal reasons – regardless of the chosen plan.

Yes, that is possible. In the default configuration, tracking can be specifically stopped for individual users with the SDK consent API: a call to uxspire.setConsent({ tracking: false }) disables both local tracking and the delivery of embed configurations. If users have Global Privacy Control (GPC) or Do Not Track enabled and these signals are respected, the server also suppresses event capture. You need to integrate the actual consent and opt-out interface on your website yourself – the SDK provides you with the necessary building blocks.

Yes. Via the /api/v1/privacy/forget endpoint, you can submit up to 100 user IDs (distinct_ids) for deletion per request – broken down by project. Important: this deletion path remains available even when regular data collection is blocked due to an expired trial, a quota overrun or a billing issue. Deletion requests are therefore never blocked by the account status.

Integration is done quickly: you add a small asynchronous script snippet with your project key to the <head> of your website – the snippet loads /embed/v1/uxspire.js with your data-api-key. You can then send your own events with window.uxspire.track("event_name", { ... }). Surveys are delivered automatically via the same embed configuration as soon as they are published and configured for a suitable surface.

uxspire can be integrated into all modern websites and common JavaScript frameworks – whether React, Vue, Angular or plain HTML. Survey embeds rely on Web Components with Shadow DOM, which ensures a clean separation from the rest of the page styling. The documented minimum baseline for the standard styling is Safari/iOS 16.4+, Firefox 101+ and Chrome/Edge 73+.

No, uxspire does not work with automatic full capture. Only events that you actively send via the SDK or the HTTP API are stored, along with survey responses from your users. Heatmap, recording or autocapture data is not collected in the current app. In addition, privacy signals, consent settings, rate limits, plan limits and workspace permissions can restrict collection.

Integrations with tools like Google Analytics, Adobe Analytics, Slack, Discord or Jira are already reflected in the plan limits, but not yet implemented as usable connections in the app. What you can already use today: ingest data via the HTTP ingestion API and export survey results as CSV – both integrate well into existing workflows.

uxspire surveys offer many question types: short and long text answers, single choice, multiple choice, ratings, Likert questions and rankings. Each question can optionally be enriched with an image. For a pleasant user experience, you can add welcome and thank-you screens. With simple display logic rules, you additionally control which questions are shown when.

You have four options: as a public link, as an inline embed placed directly in your page, as a modal or as exit-intent – that is, just before someone leaves the page. A public link can additionally be combined with an embedded survey. Inline, modal and exit-intent, however, are mutually exclusive per survey. If you want to place a survey in several spots, simply create separate surveys.

UX Metrics are proven measurement instruments that let you systematically capture the quality of your product from the user perspective: Net Promoter Score (NPS), Customer Satisfaction Score (CSAT), User Experience Questionnaire (UEQ) and UEQ-S. They are embedded directly into your product – as a modal or inline embed – and support German and English. The analysis delivers structured results such as NPS segments, CSAT scores, UEQ dimensions, trends over time and comments. For NPS and CSAT you can additionally filter by device and segment; UEQ and UEQ-S are evaluated over time.

The results view gives you a quick overview: you see response trends for 7, 30 and 90 days or the entire period, can filter by revision and display type, and review question breakdowns, text answers and word clouds. All survey responses can also be exported as CSV – handy for deeper analysis or sharing with the team.

Yes. The design of your surveys is controlled project-wide via the survey theme – you set colours, fonts and the overall appearance once and they apply to all surveys in the project. For embedded surveys, you can additionally use CSS custom properties and uxspire-survey::part(...) to align the design even more closely with your product. Individual CSS per survey is not supported, and the use of custom CSS depends on your plan.

With uxspire you collect feedback exactly where it arises – right in the moment of use. You can display surveys as an inline element, modal or exit-intent and control precisely where they appear via URL patterns, CSS selectors and insertion positions. Display logic and throttling make sure users are not disturbed too often. An AI assistant for writing questions is not yet available in the current version.

The uxspire snippet is loaded asynchronously and does not block the loading of your page. Events are buffered and, when possible, transmitted via sendBeacon when the page is left – so without unnecessary network requests during the page visit. The actual impact on your loading times also depends on your specific integration, network conditions and how many events you send. No one can promise a blanket zero impact, but the snippet is designed for minimal performance impact.

For working with events, four endpoints are available: /api/v1/e for individual events, /api/v1/batch when you want to send multiple events at once, /api/v1/identify to link anonymous with known user IDs, and /api/v1/privacy/forget for deletion requests. All endpoints are authenticated with your project key (prefix uxs_).

A 429 error means the rate limit for your project key was briefly exceeded – that is, too many requests in a short period. In the Demo plan that is 100 requests per 60 seconds; in the Tracking, VoC, Bundle and Enterprise plans the limit is 3,000 requests per 60 seconds. This limit only concerns the transport – monthly plan quotas are checked separately and lead to a different error type.

There are five plan tiers: Demo, Tracking, Voice of Customer, Bundle and Enterprise. The demo runs for 14 days and gives you the chance to get to know uxspire at your own pace. After that, your organisation switches to a read-only mode until you decide on a paid plan. Features and limits – including workspaces, editors, survey surfaces, response quotas and custom CSS – are checked directly on the server side.

Payment processing runs securely via Stripe. Stripe currently has credit card payments, Amazon Pay, Apple Pay, Google Pay, SEPA direct debit and bank transfer enabled.

Yes. Self-service customers cancel their subscription themselves in the billing administration or Stripe Customer Portal inside the app. A cancellation takes effect at the end of the period already paid for: your access remains fully available until then. Enterprise customers can additionally terminate in text form within the applicable notice period.

After the 14 days, your organisation automatically switches to a read-only mode. You lose nothing: all existing data remains viewable. New actions such as creating surveys, publishing, resuming stopped surveys, creating new workspaces or inviting team members are only possible again once you have subscribed to an active plan.