Skip to main content

Please continue to support branching based on the status of the CTA in the previous step in the new Program.  According to this ticket, it is no longer supported: 296992

We have many CTA statuses that could cause different next steps within a program.  Today in the existing program, we can use the previous step and select the Status Reporting Category.  The only option in the new program is CTA not Closed or CTA Closed.  We need to rive different actions if the CTA was successful or unsuccessful.  Bonus if we could do this in an evaluation steps and pick ant CTA attribute instead of just the status reporting categories, but at minimum we need to distinguish on reporting category. 

It doesn’t make sense to limit the CTA statuses in the built-in evaluate steps that follow a CTA.

Similarly, it would be great if we could choose which outcome we wanted to have for emails (ex: clicked/not clicked), rather than just “opened/not opened” so we didn’t have to bring in an extra evaluate step to check the audience fields.

 

Edit to the above (can’t edit my comment):

It would be great if we could choose which outcome we wanted to have for emails (ex: clicked/not clicked), rather than just “opened/not opened” so we didn’t have to bring in an extra evaluate step to check the Previous Steps.

 

​@angela_domenichelli - we had released this a while ago—does this help?

 

Terms & ConditionsCookie settings