Email Opt Out page to direct to 3rd party site

@katie_b Thanks for posting it here. Redirecting this to our product team.

@katie_b  not sure your setup. We have the same issue. Our workaround was to set up fields on the SFDC Contact Record that map from the Marketo and the GS Opt Out Options. I then added fields on the Person object that maps to the same fields. We have a rule that updates GS Person from SFDC with the Marketo fields, and a rule from GS to Person and SFDC Contact that maps to SFDC. This allows us to stay in sync between our various communication tools in different orgs. 

When we pull programs, we use the fields on the Person object to help keep aligned if someone has opted out of “all emails” from Marketo

@katie_b did you get a chance to see the workaround posted by @andreammelde ?

@andreammelde Thank you!

@katie_b  I have also posted that we would like to have a standalone Opt Out page so that we can have our CSMs manage customer’s opt out. Idea is that after a certain amount of time of being opted out, we could have a rule generate a CTA for the CSM to reach out with a link for the customer to update their preferences and opt back in. If you would upvote, that would help get the idea on GS roadmap

@sai_ram I did, although that would be a last resort for us. The ultimate experience would still be different and ensuring everything stays in sync with ever changing options would be a nightmare. All systems are managed by different teams, so we’d need to set up an entirely new process just to make sure a change in one locations is reflected everywhere. A custom link going to the ‘master’ page would be much simpler and we could still push that data into SF/Gainsight as explained it just wouldn’t require data flowing both ways.

@andreammelde Thanks for sharing...voted!

@katie_b Ability to redirect opt-out to a custom page is on our roadmap. ETA not yet decided.

Just adding my vote for this. Gainsight is one of many platforms used in our company and not being able to use a centralised out-opt page is not appropriate for us — and probably many other enterprise customers

We echo the need for this as well!

This was on the roadmap three years ago - any update/ETA?

This is absolutely necessary -- we’re trying to unify branding between our multiple email systems, but having a separate preference center (with an un-customizable link) doesn’t mesh well with that goal. Being able to update language preferences and other settings would be hugely beneficial.

Could this also be something that lives in an instance-wide header/footer menu, so we could have different headers and/or footers depending on the chosen email template?

@kstim for visibility!