cooper collier 6/9/2023 12:03:39 PM
good day Jonathan.
My two friends above both have valid approaches to your issue. I have a couple more possible ways for you to make this happen and a stupid comment.
To start, there is absolutely no way to make an unsubscribe link that will include the persons record, so all they need to do is click the link and unsubscribe. The person will need to enter there email address to unsubscribe.
OPTION 1 (super easy)
Make 2 tables...
Table 1 is subscriptions. You can capture whatever information you need, but make sure the email address is there and that it is unique.
Table 2 is unsubscribed. This one is simply email addresses.
Make a many many join between the tables and do a summary lookup, and count records matched on email address. If there is a match then you do not use that email address anymore.
Now you display table 1 for subscribing, and email a link to table 2 to unsubscribe. People just need to enter their email address.
Problem! This will NOT meet Euro Gddpr (whatever) rules.... You can set a daily action to delete records above. that may work.
You have one table that has the subscriber info in it.
Next you make a search view, this view can be set to find email addresses. or email address and last name. Then you display this view on an HTML page, either using a JS embed or a html embed.
To unsubscribe the user goes to this pages, enters email and search, then delete record. Tada!
This has the issue than anyone can find out if someone else is subscribed to your email by simply searching on the unsubscribe page.
NOW for the unhappy comment. I really really hate it when someone asks, "how do I do...." and some idiot answers, "you should not..." or "get Linux" But in this case, I think it's important to warn you about the email issues before you get too deep.
Are you using team desk to actually email the newsletter? If so, you really should not. You are going to have huge deliverability issues. The mail system in Teamdesk is designed for sending to small groups of members. Even then, we have to constantly fight with reports and other messages being marked as spam. If you do wish to send from Teamdesk, you should go through a service like Mailgun.
Plus, if you're in Europe, you need to consider the GDppr rules. Newsletter services have established processes to comply with GDppr rules and any other rules. If you use Teamdesk, you need to program to conform to all the rules yourself. I refuse to do it for my clients. It's just too easy to miss something.
But if you do use Teamdesk to manage your subscription base you now have 5 ways to do it..
Wait.... how about 6... you can get the external user's package and work with it.