While it’s important for users to be able to opt out of e-mail campaigns, currently as admins for PX there isn’t an option to control or manage the opt-out options. Our company sends marketing, operational, and non operational e-mails to our customers. While we understand some customers may want to opt out of certain communication types, if we’re sending out operational e-mails, it would be great for admins to have some control over these groupings so that if a user opts out of marketing e-mails for example, they can still receive operational e-mails.
Gainsight PX - Control Opt-Out Options for E-mails
Hi
The process that you are asking is actually an enhancement request, you can post this as an idea and our product team will look into it.
But there is a workaround that you may use, the details are in this community post, ideally the post is about KC Bot, but it has reference to email engagement opt out as well. Hope this helps.
Hi
If a user unsubscribe they wouldn’t receive any email from Gainsight, where you would need to update the email unsubscribe option in user profile if you want the user to receive emails again. Adding a community post below for your reference for re-subscribing the users.
Yes, all emails will have unsubscribe option by default, but by controlling what content user prefers to receive as per their preferences we should be able to reduce the unsubscribe clicks.
Hope this helps.
Thanks!
If a user has the same Aptrinsic ID across all products, we need to collect product-level preferences and manage them accordingly.
Attached is an example of an engagement where we collected roles and goals from our customers. Users could select multiple options (such as email preferences in our use case), and these selections were stored in attributes.
You can later use these attributes in email audience logic to ensure that only users who opted for specific email preferences receive those communications.
Thank you!
If a user has the same Aptrinsic ID across all products, we need to collect product-level preferences and manage them accordingly.
To ensure the same user ID is used across all products, the identifier call setup should trigger the same user ID whenever a user logs into multiple products. This does not require the same tag, but rather the same user ID in the identifier call when a user accesses your applications.
For product-level email preferences, companies need to create product-specific preferences. If preferences are to be managed at the company level, a single set of preferences can be maintained.
Reply
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.