Feature-Requests

Share your feedback...

Add hreflang parser for URLs in multilingual emails
If you create a multilingual email with services/articles and link to their website pages you usually need to replace each link in different languages manually which is the most time consuming part of editing multilingual emails. Links added to the xlsx. files is great, it saves us a lot of time. But I have another idea how to make it simpler for cases when you use Google translate or translate everything manually: – Many websites have hreflang meta tags pointing to all versions of the same page. – You can use that to access other versions of the page faster. – How it can work in the editor: You just parse the hreflang links on each page and if you notice that some of them exist you can show them in a dropdown as "suggested links": 1) For example, I created an email in EN with a link company.com/en/page 2) Then I translated it to other languages with Google translate 3) If I go to DE version of the email and start editing links, I choose this link/button 4) I click the URL field of the link/button and see some suggested links: company.com/de/page , company.com/fr/page , company.com/es/page etc. To go further you can suggest only links based on the current locale. For example, if I opened the DE version of the email I will see only page url from hreflang = "de" but it will make everything more complicated. there can be different versions of "de": de-de, de-at, de-be etc. So just suggesting all links related to this page based on all hreflang tags of the initial page will make the editing experience much faster.
0
Translations: Allow adding locales (combinations of language-country)
Now it is possible to only choose languages. But if you work in a few countries, very often you have different content in different places. For example, links: Even if your email content is the same in English in Germany and English in the UK you might have different landing pages. How we handle it now: – If we have an email for multiple regions we can create a single file for different languages (let's say EN, DE, FR, IT etc.) – But if we need a few different English emails (EN for Germany, EN-DE, EN-FR, EN-IT and maybe EN for the United Kingdom) then we have to create separate emails for all English versions. In the end we get one multilingual file (EN, DE, FR, IT) and five additional files just for English. The perfect way: – If you allow setting regions for each language we will be able to have a single file for any emails: EN-DE, EN-FR, EN-DE, EN-IT, EN-GB, DE, FR, IT – But it doesn't mean that you have to always choose both (the language and the country) You can set just the language if you don't need the country. So the approach can be similar to Google's approach to hreflang tags: You can set either just language or both language and region. And if you selected, for example. FR-BE, FR-CH and FR it means that you have three versions of French email: French for Belgium, French for Switzerland and French for any other country. How it can work in the language choosing interface: – There are always two fields for each item: Language and Country – When you selected a language, country by default is Global (meaning just "en", for example) – You can select each combination only once: If English – Global is already selected and you add one more English then you are not able to choose Global anymore. Only with some additional country.
1
Single email/template sharing parameters
Right now, people can access any emails and templates based on their role. It will give users more control if you allow set sharing parameters for each individual file (email or template). For example, I would like to allow only proofreading for some emails. It could work similarly to Google Drive: – If you created some template/email then you are the owner – By default it is shared with everyone based on some global rule. For example, allow doing people everything based on their role (like now – admins and editors are able to edit, proofreaders and designers have their own rights etc.). – But I as owner can change it – share with specific people by allowing/disallowing them some things – And if I, for example, allowed only translating/proofreading/designing to some specific person they can still duplicate the file. If they duplicated it then they are the owner of this new file and can do with it whatever they want. Use case: – There is an email marketer who builds all emails and templates. – Other people in the team have proofreader roles. Because of that they can only change texts, links etc. but can't move or edit elements. – Very often these teammates have to make small changes to the design, such as swapping two blocks. And they need to ask the email marketer to do so. – But if we allow them to copy files to become owners they will be able to do anything they need themselves. This way, the original template will not be broken, team members can make any small changes to their email without having to request them and wasting their time and the email marketer's time.
1