Contact Permissions - share your setup

Roll up, roll up - who's using contact permissions and would you care to share your setup?

We are migrating to Contact Permissions and in looking around, it seems there are two approaches: a top-level channel approach and then a more granular approach.

Some questions for you:

  • Are you using contact permissions for top-level preferences? For example, email/phone/mail?
    • In this case, how to you manage a single list unsubscribe?
    • What about a global unsubscribe?
  • Or/and are you using them for granular preferences? For example, your regular enewsletter, donor comms, that kind of thing?
    • In this case, how to you manage a single list unsubscribe?
    • What about a global unsubscribe?
  • Are you doing it some other way?

The cleanest way I have scoped out would be a mix of contact permissions alongside contact point purposes.

Contact Permissions: mail, email, phone (and anything else)
Contact Point Purpose: specific opt-ins for example monthly enewsletter, donor comms etc

FWIW we're on TNEW and use Wordfly. So TNEW's Contact Permissions plug-in would ask the top-level permission during checkout, and Wordfly would be linked with contact point purposes to allow our audience to select their preferences.

Please share your setup! I'm keen to hear how others are doing it. Especially you folk in the EU who have gone through a lot of rethinking here because of GDPR.

Cheers,

dgh

Parents Reply
  • Hi Jess and Karen, since you both mentioned it, the "wrong org" thing only appears when you're composing a reply, not when you actually save your reply; hopefully you've seen that when you saved, your replies are showing as the correct org now. You'll see it's from the original poster's org on the thread; when we added this functionality, we had to choose between merge code and the OP's org showing while composing replies and we felt the merge code looked more broken. Happy to hear other opinions though!

    Best,
    Todd Lantry
    Tessitura Network

Children