Redirect after completion

Someone completed your survey — five minutes of their time, honest answers. A "Thank you for participating" screen appears, and that's it, the interaction is over.

But it can be different: send them to a promo code, a personal recommendation, a product landing page, a thank-you video. Redirect after completion turns the end of a survey from a full stop into a comma: the user finishes one action and immediately moves into the next. This extends the interaction path and turns the survey into part of a funnel rather than its dead end.

Definition

Redirect After Completion — the automatic redirection of a respondent to a specified external page immediately after they finish a survey. It is set up as an alternative or supplement to the standard "Thank you" screen. It is used to pass parameters into a CRM, deliver a reward, move people into the next step of a funnel, and integrate the survey into complex user scenarios.

What it is used for

Delivering a reward. After a survey with a promised prize — a redirect to a page with a promo code, a downloadable file, or access to gated content. The promise "you will get X after the survey" must be fulfilled instantly, and a redirect makes that happen without extra steps.

Moving into the next funnel stage. A qualifying survey identified a "hot lead" — a redirect to a page for booking a call with a manager or scheduling a demo. A "cold" one — to a page with educational materials. The redirect logic is built in through logic jumps: different outcomes lead to different destination pages.

Integration with CRM and analytics systems. A redirect to a CRM endpoint with parameters in the URL is a simple way to pass response data without setting up an API or webhook. As a result, the lead automatically appears in the CRM with the corresponding fields filled in.

Continuing the interaction. A redirect to the product's main website, the corporate blog, or a page with recommendations based on the answers. The survey becomes part of a larger user journey.

Returning to the original context. When a survey is embedded in an app or a partner service, the redirect returns the user to the interface they came from. A seamless finish.

How it works technically

The basic mechanic is simple: after submitting the last answer, instead of the standard "Thank you," the user gets an HTTP redirect to the specified URL. Implementation options:

Simple redirect. One destination URL for all respondents. Configured in the survey settings: "after completion, redirect to [URL]."

Conditional redirect. Different URLs depending on the answers or scoring results. Implemented through branching: on the final step, a condition checks the score or a specific answer and sends the user to the corresponding page.

Redirect with parameters. Parameters carrying the user's answers are added to the URL. Example: https://crm.company.com/lead?email={email}&score={score}&source=survey. The values in curly braces are substituted from the answers via piping. This passes data to the target system without an API.

Delayed redirect. First a results screen with a message or personalized content is shown, and after a few seconds — an automatic transition. Or a redirect on a button click. A compromise between informing the user and moving them into the next step.

Example: a qualifying quiz with a conditional redirect

A SaaS company launches a "Find your plan" quiz. Depending on the scoring result, the redirect sends the respondent to different destination pages:

• Low score (0-30) → free sign-up with an educational email
• Medium score (31-60) → a pricing page with the recommended plan highlighted
• High score (61+) → booking a demo with a manager, with prefilled data (email, company, size)

Over a month, 1,200 people took the quiz. Of the high-scoring ones (180 people), 72 booked a demo — a 40% conversion rate. If everyone had seen a standard "Thank you" screen with a single "go to pricing" link, the conversion into demos would have been substantially lower — a search-driven path rather than a guided one.

Similarly, the medium-scoring respondents received personalized plan recommendations, and the low-scoring ones entered a nurture funnel. All three segments work through different scenarios via a single survey.

Redirect vs Welcome Screen vs Results Screen

Different survey screens perform different jobs:

• Welcome screen — the greeting screen before the questionnaire begins. It explains the purpose and length and motivates people to complete it.
• Results screen (the "Thank you" screen) — the final point: gratitude, confirmation of submission, and possibly a personalized message.
• Redirect after completion — a move to an external resource instead of or after the results screen. This is an active continuation of the interaction, not an ending.

They are often used together: the results screen shows a short message ("Thank you! You will now be redirected to your promo code"), and after 3-5 seconds the redirect fires.

Common mistakes when setting up a redirect

Redirect without warning. The user clicked "Submit" and suddenly ended up on a completely different site. This is disorienting. Better: show a short "Redirecting you to..." message with a countdown or a button.

Passing sensitive data in the URL. URL parameters are visible in the browser history, server logs, and referrer headers. Email and general data are acceptable. Card numbers, passwords, and personal documents — never pass these through a URL.

No fallback. If the destination page is unavailable or the URL is wrong, the user sees an error instead of a confirmation that they finished. Set up a standard results screen as a fallback that is shown if the redirect does not work.

Redirecting to a long external path without explanation. Moving from a survey to a demo booking page with 15 fields is a high barrier. If the next step requires a serious action, it is better to first show an intermediate screen with an explanation: "Your score is high — we suggest booking a demo where you will learn more."

Redirect in SurveyNinja

In SurveyNinja, the redirect is configured in the survey settings: you specify the destination URL, optionally with variables from the answers substituted in. For conditional redirects, logic jumps on the final screen are used: depending on the conditions, the user lands on different versions of the results screen, each with its own redirect. To pass data to a CRM or external systems without setting up an API, use URL parameters with answer piping.

More on configuring final screens can be found in the results screen documentation. For complex scenarios with the transfer of structured data, it is more convenient to use webhooks, but for simple cases a redirect with parameters is a quick way to integrate a survey into an existing process.

Redirect after completion turns a survey from an isolated data-collection point into a node in the user journey. A well-configured redirect is personalized (different URLs for different segments), passes data for the next step, warns the user, and works even on error (a fallback to the standard screen). Without a redirect, the survey ends with the word "thank you"; with one, it triggers the next action.

Frequently asked questions

Do you have to replace the results screen with a redirect?

No, you can use both: first a short results screen with a confirmation and a countdown, then an automatic redirect. This lets the respondent understand that the survey finished successfully while moving them into the next step. A pure redirect without a message is an option for cases where the speed of the transition matters more than confirmation.

Can you use different redirects for different respondents?

Yes, through logic jumps on the final step. Depending on the answers, the scoring result, or hidden variables, different respondent segments land on different URLs. This is the main way to personalize the path: a hot lead → a demo, a cold one → educational content.

What should and should not be passed in URL parameters?

You can pass: email (if collected), basic demographic data, the scoring result, a source identifier (UTM), and answers to key questions. You should not pass: bank card numbers, passwords, document numbers, or any data that should not end up in logs and browser history. To transfer sensitive data, use encrypted webhooks rather than a URL.

How can you tell that the redirect worked?

On the destination page, set up tracking of arrivals from the source — through UTM parameters in the redirect URL. In systems like Google Analytics or Yandex.Metrica, visits with the utm_source=survey tag will appear. Alternatively: a pixel or an event on the destination page that triggers when someone arrives from the survey.

What should you do if the target server is temporarily unavailable?

Set up a fallback: if the redirect does not fire or the destination page returns an error, the respondent sees a standard results screen with a "Try later" button or support contacts. This prevents the situation where a user completed the survey but did not receive the promised reward because of a technical error.