Hey fellow e-nerds,
Just wanting to float that evergreen topic of Permissions as no matter how many times it's brought up and how many hours it's talked about I always seem to be left wringing my hands and pulling sobbing into my keyboard.
So I'm looking at Contact Permissions (with Interests) and the Contact Permissions Plug-In. More background listening here https://www.tessituranetwork.com/en/Items/Videos/Webinars/2017/GDPR NB/ I'm leaving aside Contact Point Purposes for mental health reasons.
Business Need
We have a need to take separate customer Opt-Ins for venues we perform at and presenters that perform at our venues, separately to our shows. We need those options to be dynamic depending on what is in the cart. We're also interested in separating our Philanthropy and Marketing Opt-Ins with philanthropic comms opt-in being offered when a donation is made.
The Contact Permissions Plug in does that with bells on which seems like a win.
Other preferences
We have other parts of the business like our Dance Academy, Youth Workshops and Dance Classes which we can manage as Interests well enough.
Pain
My difficulty is what does a WordFly Optout mean in this situation? A global opt out is a requirement so when someone opts out of everything where does this happen? The party line for both Tessitura and WordFly is "Only use Permissions as a Global Setting" but that would seem to invalidate the whole Permissions Plug-In product that was developed due to a very real industry need. Letting people opt-in and out of business segments is a great idea but would seem to need another hierarchical level.
Has anyone managed to tease out that issue?
Thanks in advance.H
Hi Jean,
The two list criteria elements should be used together otherwise you will end up with a list of everyone who has Yes to any contact permission (or vice versa with No), as you are seeing on your criteria.
For example if you wanted to just pull a list of constituents who have the Email contact permission set to Yes, your list criteria would be:
- Contact Permission Type = IN = select your Email contact permission type- Contact Permission Answer = IN = Yes
This will only pull constituents who have the Email contact permission set to Yes. If that's not what you're seeing I'd recommend putting in a support ticket with some screenshots and one of my support colleagues will be able to help.
Side note: for any email comms, I always recommend including the Primary Eaddress Flag = IN = Yes criteria so you only get constituents who have a primary email address on their record.
Cheers,
dgh
Hey Heath,
Heath Wilder said:But by putting a branching number of options at the Permission Level (and that is what the Plug In does) you solve one problem (opt-ins dynamically by product) but create another (no global permission).
Can you give me a use case for this? In my mind the presenter-type contact permissions are for internal use - eg, as a criteria to pull a list to send the data to the presenter or a flag for Importal to pick up on. I wouldn't expect those permissions to supersede your own global contact permission/s, particularly because when you're using the contact permissions plug-in the customer is going to be prompted to opt-in to the presenter contact permission. You are explicitly asking their consent for that permission type. Even if they have not opted in to your global contact permission, they could still opt-in to the presenter and you could happily share their data knowing they have consented to that.
I think that I know what I need to do pragmatically to make it work.
My problem is that it is presented in one way (Permissions should be global opt-ins) but there are quite a few exceptions. And the examples (philanthropy and marketing) compound that. Knowing that's the case though I've got a call in with support to follow up on some items.
Thanks for taking the time to go through it.
Hi Jean, we have three Marketing-specific contact perm types: Email, Direct Mail, and Phone. Then we use Interests/Preferences to determine which email they receive. The preferences they see when they subscribe are: Weekly Newsletter, Promo Emails, and Event Updates. In our lists, we use the Contact Perm Type = Y and, depending on which email type it is, it also has Constituent Interest is = Weekly Newsletter + Consituent Interest Selected = Y.
So we are pulling the Weekly Newsletter list based on the criteria that the permission type is email marketing and the interest selected is weekly newsletter. (There's a screenshot above of our list criteria for reference.)