Rory Colsell what's the latest on this? You were revisiting beginning of this year? :) thanks!
Jade Lander
•
May 26, 2021
Yes yes yes!
Teal Ox
•
Feb 19, 2021
need need need
Tomato Beach
•
Sep 8, 2020
I can see this feature is now planned since aug. 2019. Any news on how far ahead this feature is?
Beige Quesadilla
•
Nov 27, 2019
Chris Hexton - Would this include when someone exits a campaign/workflow? For example, when a goal is reached in one workflow/campaign, it would trigger an event that could be used to put them into a different workflow/campaign.
Chris Hexton
Team•
Nov 27, 2019
Chad Halvorson: We haven't quite decided what we'll roll out here. We definitely know that people want to schedule Workflows based on other sends (e.g. triggering follow ups to a newsletter is the most basic use case).
A few things we have been thinking about:
Customers have asked to record clicks or opens as a "conversion" in a workflow.
Customers have asked to have "update a user property" as an action in a workflow.
Customers have asked to have "update a user property" as a "conversion" in a workflow.
Customers have asked to have "enters segment" as a workflow trigger.
Do you think that if we had 1-3 above, it'd mean there was no need to have "completed workflow", etc. as a trigger? Instead, you could update a user property to record the user's state and then use "Enters that segment" to trigger the next workflow?
We could build out all of the above! We just want to think it through so we don't create a scenario where you could do everything 5 different ways, as we think that'll make maintaining Workflows tricky!
Beige Quesadilla
•
Nov 28, 2019
Chris Hexton: Thanks Chris. I think 1-3 would create useful flexibility. Would what you are describing in this feature allow me to set an "entry trigger" for a campaign based on someone entering a segment? If so, that could work. The problem I see needing to be solved is an easy/flexible way to define "entry trigger" or "exit trigger" users from workflow that isn't limited to triggering API events externally.
Specifically on the #1 in your note above, it would be useful to be able to select the specific link in the workflow as the click that records as "conversion". Note: The specific "conversion" link may be unique per user, so it would need to be flagged as the "conversion_link" with a class name or something… i would think.
cc: Ellen Falk
Chris Hexton
Team•
Dec 3, 2019
Chad Halvorson:
Would what you are describing in this feature allow me to set an "entry trigger" for a campaign based on someone entering a segment? If so, that could work.
Exactly right, that's what it'd enable.
The problem I see needing to be solved is an easy/flexible way to define "entry trigger" or "exit trigger" users from workflow that isn't limited to triggering API events externally.
That is definitely a primary goal of this feature request. The "Enters segment" should solve this (at least, it's one approach to do so!)
Out of interest on this question, what are the triggers? I.e. is it a person changing their state, represented by a user property that is updated? What I'm keen to dig into here are examples of use cases you can't do now that you are hoping we can enable.
Specifically on the #1 in your note above, it would be useful to be able to select the specific link in the workflow as the click that records as "conversion".
This definitely makes sense, the clicking in aggregate is already tracked, so it'd be about specificity for this one :).
Coffee Nebula
•
Aug 29, 2019
PLEASEEEEE!!!!!!!!!!
Gold Beaver
•
Aug 1, 2019
Yup. This is pretty critical for the kind of thing we're moving in to. +1. IMHO email events are just as much part of the picture as behavioral events…
Sapphire Cascade
•
Mar 25, 2019
This is a must for us!
Apricot Berry
•
Jan 30, 2019
I'd love this too, .. super useful to be able to build our workflows based on doing an initial newsletter .. then using the email events attached to this (opened, clicked etc) to then run a sequence
Log in to comment and vote
Comments12
Jade Lander
May 26, 2021
Rory Colsell what's the latest on this? You were revisiting beginning of this year? :) thanks!
Jade Lander
May 26, 2021
Yes yes yes!
Teal Ox
Feb 19, 2021
need need need
Tomato Beach
Sep 8, 2020
I can see this feature is now planned since aug. 2019. Any news on how far ahead this feature is?
Beige Quesadilla
Nov 27, 2019
Chris Hexton - Would this include when someone exits a campaign/workflow? For example, when a goal is reached in one workflow/campaign, it would trigger an event that could be used to put them into a different workflow/campaign.
Chris Hexton
Nov 27, 2019
Chad Halvorson: We haven't quite decided what we'll roll out here. We definitely know that people want to schedule Workflows based on other sends (e.g. triggering follow ups to a newsletter is the most basic use case).
A few things we have been thinking about:
Customers have asked to record clicks or opens as a "conversion" in a workflow.
Customers have asked to have "update a user property" as an action in a workflow.
Customers have asked to have "update a user property" as a "conversion" in a workflow.
Customers have asked to have "enters segment" as a workflow trigger.
Do you think that if we had 1-3 above, it'd mean there was no need to have "completed workflow", etc. as a trigger? Instead, you could update a user property to record the user's state and then use "Enters that segment" to trigger the next workflow?
We could build out all of the above! We just want to think it through so we don't create a scenario where you could do everything 5 different ways, as we think that'll make maintaining Workflows tricky!
Beige Quesadilla
Nov 28, 2019
Chris Hexton: Thanks Chris. I think 1-3 would create useful flexibility. Would what you are describing in this feature allow me to set an "entry trigger" for a campaign based on someone entering a segment? If so, that could work. The problem I see needing to be solved is an easy/flexible way to define "entry trigger" or "exit trigger" users from workflow that isn't limited to triggering API events externally.
Specifically on the #1 in your note above, it would be useful to be able to select the specific link in the workflow as the click that records as "conversion". Note: The specific "conversion" link may be unique per user, so it would need to be flagged as the "conversion_link" with a class name or something… i would think.
cc: Ellen Falk
Chris Hexton
Dec 3, 2019
Chad Halvorson:
Exactly right, that's what it'd enable.
That is definitely a primary goal of this feature request. The "Enters segment" should solve this (at least, it's one approach to do so!)
Out of interest on this question, what are the triggers? I.e. is it a person changing their state, represented by a user property that is updated? What I'm keen to dig into here are examples of use cases you can't do now that you are hoping we can enable.
This definitely makes sense, the clicking in aggregate is already tracked, so it'd be about specificity for this one :).
Coffee Nebula
Aug 29, 2019
PLEASEEEEE!!!!!!!!!!
Gold Beaver
Aug 1, 2019
Yup. This is pretty critical for the kind of thing we're moving in to. +1. IMHO email events are just as much part of the picture as behavioral events…
Sapphire Cascade
Mar 25, 2019
This is a must for us!
Apricot Berry
Jan 30, 2019
I'd love this too, .. super useful to be able to build our workflows based on doing an initial newsletter .. then using the email events attached to this (opened, clicked etc) to then run a sequence