To my knowledge, there is no way to do that. Neither via backend Control nor through the API (I just looked again). 

The user has to take that action themselves. 

I recall there being various ideas about that over the years, but I couldn’t find a good one to link here. Maybe I’m wrong about the functionality ​@Kenneth R can correct me. (If not, can you please link the most appropriate idea here Kennth?)

Candidly, this has been a concerning pain point for some time and I’m surprised it hasn’t been addressed due to the compliance implications with various regulations. 

Here’s a work around to help you in the mean time. 

1. Custom Role for Unsubscribes
2. Automate assigning this role (via the API) when someone unsubscribes via your other email marketing tool(s)
3. Set strict rules to always ensure your distribution list for an email does not include users with that role
   • This will be a challenge when building your audience lists and prevents you from using Automated Email Campaigns (Segments are not yet supported)

It’s a bit more complex, but I’d actually advise this approach: 

1. Custom Role for Opt-In to Email Campaigns
   • Bulk add to all existing users
   • Automate adding it to all net-new users
   • You don’t need to worry about when they unsubscribe from Email Campaigns via the CC unsubscribe option in the email or via their profile settings, CC will respect that preference even if they have the Opt-IN role on their profile. It just may be a bit confusing. 
     • Caveat: unless you’re looking to do the same thing, where an unsubscribe to community email campaigns needs to push to your other systems…  
2. Automate Removing this role when someone unsubscribes via your other marketing tool(s)
3. Set strict rules to always INCLUDE that opt-in role in your audience definition 
   • Building lists that are a mix of Role includes and role does not include isn’t supported, this solves that. If you need to email to a role-based list, your list criteria is that they have  {role} and {opt-in role}
   • Automated Email Campaigns would support this approach

One way to help ensure compliance to #3 in above: 

Create an email campaign that’s your Template. Set the recipient criteria to include the Opt-In role. 

Then train your team to always clone that email first, rather than use the button to create a new Email from scratch. 

Last thought: I imagine Gainsight support could do the unsubscribes in bulk on their end to get you up to compliance ASAP for those who have unsubscribed thus far. 

But you’d need something like the workaround above to maintain compliance for net new unsubscribes. 

Hi ​@DannyPancratz, 

Thank you for the advice and those suggested workarounds. I was thinking a custom role might be the best way to go if this functionality wasn’t available. I appreciate your thoughts! Thank you! I posted this as an idea as well if you’d like to add your vote to it. 

Just an update on this, creating a custom role to unsubscribe users doesn’t quite work because in email campaigns you are not able to omit custom roles, you can only select filters to include users. The second approach you outlined would work best for because of this. 

​@DannyPancratz, 
I have another question! When setting up email triggers for an automated email do you know if adding two different roles further narrows the scope of the email or expands it to include both roles? 

For example, I created a ‘subscribed role’ based on our conversation above, and applied that along with another role. Will it send to all people who are subscribed or only to people who have both roles?

It should narrow the scope. I believe I tested that scenario out when I put together the scenario above. 

However, it should also give you a count of users when you select the criteria for your email campaign, which would allow you to validate that it narrowed. 

Okay thank you for confirming. I don’t know if the user count is shown on automated email campaigns. I can see the user count in one-offs which lets you use user segments. 

Ahhh… I didn’t catch the Automated Email part. 

It should work exactly the same. 

The reason why you don’t see the count is because the count changes dynamically; when a user meets the criteria set, they are sent the email. I assume they chose not to show the count in the UI for that reason. 

That makes sense, thanks for helping again!