Survey links only allowing one completion due to distribution (Q_DL) | Experience Community
Skip to main content
Question

Survey links only allowing one completion due to distribution (Q_DL)

  • February 2, 2026
  • 2 replies
  • 23 views

Forum|alt.badge.img

HI, we set up links for a client survey with embedded data, where the emails were being sent outside of Qualtrics, so we wanted one link per client with the embedded data.

we set up links such as this one, not realising that the link was a single use link only.  https://brighthorizonsuk.qualtrics.com/jfe/form/SV_51JQPCgiTrJPlvE?Q_CHL=gl&Q_DL=EMD_A67fov1Y7u2BgsH_51JQPCgiTrJPlvE_CGC_YHN0fKLZTPreSoQ&_g_=g

however we want to use these links for multiple uses e.g. for any employees at that client without changing the link. (we know what to do for the future)

Can anyone confirm if links containing Q_DL can be repurposed or reused for multiple completes, even if survey security settings allow multiple submissions

2 replies

kgillis
Level 6 ●●●●●●
Forum|alt.badge.img+30
  • Level 6 ●●●●●●
  • February 3, 2026

I cannot confirm there, I would recommend testing but I have a similar case in my org. So instead of creating links with the embedded data we simply append URLs that then pass the embedded data back into the survey. This allows for us to send surveys and create “personal style” links (although on paper they’re anonymous links - BUT we are capturing all their data through the appended URL) from a 3rd party sending system. 


Forum|alt.badge.img+24

Not sure if it is suitable for your case.

In my situation, I would pause the survey to stop any ongoing session or new session creation, then delete the distribution to break the links, followed by resending a new distribution.

 

Appending query strings is a nice alternative as mentioned above by kgillis.

However, extremely rare possibility of data corruption may still exist when respondents paste the url instead of clicking on link to open survey, where part of the query string gets corrupted by respondents by accident and may not be spotted easily.

For example, “...Name=Joan” becoming “...Name=Jocan” by an additional c before pressing enter.