How to share news per partner language?

If you have partners in different countries it could be better to adapt your communication based on their language.

It's possible to share news in Kiflo based on the partner's preferred communication language.

How does it work?

For the same news, you can add many translations, in as many languages as you want.

Then for each partner, you can specify the preferred communication language.

From their partner portal, partners will see news defined in their preferred communication language.

Real-life example

  • Add a news to promote a new article on your blob
  • Add a Spanish translation in addition to the default English version and make the CTA points to the Spanish version of your blob
  • Publish the news
  • Spanish partners will see the news in Spanish and will open the Spanish version of your blog
  • English partners will see the same news in English and will open the English version of your blog

What if the preferred communication language is not set on the partner?

In that case, the partner will see the default translation for the news. The default translation is the first translation available.

What if there is no translation for one piece of news in the partner's preferred communication language?

If the preferred communication language for a partner is set to Spanish but there is no translation in Spanish for the news, then the default version will be displayed.

Add translation

Open the news you'd like to edit, then:

  • Click on the Add translation button
  • Select the language
  • Click Add
  • That's it!

The following fields can be translated:

  • Layout
  • Category
  • Title
  • Description
  • Image
  • CTA-related fields

Delete translation

Open the news you'd like to edit, then:
  • Click on the translation you'd like to delete
  • Click the Delete button
  • Then confirm

This is not possible to delete the default version but you can assign another language to the default version.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.