Does the same logic of removing contacts from automation path apply to segments as it does to lists?

[NickS]

Hi there, I accidentally added my entire list to a segment and sent them down one of my automation paths.  I updated the segment logic to remove the people who aren't supposed to be on it.

From my reading of https://knowledgebase.constantcontact.com/email-digital-marketing/articles/KnowledgeBase/27937-Valid...

If a contact is removed from a list, they stop going through the path (also I'm using path / series interchangeably, please let me know if that's not correct).  Is this true for a segment as well? To ask another way: if a contact is removed from a segment, does it also get removed from the automated path that the segment is a trigger for?

[William_A]

Update: see Accepted Solution from Community user NickS.

Hello @NickS ,

Similar to how each step of a list-join Automation Path checks the contacts in the list before sending the upcoming step, the same will apply to segments. If you remove contacts from a segment associated with the path, then it will not send to those contacts further.

[NickS · Accepted solution]

Hi William - I have a message from David, Tier 2 Technical Support Specialist that suggests the opposite is true:

Incorrect: I originally informed the agent and passed on to you, that if you removed  a contact from a segment, they would not get the remaining emails in an automation series.

Correct:  A contact still receives emails in an automation series even if they are removed from the segment attached to it.

"If it's vital that these contacts not receive the remaining campaigns in that automation path, you will need to end the path unfortunately. We have written up a defect ticket for our developers to make them aware of it."

[William_A]

Thank you for providing that updated info from the Tier 2 agent. I'll mark your response as the Accepted Solution so it's more visible as the current situation regarding segment automations. 

[NickS]

I have called in to trouble shoot automations - the consistent answer has been that the dev team is looking into it, but there's no expected resolution date.