Can I enter two different redirect links to different panel providers on the same survey? | XM Community
Skip to main content

I’m working with one survey and we’re thinking of sourcing respondents from two different panel providers at the same time. I’ve already set up redirect URLs for provider #1, but we’re not getting enough responses, so we’re considering using provider #2. How can I configure redirects for the second panel on the same survey? From what I can tell, the 'End of Survey' block only allows one redirect link. Can someone assist?

I have a similar use case and essentially had to create 2 separate end of survey messages - one that goes to 1 link, and the 2nd going to another link. I use survey flow and condition sets to determine which end of survey message (link) gets displayed to the respondent. 

 


That makes sense—and it's actually the approach I was considering. Regarding the embedded data ID at the start of the survey flow, did you create a separate block for it as well? Here's what mine currently looks like. Should I add a new 'Set Embedded Data' block for provider #2’s ID?

 


Are you assigning the embedded data value on the contact level? If so you don’t need to add it in again.


Hi kgillis, I might be misunderstanding your question—this is my first time working with redirect URL links. My first panel provider gave me three separate links for Completes, Terminates, and Overquota. I was instructed to set their ID as embedded data at the very start of the survey flow. For example, their TERMINATE link looks like this: https://dig…com/exitlink?statusid=2&digid=${e://Field/digid} (I took out the full link for privacy), so I added 'digid' as an embedded data field at the beginning of my survey flow. I’m assuming provider #2 will use a different link and ID name, which is why I’m wondering if I need to add a second 'Set Embedded Data' block right after the one I already have.


Nope - the single embedded data of “digid” just as you have it shown above should capture it from all 3 of those links!


@MktgData did this work for you?