Wordfly Preferences

Hi Rya, we set ours up with interests, and I would not recommend it. In retrospect I think we should have used Purposes on the email address. (and attach the unsubscribe to the email if possible) With merging, households, people with multiple email address putting all that on the account isn't that easy to manage. If someone unsubscribes on an old email, then makes a new account with a new one, when I go to merge those old preferences and unsubscribe come along. A bit of substandard data management.

Here's what the preferences look like to Patrons: http://email.wordfly.com/unsub/preferences.aspx?sid=Mjk0Xzc1NDVfODE1MjRfNzAzNQ In Tessitura they're just the titles.

Ann

Thank you, Ann! That is very helpful!

I want to make sure that I understand...

You would choose to store to the preferences here?

Yep exactly. That way it's all related to the email address, which is what Wordfly uses as the unique account.

We're moving WordFly Preferences to v15 Contact Permissions and are using the Allow Marketing check box on the email address for Unsubscribes. I'm still working through the set-up as it doesn't seem to be working quite right yet though.

Hello All, 

We were looking into starting to use interests + WordFly for to help target our lists, provide a better welcome & unsubscribe experience etc. however, reading this thread I am thinking perhaps we need to use contact permissions instead. I get how this works for a WordFly unsubscribe. However (please forgive me for working through my thoughts in this thread), I have some things I need to work out in terms of making this work for what we need, if this will even be a better option for us.

Part of this larger plan is that we wanted to begin on boarding/welcome emails and encourage people to set their preference on their tessitura account - how would we direct people to preferences rather than interests (can we even do that?). Now assuming that we could get persons to set their preferences on their tessitura account pages, this would be fairly simple for NEW persons -- then we have the larger question of what do we do a.) with our insanely large database of current people, can we default the preferences for current people in the database to ALL the preferences we set up, then if/as they unsubscribe to some it will update within their account and then b.) what happen to new people who don't set preferences, can we run a procedure to see accounts with empty preferences then default to all? Related question is what kind of reporting (is there any) that could give us some data on preferences that people are setting/not setting etc. etc.

Thoughts ("you are crazy Michaela" is an acceptable thought)?

Many thanks, 

Michaela

Good morning - 

You're never crazy, Michaela--just dreaming big.

I'm commenting to throw an essential element in to the mix, one that otherwise has me regulated to the sidelines here: TNEW only allows for Interests at the moment, both in v6 and v7.

I know the TNEW dev team is sensitive to this, but I haven't heard any change is actively slotted onto the Road Map just yet. (Perhaps Chris Szalaj or Nara could chime in?) 

Otherwise, I think you're asking the right questions with the right ideas--we had iterations of the backend updates running once upon a time to cover this. 

And just to throw something else big in the mix, there's also no resubscribe option via TNEW that's public facing, at least not one that I think does the job. Interests, at least via TNEW account management, just aren't dynamic enough for us to rely on them as literal permissions. That lives elsewhere, which means there's no patron-facing version. I've chatted with WordFly about how their account options might be an alternative, but it's not quite aligned enough either.

Jamie O'Brien
Associate Director of Digital Services, The New 42nd Street

PS. Acknowledgement that I'm with a US organization, and people responsible for stricter data protection standards will only find this the very beginnings of the challenges. But there is the EU-available add-in options for TNEW that help. https://www.tessituranetwork.com/en/Services/Software-and-Web-Consulting/Components#contact-permissions and https://www.tessituranetwork.com/en/Files/Docs/TNEW/Contact_Permissions_TNEW

Hi Jamie O'Brien and Michaela Donnelly - 

Just confirming that while it is something that we have our eyes on, its not on the 2019 Roadmap. You'll likely see improvements here once we finish converting TNEW over to REST Services completely. 

Thanks

Chris

CC Nara Zitner