Hello, everyone. I am a senior software engineer given the requirement to integrate a qualtrics survey into the normal flow of our transactions. The result need not be instantaneous, but the key point is that the customer must complete the survey before continuing on to the next step, which in this case is to get an artifact. So the flow is: 1) Customer presses a button "Get thing". 2) If the customer has not already taken the survey, they are redirected to the survey. They take the survey. 3) After the survey is done, they return to our website and are presented with the window again. This time, they press "get thing" and get their new , shiny thing! Let's call the thing uniquely identifying this operation as 'transactionID'. A user can have many transactions in flight at the same time, so we can't just assume that the customer id uniquely identifies the transaction in question. So ... how to implement this? I can think of two solutions: Solution 1: Site-Intercept logic on qualtrics survey. 1A) User presses button. Goes to a qualtrics survey. 1B) survey site-intercept captures the transactionID and adds it to the response's embedded data. 1C) User takes the survey. When the response is completed, our system is notified by a webhook on response.completed, which tells us both that a response is completed and the responseID that was so completed. 1D) Using the survey response endpoint, we query based on the response id. This returns the response and the embedded data associated with it. We pull the transactionID (stored in 1B) from the embedded data. We then mark the transaction associated with transactionID something like 'survey complete' in our own system. 1E) The customer is now free to walk home with their shiny new thing! SOLUTION 2: Programmatically create response. In this case, we don't bother with doing anything on the qualtrics side. Instead, we create the survey and the questions and so forth entirely on our own web site, then use the qualtrics API to create the response with questions and answers programmatically. In this case, we don't need site intercepts or webhooks or additional calls -- since we know on our own system when the user has completed the survey, we can mark it 'survey complete' ourselves. These are the two proofs-of-concepts I have come up with to answer the requirement. What do you think? I'm looking for a second set of eyes here. Are there any gaping flaws with either solution? Is there a third method I have missed that is easier? Respectfully, Brian P.

IMHO, option 2 appears to be more stable. Conventional marketing wisdom says that the path to purchase should be as smooth as possible, therefore, I would try to avoid as many redirects as possible.I'm not sure how site-intercept works, but one options could be to open the survey in a modal and capture the information from there.

No, its not webhooks.In the support pages, read up on: Customizing End of Survey elementPassing query string parameters to surveys I would strongly recommend against this solution. Imagine yourself in the customers shoes, your about to place and order, and all of sudden you are redirected to some random survey.🙄

Integrating Qualtrics survey into a transaction flow

Integrating Qualtrics survey into a transaction flow | Experience Community

Sign up

Login to the Community

Scanning file for viruses.

This file cannot be downloaded