Integration Setup Survey

Integrations are how your product fits into a customer's existing stack. A good integration setup feels effortless. A bad one creates the kind of frustration that makes customers question whether your product is worth the trouble.

An integration setup survey captures feedback immediately after a user connects your product with another tool. It measures how smooth the process was, what went wrong, and whether the integration works as expected.

When to deploy an integration setup survey

Immediately after integration completion. Trigger the survey the moment a user successfully connects an integration. The experience is fresh and the feedback is specific.

After a failed integration attempt. If a user starts setting up an integration but does not complete it, trigger a survey asking what went wrong. This captures the exact friction point.

One week after setup. A follow-up survey after a week of use measures whether the integration works reliably in practice, not just during initial setup.

Integration setup survey questions

Post-setup survey:

1. How easy was it to set up the [integration name] integration? | 1-5 scale (Very difficult to Very easy) | Required
2. Did you encounter any issues during setup? | Yes / No | Required
3. If yes, what happened? | Open text | Conditional
4. How well does the integration meet your expectations so far? | 1-5 scale (Not at all to Completely) | Optional
5. Is there anything the integration does not do that you expected it to? | Open text | Optional

Post-failure survey:

1. What prevented you from completing the [integration name] setup? | Multiple choice (Could not find the right settings, Authentication failed, Instructions were unclear, Got an error I could not resolve, Needed a feature that was not available, Other) | Required
2. Would better documentation have helped? | Yes / Probably / No | Optional
3. Would you like help setting up this integration? | Yes / No | Optional

One-week follow-up:

1. Has the [integration name] integration been working reliably? | Yes / Mostly / No | Required
2. How often do you use the integration? | Daily / Weekly / Rarely / Stopped using it | Optional
3. What could we improve about this integration? | Open text | Optional

What integration survey data reveals

Setup friction hotspots. If ease-of-setup scores vary significantly across integrations, the low-scoring ones need better documentation, simplified auth flows, or UX improvements.

Documentation gaps. High rates of "instructions were unclear" point to documentation problems. Cross-reference with the specific integration to identify which setup guides need rewriting.

Expectation mismatches. Question five ("does not do what I expected") reveals where your integration description overpromises or where users have needs your integration does not cover.

Reliability issues. The one-week follow-up catches integrations that work during setup but fail during actual use. Intermittent sync issues, rate limiting problems, and data mapping errors surface here.

Common mistakes

Not surveying failed setups. Users who could not complete the integration are the most important to hear from. They have specific, actionable friction data.

Surveying only at setup. Integration quality is about ongoing reliability, not just initial connection. The one-week follow-up catches issues that setup surveys miss.

Generic questions. "How was the integration?" is too vague. Reference the specific integration by name so the user knows what they are evaluating.

Set up this survey in Formbricks

Formbricks can trigger integration surveys based on custom events. Fire an event when an integration is completed (or abandoned), and the survey appears in context. The template supports different question sets for successful setups, failed attempts, and follow-up reliability checks.

Responses are tagged with the integration name and user attributes, so you can compare setup experience across all your integrations and identify which ones need the most attention.