Hello! I'm curious how everyone is handling bounces and unsubscribes, from a contact permission perspective. Do you have that information synced between Wordfly/Prospect 2 and Tessitura?
My hesitation is that contact permissions apply to the constituent level. But many constituents have multiple email addresses. So it may be that only one email is bouncing, and/or they meant to opt out from a particular email address rather than their entire record.
However, because we don't have that information written back to their record from Wordfly, sometimes we are promoting emails to an account that won't actually receive it.
I'd love thoughts on this! I had asked around at TLCC this year and it didn't seem anyone had much of a solution, but perhaps there's something that's missing.
We use P2 and are not syncing P2 to permissions mostly for that reason that you address: many email addresses to 1 constituent record. However, with Contact purposes being more of a 1 to 1 relationship, we would probably feel safer syncing our bounces/unsubscribes via purposes.
For unsubscribes, it's interesting because we might unsubscribe a patron via an automation, simply because they haven't been engaging with us over a set period of time. This was an unsubscribe that we did, and not a patron marking as an unsubscribe. We do this for reasons around deliverability and we don't keep sending to contacts that are not engaging. However, I might not want this kind of automation unsubscribe to write back to Tessitura.
Thank you, Michael! So you are using Contact Point Purposes rather than Permissions? It seems Tessitura wants us to move toward the latter, which is constituent-based rather than email-specific, which is my hesitation! We currently are using Permissions.
It might make a difference if you are on P2 or Wordfly. What are you currently using?
We're on Wordfly, but I'm not sure if that matters in this case. I know that it CAN write back to Tessitura. I'm just not sure if it should.
Thanks Jean. I am thinking about the integration points and how each platform, Wordfly/P2 integrate back to Tess. Also depending on how each organization stores and pulls data, that might dictate if permissions are more important than purposes, or vice versa.
While we will be using permissions as an organization because we have to for V16, we will probably skip the P2 integration of contact permissions. I do think for us as P2 users, the strength of purposes will be much more useful for us.