-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues Configuring Opt-Out/Unsubscribe #179
Comments
We are experiencing a similar issue on one of our site using Mosaico. Tokens "unsubscribe via email", "opt-out" looks weird in actual preview or final email that is sent. See - Also, the social media buttons wasn't displayed correctly, but we got that fixed by #182. |
@dinalondon I don't fully understand the description. There are two distinct aspects of the unsubscribe/opt-out:
|
@dinalondon not sure if this is the same issue or helps you. When creating a template I chose hyperlink the word 'Unsubscribe', instead of hyperlinking to a web address I input http followed by the token. When I test this it appear the word is linked to the token, therefore this looks much nicer than the token being exposed, however it results in a blank webpage and the unsubscribe token in the address bar. Not sure where i am going wrong |
The preset unsubscribe feature seems to be working well however my struggles are with adding the 'opt out' option. |
Yes, the hyperlink is exactly what I ended up doing. Was just looking for
something more flexible like what you see when you go to Mailings/Headers,
Footers and Automated Messages.
*Rabbi Dina *London
Vice President General Manager
• • •
*Jvillage*Network
212 Battery Street
Burlington, VT 05401
802-846-3517 direct
Sales Offices:
Chicago/New York
…On Tue, Dec 5, 2017 at 3:40 AM, EmilySolaris ***@***.***> wrote:
@dinalondon <https://github.com/dinalondon> not sure if this is the same
issue or helps you.
When creating a temple I chose hyperlink the word 'Unsubscribe', instead
of hyperlinking to a web address I input http followed by the token. When I
test this it appear the word is linked to the token, therefore this looks
much nicer than the token being exposed, however it results in a blank
webpage and the unsubscribe token in the address bar. Not sure where i am
going wrong
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#179 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHk5Blxf4H2oprAWgn081QsbTs69-mJjks5s9QFxgaJpZM4Ov_lw>
.
|
Can we consider this issue closed? Hyperlinking the token is what needs to happen and seems to be common practice. Maybe include that in any documentation related to tokens/tokens that are links. |
Yes, consider it closed, thanks.
Dina R. London
Jvillage Network
A Division of Shulware
[email protected]
802-846-3517
…________________________________
From: themak1985 <[email protected]>
Sent: Wednesday, January 23, 2019 5:26 PM
To: veda-consulting/uk.co.vedaconsulting.mosaico
Cc: Dina London; Mention
Subject: Re: [veda-consulting/uk.co.vedaconsulting.mosaico] Issues Configuring Opt-Out/Unsubscribe (#179)
Can we consider this issue closed? Hyperlinking the token is what needs to happen and seems to be common practice. Maybe include that in any documentation related to tokens/tokens that are links.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#179 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AHk5BtJ23MawmezMHayY9kMr1FOvYsYbks5vGO-egaJpZM4Ov_lw>.
|
I've been struggling with the configuration of opt-out/unsubscribe. I see the options listed in the advanced settings, but they don't automatically show up in the template nor can I find anywhere to configure the tokens or automated messages. I can manually add the tokens to the template, but they don't look very pretty nor are they intuitive for the person receiving the mailing.
Does anyone have any insight into this issue? Am I missing something?
Thanks so much!
Dina
The text was updated successfully, but these errors were encountered: