Hey Peter -
To echo Sanford, you don't need to do this. As he said, "if a Data Value Changes trigger brings someone into a flow, they don't get booted from the flow if the value changes again later. They're already in the flow." In other words, say Laura completes form and chooses Product A, I'm guessing this kicks off a smart campaign something like this:
Trigger
Data Value Changes->New Value is: Product A
Flow:
Send Product A EM1
Wait
Send Product A EM2
Wait
Send Product A EM3
etc.
If Laura comes back and fills in the same form again and chooses Product B, presumably that will kick off:
Trigger
Data Value Changes->New Value is: Product B
Flow:
Send Product B EM1
Wait
Send Product B EM2
etc.
The fact that the Data Value was changed to Product B later, has no impact on the chain of events triggered by the selection of Product A.
And where Sanford said "And you can (and probably should) be using list or program membership to permanently record their interest anyway.", you can insert something like this into your flow so that you keep track:
Trigger:
Data Value Changes->Product Interest-New Value=Product A
Flow:
Add to List
Choice 1:
If Product Interest = Product A
Add to List: Interested in Product A
Choice 2:
If Product Interest = Product B
Add to List: Interested in Product B
Send EM1 for Product A
Wait xxx
Send EM2 for Product A
Hope that helps!
- Denise
This is fantastic information.
Thank you all so much!
Before I start processing the latest suggestions, one quick question:
Would checking the Multiple Selections box on the drop down select field editor solve this problem?
Would checking the Multiple Selections box on the drop down select field editor solve this problem?
That would turn the <select> into a <select multiple>. It's a standard HTML widget, but looks different from a single-select <select>. If the client is cool with it then it'll work well.
Thanks yet again, Sanford.
I've decided to keep the dropdown, then create lists to track the product interest, which I have to do anyway to provide product-specific email communications.
Denise, thanks again.
You're right about the email flows following the form submissions.
Part of my puzzle is that I don't want to kick off multiple email drips at one time. And I don't want people making more than one product choice on the first form submission.
I think the way to handle this is to use lists, as you've suggested.
I've pushed the customer on checkboxes, and I'll wait and see what they say.
Thanks!
Hi Peter,
Re: Part of my puzzle is that I don't want to kick off multiple email drips at one time.
I thought in an earlier post you had said that you DID want to kick off multiple email drips. Maybe you mean you don't want them going at the same time. If that's the case, there are a variety of ways that you could accomplish that: - but recommending exactly how to do that would require a lot more detail about your particular setup and goals. At a high level, here are a couple of options:
1) Create separate drip campaigns for each of your 5 products and don't let someone into email drip 2 if they are already in email drip 1 until the have received the last drip 1 email.
2) Create Engagement Programs for each of the products and have them send on alternate weeks
Re: And I don't want people making more than one product choice on the first form submission.
Use radio buttons - or use the drop down without enabling multi-select.
Denise
Thanks Denise. You're correct, I don't want people getting separate email drips at the same time.
I've landed on using the dropdown as the client prefers, and creating lists that capture product specific interest.
That way, a prospect would really have to go out of their way to get into two drip campaigns, in which case I don't mind sending them the additional email.
Thanks again for your help!