You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the user clicks on the bottom of the newsletter in unsubscribe from this list, it is directed to another page where the titles of each list are listed.
If there is even a list defined as public, it is what will appear in this screen regardless of whether the user is subscribed to this or another. This screen is very confusing for the user, it is unclear where he must click to unsubscribe.
The suggestion is that instead of listing any bank contacts of this screen, there is only one message "Do you want to stop receiving this information?" and the buttons "Yes" or "Cancel".
This functionality could be implemented in sendpress?
I noticed that you previously inserted the ListId in URL's, because no longer use this approach?
Is there any security risk if again we put the ListId in the URL, in order to implement this functionality?
The text was updated successfully, but these errors were encountered:
We added the option to redirect the unsubscribe link to a new page of your site. This is for emails that have an unsubscribe link in them. take a look and let me know if this would work for you.
When the user clicks on the bottom of the newsletter in unsubscribe from this list, it is directed to another page where the titles of each list are listed.
If there is even a list defined as public, it is what will appear in this screen regardless of whether the user is subscribed to this or another. This screen is very confusing for the user, it is unclear where he must click to unsubscribe.
The suggestion is that instead of listing any bank contacts of this screen, there is only one message "Do you want to stop receiving this information?" and the buttons "Yes" or "Cancel".
This functionality could be implemented in sendpress?
I noticed that you previously inserted the ListId in URL's, because no longer use this approach?
Is there any security risk if again we put the ListId in the URL, in order to implement this functionality?
The text was updated successfully, but these errors were encountered: