Back to help
19

Languages, themes, and layout

The interface selects a supported language from the browser and falls back to English when the language is not available. Users can switch language manually and choose light, dark, or gray themes. The layout is designed for desktop and mobile use, with controls, tables, forms, help content, and long translations arranged to stay readable without unexpected horizontal scrolling.

Languages, themes and mobile use

The language is selected in the site header. 32 languages supported: English, Russian, Simplified Chinese, Hindi, Spanish, French, Arabic, Bengali, Portuguese, Urdu, Indonesian, German, Japanese, Marathi, Vietnamese, Telugu, Hausa, Turkish, Punjabi, Swahili, Filipino, Tamil, Persian, Korean, Amharic, Thai, Javanese, Italian, Gujarati, Kannada, Yoruba and Polish.

Arabic, Urdu and Persian use the direction from right to left. URLs, technical identifiers, UTM keys, error codes and JSON fields save the technical record. Changing the interface language does not change the link data and does not set the browser language of future visitors for routing.

In the header you can choose a light, dark or gray theme. The theme affects the interface, and the colors of the exported QR are set by its own settings. Preferences are saved by the browser; In a private window or on another device, the selection may differ.

On a narrow screen, shapes are rearranged. Wide tables can scroll within their own block. For large QR layouts and long reports, use an appropriate scale, but still be able to read captions and click buttons. The keyboard allows you to navigate between fields; the visible focus frame shows the current element.

Publication checklist

• The link has been created in the desired account; the domain and ID correspond to the location.

• The target URL opens and contains the correct UTMs.

• Dates are recalculated in UTC, the limit corresponds to the plan, and the completion of the campaign is provided for.

• For each significant language, device, and time, the rule selection is tested; There is a working default option.

• The comments in the diagnostic report were studied; saved JSON if you need a startup log.

• In the new session, the real password chain, OTP, referrer, warnings and link click are checked.

• The exported QR and proof print are scanned; The link/vCard mode was chosen deliberately.

• Test conversion and webhook are checked where they are needed; messages reached through the selected channels.

• Colleagues were given the necessary rights, the recipient's report was checked without the owner logging in.

• Once published, actual link clicks and the status of the destination URL are tracked; old printed links are not removed without assessing the consequences.

To consistently master these actions, go to Practical course.

Complete user guide ยท Practical course

How to apply this section

Each topic explains a feature, the user decision behind it, and how to use it without making the link harder to manage. Read the checklist before changing a link that is already shared.

Before you publish or update

  • Start from the visitor experience: who opens the link, from where, on which device, and what should happen next.
  • Check that the destination is correct, opens quickly, and shows the expected page for the intended audience.
  • Choose only the controls that match the goal, such as expiration, password, referrer, QR design, UTM, routing, or analytics sharing.
  • Save a short note for important changes so future review, rollback, or teamwork stays clear.
  • Open the short link in a private browser session and, when relevant, test mobile, desktop, QR scan, and protected access paths.
  • Review analytics after sharing to confirm real visitors, source quality, device mix, and campaign performance.

Practical example

Example: create a test link for an internal page, add a clear slug, set a short expiration, enable preview if the destination is sensitive, scan the QR code from a phone, then check whether the visit appears in the link statistics.

Next step

After this topic is clear, combine it with one adjacent feature. For example, pair UTM with campaigns, QR with print layouts, targeting with fallback, or webhooks with conversion tracking.