Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot use survey metadata in the Confirmation Page link #520

Open
marcomb opened this issue Nov 7, 2023 · 4 comments
Open

Cannot use survey metadata in the Confirmation Page link #520

marcomb opened this issue Nov 7, 2023 · 4 comments
Assignees

Comments

@marcomb
Copy link

marcomb commented Nov 7, 2023

Describe the bug
Cannot use survey metadata with the Confirmation Page link setting.
As you can see in attached figure, there is in the "Complete link" field a HTTPS external website link to call when the survey is submitted (completed and confirmed)
The syntax used is "../Survey/Complete?ProjectToken={ContributionID}"

To Reproduce
Steps to reproduce the behavior:

  1. Create a test survey with 1 question.
  2. Click Properties
  3. Scroll down to Special Page -> Confirmation page
  4. Fill the field with a HTTPS URL and attach at the end a variable with the metadata "Contribution ID" (see pics)
  5. Save the form
  6. Try to submit 1 survey

Expected behavior
The Survey form is submitted and then the redirect to the confirmation link is holding the ContributionID
{ContributionID} must be replaced with the current ContributionID of the submitted survey, and so I expect to have a URL that is
"../Survey/Complete?ProjectToken=187fec87-d66e-4439-97e8-2e39446ec116

Screenshots
Special Pages

Desktop (please complete the following information):

  • OS: Windows 11
  • Browser: Chrome
  • Version: 118
@origabe origabe self-assigned this Mar 4, 2024
@origabe
Copy link
Contributor

origabe commented Mar 4, 2024

Dear @marcomb,
Indeed currently it is only possible to use the metadata tags within the text confirmation page. Not in the Link option.
Could you please explain what is the business case behind this need?
Thank you!

@marcomb
Copy link
Author

marcomb commented Mar 6, 2024

Yes.
We need to run a survey in collaboration with an external contractor that is taking care to submit our survey to a certain specific audience and in certain EU countries. Our contractor need the possibility to have a more advanced redirect in order to integrate EU Survey with its survey system (often a CRM-bases platform).

They are asking to have more than one redirect:

  1. “Complete” is for the panelists who belong to the wanted target and who complete the questionnaire.
  2. “Screen out” is for the panelists who don’t belong to the target and who are not supposed to complete the questionnaire
  3. “Quota full” : to use in the case we want to implement quotas (a max number of submissions).

All 3 external link need to have the token ID passed through in order to align the data collection

An example of link is:
Complete https://passback.lifepointspanel.com/Survey/Complete?ProjectToken=f459004b-400f-44e9-9f32-f5a3e147864a

So, the simplest possibility IMHO, is keeping just the "Confirmation Page" external link adding the EU Survey generated Token ID as query string parameter.
This integration requirement seems something requested by several providers, probably because many of them are using their own survey platform

clam2310 added a commit that referenced this issue Mar 11, 2024
clam2310 added a commit that referenced this issue Mar 11, 2024
@marcomb
Copy link
Author

marcomb commented Mar 11, 2024

The required "external link" that we need to set into EU Survey settings is

https://dkr1.domain.com/projects/end?rst=1&psid=XXXX

where XXXX is the captured value for PSID

Is it possible to implement this change?

@feketga
Copy link

feketga commented Jun 19, 2024

Improvement ticket was created for your request (ESURVEY-8427), you will be informed about any update on it. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants