I’m trying to figure out how to create a dynamic list depending on how a prospect fills out our subscribe to newsletter form which takes a contact on an email nurture workflow depending on how they have responded e.g. they choose Job title X and not Job title Y under What best describes your role?
Basically if you choose Job title X, you then go into the X Workflow. If you chose Job title Y, you are pushed into the Y Worfklow.
I know at a basic level, I need to create a form (done), dynamic list (problem setting up), dedicated workflows (setting up), and workflow criteria/triggers (setting up).
I think my issue is with the dynamic list - I’ve tested it out and it’s not capturing the contacts I’ve fed into the forms for testing purposes. In my dynamic lists, I’ve used Custom Property (Job title X), and Form Submission as the filters.
Can someone please educate me on how best to do the above? Much appreciated!
Hey ILLYO! Have you tried adding them to the list from the workflow? I am wondering if you are running into a delay between when the initial workflow runs and the dynamic list gets the properties needed to include the contact
I think if you were to include them being added to a list as one of the workflow steps this would solve it. You could even connect the dynamic list to that list as well.
Is there a particular reason that you want active lists in the mix? Generally, when I’m able to avoid additional assets as required building blocks for a process, I will avoid them. More assets mean there’s a higher likelihood of something not working as expected.
In your case that means the following: Your nurturing workflow could start off with a branch which acts like the sorting hat in Hogwarts, checks criteria of each contact and then sends them down their own nurturing path – all within one workflow.
The only reason to create multiple workflows would be if you want to have workflow analytics for each single track and want to be able to analyze each one individually.
The benefit of having just one workflow is that workflow branches, by default, always have a last branch that catches all contacts who did not meet earlier criteria.
(This might look slightly different for you. I had to switch to the old workflows user interface to get all information in one screenshot.)
If you decide that you definitely want separate workflows, you still wouldn’t need lists, technically. You could move the criterion of the job title up into the enrollment triggers: has filled out form + has opted into + job title is equal to, then send your nurturing emails.
I like the idea of having one workflow. I’ll try and build it as you’ve suggested above.
What if the criteria is not a job title? I have shared the exact form that we have across our website that subscribes users in the specific email nurture.
The filtering question is What best describes your construction business?
Then, depending on how the user responds, they will be sent to the specific content branch.
