Skip to main content
Contributor ⭐️
October 5, 2026

Best way to dynamically exclude survey respondents from a Journey Orchestrator reminder send?

New to gainsight here so still learning some of the ropes but wanted to ask for some help on automation.

We're running a reminder email program in Journey Orchestrator for a survey campaign. Each recipient gets a Typeform link with a unique trackid embedded as a tokenized field, so we can tie a submission back to the original recipient.

The problem: people who've already completed the survey are still getting the reminder, because there's currently no automated way to pull them out of the next send before it goes.

What I'd like to build: when someone submits the Typeform, that updates a field in Gainsight against that trackid/identifier that then says they did the survey. I’d use that field in an evaluation step to then exclude those from the send of the reminder email a week later. 

I know the Program-level Exclusion List is CSV-upload only, so that's not a fit for something that needs to update continuously. Would love to hear if anyone's done a Typeform (or similar external form) → Gainsight integration like this and has lessons learned.

3 replies

Sanchita
Gainsight Employee ⭐️
Gainsight Employee ⭐️
October 6, 2026

Hi ​@joe.spina 

I hope you’re doing well! 

We could use the survey outcome option here which shows 2 options, responded/not responded which is captured in Gainsight and then we could branch it out accordingly. 

 

 

Translate
joe.spinaAuthor
Contributor ⭐️
October 6, 2026

Hi ​@Sanchita thanks for the response! Would that only work if they use gainsight native survey? This survey is in typeform so we want to use the knowledge of if they complete that survey to have them not receive the reminder email we send in the journey. Right now we are cloning the journey and then adding the exclusion of those that completed as a CSV each time before sending. 

Translate
Sanchita
Gainsight Employee ⭐️
Gainsight Employee ⭐️
October 8, 2026

Hi ​@joe.spina 

Yes, it would work only for native surveys. Instead of a CSV we could create 2 JO’s running. The first JO would send the initial survey and the second JO would make use of the first JO object namely, AO object as an audience and add filters consisting of the first JO name, participants who have completed the first JO, exclude them from syncing in second JO, and send emails only to participants who have not responded to first JO survey. 

Translate