Different Spotlight depending on URL
Answered
Hi,
I have a multilingual website, and I would like to display a Spotlight Subscribe in different languages, depending on the base URL, like:
- mysite.com/en → Displays spotlight in english (the MailerLite action should add them to an english group).
- mysite.com/fr → Displays spotlight in french (the MailerLite action should add them to an french group).
- mysite.com/de → Displays spotlight in german (the MailerLite action should add them to an german group).
How can I achieve that?
Thanks!
Jeremy
-
Official comment
Hey Jeremy!
When you have different language options on your site, you should be able to use the same Subscribe form for each by adding additional Language options in the Subscribe form's Advanced settings.To do this, you'll navigate to Grow Publisher Portal > Subscribe > Forms and click Manage Form on the form you need to add additional Language options to. Scroll to the bottom and expand the Advanced section, then click the Add New Language Button. This will allow you to add custom messaging to your Subscribe form for supported languages.
When you've added the custom Language options, click Save Changes! Grow should detect the browser language for each user and serve them the correct messages.
-
Hi Ben,
I've already done that, but I can't change the action, hence my point : “the MailerLite action should add them to an english group" for the English subscribe spotlight.
It doesn't make sense if each user sees the popup in its native language, but then subscribes to a newsletter in another language…
0 -
I'm so sorry I missed that, Jeremy! It's early morning here. 😅
The best way to accomplish different Form Actions currently is to use multiple Subscribe forms. Depending on how your site is set up, you can go about this a few ways.
If the language the reader is browsing is included as category metadata and you have a WordPress site, you can use Category Targeting. This would mean you'd need to create a Spotlight Subscribe form in each language (making sure the non-English forms have the custom Language messaging in their Advanced settings) and then choose the appropriate language category in the Category Targeting section.
If you are not on WordPress or the language is not part of your category metadata, you can use Manual Placement Subscribe forms. You'd need to create a Manual Placement form in each language (making sure the non-English forms have the custom Langauge messaging in their Advanced settings), then embed the form's Manual Placement code in the post anywhere below the first screen view.
You could choose to use this method on WordPress and create reusable blocks/patterns to more easily place these forms in your content.
0 -
No worries for the morning fog 😉
My site is on WordPress, but I use WPML to create the multilingual structure as described in my OP :
mysite.com/en
mysite.com/fr
mysite.com/de
So it's not categories but kinda sub-folders, and I'm looking for an automated way to add the Forms.
Manually adding Forms is not an option as it is absolutely not scalable.
Sorry to ask, maybe because it's late evening here 😅, but I can't think of any use case where a multilingual form creates new subscribers without having any info about the users' language…0 -
There's not currently a way to use your multilingual structure as outlined to automatically target individual Subscribe forms. The best course of action with Grow's current capabilities would be to add language categories to the sections of your site in those languages to allow you to utilize Category Targeting. This would be the least manual method.
I have logged this as a feature request with the Grow Engineering Team for you. We could see additional capabilities added for Form Actions that would allow for unique actions depending on the reader's language.
As for detecting the language to use, Grow looks at the web browser's language settings to present the reader with their browser's default language when possible.
0 -
Thanks for the feature request.
As for detecting the language to use, Grow looks at the web browser's language settings to present the reader with their browser's default language when possible.
Ok, maybe I'm missing something, but what is the point of presenting the reader a form in, let's say French, if it subscribes him to a German newsletter, that he can't understand ?
I'm simply asking this to understand if I can do something with that feature.
0 -
You're welcome, Jeremy!
Many web browsers will translate content on a page for the user based on their language settings. For example, when I browse content or emails in German, Chrome offers to translate the content I'm viewing to English. This same experience is available in Gmail when I open an email in a language other than what appears as my preference in my settings.
Allowing for custom messaging in supported languages lets you curate the Subscribe experience for users whose browser language settings may auto-translate the default Subscribe messaging. Then, their email service could do the work of translating the emails they receive.
0 -
Oh ok. Definitely not something I would do, but thanks for the explanations.
May I ask one last question (unrelated to the topic, so feel free to close the post or remove my message) :
I created a Spotlight Subscribe to try to achieve what I wanted. But since the feature is missing, I don't need that Subscribe, and now I'm stuck with this, because I can't find any option to delete a Subscribe form. Or did I miss it ?0 -
You're not able to delete Subscribe forms at this time (but hopefully we'll have that available in a future update). For now, you can disable any Subscribe forms you do not want to appear on your site.
To disable Subscribe forms, navigate to Grow Publisher Portal > Subscribe > Forms and click the toggle switch for any forms you want to disable to the off position:
0 -
For some reason, I can't get the screenshot to appear in the above comment, but hopefully it'll upload in this one!
0 -
Thanks. I saw that I could disable forms, but I'm OCD with this kind of things…
I thought CRUD operations were the first things to implement in a UI, but maybe I'm OCD with that too ! 😅
Anyways… Thanks for your support
0
Please sign in to leave a comment.
Comments
11 comments