Hi all,
Is anyone making use of the new Contact Permissions in v14? If so, have you swapped from using the Purposes within Electronic Addresses?
I'm looking to start using the Purposes for email addresses (So we can identify those who are signing up to our e-newsletters. Lots of these people have multiple email addresses, but should only receive the e-newsletter to one of them.), however I don't really want to change the process again when we go to v14. From what I've seen/read the contact restrictions on the General tab will be disappearing in v14, but the the Purposes will remain for the Postal Addresses, Phones and Electronic Addresses within the Contact Details tab? I couldn't see anywhere in the new Contact Permissions for them to be tied to specific email addresses, if the constituent has more than one?
Does anyone know if I'm right in thinking this?
Thanks,Alison
Hi Alison,
We are looking at a similar scenario as we transition from Mail2 to WordFly. Did you get any further with your analysis?
I think you are correct in that Contact Permissions do not relate to a specific email. Hence I think you need both Contact Permissions and Purposes. The Purposes flagging which email(s) constituents have subscribed to the eNews and the Permissions flagging the authority to send emails in general.
WordFly seems to support both in Tessitura v14.
Thanks
Ian
Hi Ian,
In the end I set it up as the following as we were still on v12.5:
-A Purpose within Electronic Addresses, that is used purely to identify which email address we can send to (lots of constituents have multiple email addresses, so we needed to distinguish the one to use).
-An Interest called WordFly to signify that the person had requested to receive email from us.
We had a script written that unchecks the Interest when an email bounces or someone unsubscribes via WordFly (we just uncheck it manually, if they unsubscribe over the phone or via email) and makes the email address inactive.
It seems to work well so far for us. We’re actually still on v12.5 at the moment, but from the testing I’ve done in our v15 TEST site, everything still seems to work as before, as Contact Permissions are not compulsory to use. I haven't tried setting up any new Contact Permissions though, so it's probably worth you testing it still.
Best,Alison
Yes, I'll essentially do the same, except use Contact Permissions instead of using Interests. I'm not sure if WordFly handles Contact Permissions so I may need to write some code.
Cheers
Here is some light reading on Tess Contact Permission / WF Preference setup
support.wordfly.com/.../204768684-How-to-setup-Tessitura-preferences
Hi Heath,
Thanks for the link. Do you know if the LP_WF_PREFERENCE_UPDATE_CUSTOMER stored procedure contains code for handling Contact Permissions? Just trying to plan the rollout of WordFly.
Hi Ian. Your Wordfly Account/Preferences page has a drop down for each Interest/Purpose/Permission/Attribute etc. LP_WF_PREFERENCE_UPDATE_CUSTOMER will update the relevant table (eg: tx_contact_point_purpose) depending on what type you select.