Help
Frequently asked questions about uxspire
Answers about audience studies, surveys, UX metrics, data protection, integration and plans. Search for a term or filter by topic.
Questions and answers
A survey with several structured questions whose answers uxspire groups into segments. Respondents with similar answer patterns end up in the same segment. A persona set card describes each segment: what matters more or less to this group than on average, what it is missing and which change you could test.
The analysis starts from 100 completed responses to a published study. That is a technical minimum, not proof of representativeness. The quality notes show whether the segments hold up; plan for more responses where possible.
No. Single and multiple choice, ratings, numbers and Likert scales feed into segmentation. You read free text per segment because it shows reasons and wording, but it does not change the segments.
The analysis tests solutions with 2 to 5 segments and recommends the smallest suitable one. Only solutions with at least 10 people in the smallest segment and sufficiently stable segment statements can be confirmed. If no solution meets these limits, the analysis says so openly.
From you: you survey your own customers and shop visitors by link, for example in your newsletter, or embedded in your shop. uxspire does not provide a survey panel and does not recruit participants.
There are 23 German-language templates, including “E-Commerce generisch” and templates for fashion, electronics, furniture and groceries. You can upload your own templates as JSON files. Respondents answer in German or English, and the app interface is available in English and German.
Four analysis views of the same segments (Comparison, Matrix, Radar, Focus), a persona set card per segment as PDF and all responses as CSV. The e-commerce example study (in German) shows what this looks like.
uxspire is software for audience studies in e-commerce. Shops use it to survey their own customers, identify segments with different purchase motives and barriers, and use persona set cards for decisions about their shop, offer and messaging. Surveys and the UX metrics NPS, CSAT and UEQ complement the offer.
For online retailers and D2C brands with their own shop that can reach their customers and act on findings: e-commerce leads, performance marketing, shop and UX owners and CRM teams. You do not need statistical knowledge for the analysis; the shop integration is best done by someone with access to the shop template.
Your organisation contains projects, for example one per shop. Each project has its own integration key and its own surveys, UX metrics and audience studies. Team members get the role Admin, Editor or Viewer, either for all projects or only for selected projects.
uxspire is not a product analytics tool: heatmaps, session recordings, funnel analysis and usability testing are not part of the offer. Neither are a survey panel, transferring segments into advertising audiences or a connection to shop revenue.
uxspire is built with data protection in mind and respects signals such as Global Privacy Control and Do Not Track. Whether your specific use is lawful also depends on your legal basis, your consent solution, your privacy notices and the questions you ask. A blanket seal would therefore be misleading; details are in the privacy policy, the DPA and the CMP integration guide.
Yes. For Demo and self-service plans, the online DPA applies where uxspire processes personal data on your behalf. Enterprise contracts or individual offers may use a separately agreed DPA.
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.
The application runs on Microsoft Azure in an EU region. Survey assets and consent records are stored or delivered via Cloudflare R2 with EU jurisdiction. Payments are processed by Stripe. Details on service providers are in the privacy policy.
That depends on the plan: 15 days on the Demo plan, 6 months on Starter, 13 months on Growth and 25 months on Enterprise. We keep invoice and contract data longer for legal reasons.
Yes. Embedded surveys only start once your consent management platform allows them; calling uxspire.setConsent({ tracking: false }) stops collection and the delivery of embeds again. Signals such as Global Privacy Control and Do Not Track are respected by default.
Yes. Via the POST /api/v1/privacy/deletions endpoint, you submit up to 100 IDs of a project per request for deletion. The endpoint uses a server-side privacy key and remains available even when collection is blocked because a Demo access has expired or quotas are used up. Without code, admins can process a deletion request in the dashboard under Settings → Privacy.
Surveys shared by link need no integration. For embedded surveys, you add an asynchronous script with your project key to the shop template once, directly or via a tag manager. After that, you manage surveys, metrics and studies in the app without touching the shop code again.
No. You add the script once. Which survey appears where is then controlled in the app via URL patterns, CSS selectors and insert positions.
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 stores answers to your surveys and events that you actively send via the SDK or the HTTP API. It does not record clicks, mouse movements or screen content.
There are no direct connections to tools such as Google Analytics, Slack or Jira. You export responses and results as CSV; events can be sent via the HTTP API. Both fit into existing analyses.
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.
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 Starter, Growth 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.
8 question types: short text, long text, single choice, multiple choice, rating, number, Likert and ranking, each optionally with an image. Welcome and thank-you screens as well as display rules and branching control the flow.
As a public link, inline in the page content, as a modal or on exit intent shortly before someone leaves the page. The link can be combined with exactly one embedded option. Exit intent reacts mainly to mouse movements and therefore makes sense primarily on desktop.
Standardised metrics for the experience from the customer’s point of view: Net Promoter Score (NPS), Customer Satisfaction Score (CSAT), User Experience Questionnaire (UEQ) and its short version UEQ-S. They are embedded in your shop as a modal or inline; the respondent language, German or English, is fixed per instrument.
You see trends for 7, 30 or 90 days or all time, filter by delivery channel and survey version as well as by device, campaign, origin, page, visitor type, country, browser and operating system, and read results per question, free text and a word cloud. All responses can be exported as CSV; the file follows the active filters.
Yes. Every survey and every metric has its own theme for colours, fonts and layout; you can save proven settings as a template. Custom CSS is included from the Growth plan.
A survey answers one specific question, such as what is missing on a product page. An audience study looks at answer patterns across several questions and shows which customer groups differ and how large they are.
uxspire is currently running in closed beta with selected teams. Join the waiting list and we'll let you know as soon as your access is available. Your organisation then starts on the Demo plan. You can sign up via the contact form.
Starter from €50 per month, Growth from €1,000 per month and Enterprise on request, all excluding VAT. The plans differ mainly in how many audience studies run at the same time and how many responses count per month. All details are on the pricing page.
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 primarily cancel their subscription in the billing settings or the Stripe customer portal of the app. Alternatively, you can cancel in text form by email to , observing the notice periods, if the billing settings or the Stripe customer portal are unavailable or cannot be used. Such messages are processed manually. The cancellation takes effect at the end of the billing period already paid.
After 14 days, your organisation automatically switches to read-only mode. Existing data remains visible. You can create or publish new surveys and invite team members again once a plan is active.
Responses beyond the monthly quota are not stored. Existing responses and analyses remain available; the quota is available again with the next billing period. You can move to a larger plan at any time.
Can’t find your question? Write to us.