What I would like to achieve is an email unsubscribe process that is secure, performant and on an external page with the ability to update the internal system table (dataview) _Unsubscribe.
How I imagined this to work is like this:
- Create an aMPScriptAMPScript variable inside a newsletter that stores the values that are needed for the _Unsubscribe dataview separated by a special character
- Encrypt the variable with AES
- Create an Unsubscribe Link in the e-mail with a typical a href to our external page and and concat with encrypted variable on it as a parameter value. First three points shown here?
- Decrypt the url-parameter with the backend of our external shopengine and store it in different variables (RegEx on special sign)
- Use the client-id and secret from a package created in the marketing cloud
- Retrieve the access token
- Do the last two steps with Java Axis 1.4 or something else
- Create a SOAP-API Call and insert the values into it
- Send this data to the right endpoint (which is?) when the user clicks the unsubscribe button in the website
Here my Questions:
- Is this the right way to do it?
- Is there a simpler way when you are using an external page and not cloudpages?
- Is the point 2 secure, what do i have to make sure that point 2 is secure?
- Are there any documents you know that can help me with this task?
Kind regards for reading