Solved! Go to Solution.
Views
Replies
Total Likes
@david--garciaWe have talked about this solution as well and I wanted to raise something that made us look a bit closer at the preferences use case.
In a lot of jurisdictions, when someone follows an unsubscribe link and unsubscribes (either automatically or by entering an email or clicking "Unsubscribe") you have to enact that change immediately and not provide some additional steps in order to unsubscribe (e.g. login, confirmation email, etc.)
If you require validation before making the change, you run the risk of the email not being received and the person not confirming it and you would fall afoul of the regulations in that country. It's worth checking the regulations in your client's area.
What I would do, is the reverse. Make the change in the database immediately, and send an email confirming like Google does - "If this was not you, then click this link to undo change" - that way you fulfil the regulatory obligations, but also give the user a chance to reverse the change if it was not done by the original recipient (or was done by accident)
Just my 2c
Cheers
Darren
@david--garciaWe have talked about this solution as well and I wanted to raise something that made us look a bit closer at the preferences use case.
In a lot of jurisdictions, when someone follows an unsubscribe link and unsubscribes (either automatically or by entering an email or clicking "Unsubscribe") you have to enact that change immediately and not provide some additional steps in order to unsubscribe (e.g. login, confirmation email, etc.)
If you require validation before making the change, you run the risk of the email not being received and the person not confirming it and you would fall afoul of the regulations in that country. It's worth checking the regulations in your client's area.
What I would do, is the reverse. Make the change in the database immediately, and send an email confirming like Google does - "If this was not you, then click this link to undo change" - that way you fulfil the regulatory obligations, but also give the user a chance to reverse the change if it was not done by the original recipient (or was done by accident)
Just my 2c
Cheers
Darren
Nice point to consider @Darren_Bowers I will bring this up to my client, did you develop the solution at the end? have you thought about the processes to revert changes? custom schema? maybe a webapp sends command to workflow to fetch the user's before changes from temp schema and revert? I am looking for ideas.
Views
Replies
Total Likes
@david--garciaWe never implemented a solution in Campaign so I cant help you there sorry. I was designing a more enterprise-wide source-system agnostic design where the profile data is made available centrally to a number of different campaign management applications. This was just one of the use cases we put forward for consideration.
Cheers
Darren