XM Directory Lite users: Please upvote EV-4918 to restore mailing list unsubscribe support

Question

Hello Community,If you use XM Directory Lite and rely on the XM Directory Task to unsubscribe contacts from a specific mailing list, please consider supporting EV-4918.The deprecated XM Directory Task can unsubscribe a contact from a mailing list without opting them out of the entire directory. However, on the XM Directory Task support page, Qualtrics recommends migrating to the Update XM Directory Contacts Task, which currently only supports directory-level opt-outs and does not provide equivalent mailing list-level functionality in XM Directory Lite.Qualtrics Support confirmed:Our engineering team has investigated this issue more closely and unfortunately concluded that the new task is currently not designed in a way that the opt-out option works with the XM Directory Lite. This is because the task is designed only to remove a contact from the entire directory rather than a mailing list and in the case of the Lite Directory, a directory does not exist. Our internal team has carefully considered this issue but unfortunately came to the conclusion that this currently cannot be fixed as a bug... Instead, to resolve this issue, you will need to submit a feature request through the Qualtrics Community.The legacy XM Directory Task remains available today, but there is currently no equivalent migration path for workflows that depend on mailing list-level unsubscribes.If this affects your workflows, please add your support to EV-4918.De Duped Ideas Title: “Ability to opt out a contact from a single mailing list using the Update XM Directory Contract task, not the entire directory”https://community.qualtrics.com/p/evolveThank you!

vgayraud · Accepted Answer

Hi ​@Tom_1842Unless I’m mistaken, I think theUpdate Contact In Mailing Listwill allow you to achieve that in a web service task. Probably a bit more setup depending on your overall goal, but might be a viable workaround.The doc says it’s only available to XM Directory users, but I just tested it on a contact in a Directory Lite list and it worked just fine.Best,P.S. Still gonna upvote your idea, it’s much simpler to have this baked in native tasks. :)

Tom_1842 · Answer

​@vgayraudThanks for pointing me in the right direction! I tested it out and it does indeed work for my use case.Replacing the deprecated XM Directory Task with a combination of Update XM Directory Contacts and a Web Service task does the trick. I configured the Update XM Directory Contacts task first to expose the Directory ID, Mailing List ID, and Contact ID for piping into the Web Service task. Then I followed the API documentation and submitted a request with just{"unsubscribed": true} in the body.If it helps anyone else, here's an example endpoint with the piping in place:https://yul1.qualtrics.com/API/v3/directories/~{ch://OCAC_xzOeHe3n3KKqkra/directoryId}/mailinglists/~{ch://OCAC_xzOeHe3n3KKqkra/mailingListId}/contacts/~{ch://OCAC_xzOeHe3n3KKqkra/contactId}That said, I also hope EV-4918 gains some traction. This workaround solves the problem, but it requires replacing a built-in workflow task with a custom API call. Having mailing list unsubscribe support available directly in the new task would make migration much simpler for organizations currently relying on the legacy XM Directory Task.Really appreciate the workaround and your support for a native solution!

Sign up

Login to the Community