Skip to content
Open the console

Manage strings ​

The Strings page in the console is where the users' words are written: the share messages and link cards, and any text a reward, token, section, level or push points at. A change made here is live within a minute, in English, Spanish and Russian, with no app update.

Before you start

Owners and Admins add, write, translate and switch strings on this page. Any operator can use a string in a field by typing @. To understand which words live here and how they reach users, read Strings and languages first.

Find your way around ​

Each row is one piece of text. It shows the string's ID (like STR-12), its status (Active or Passive), its key (its name in the system), its type (Sharing or Manual), its text, which languages it has (EN ES RU, faint where one is missing), and when it last changed.

The cards above the table count the whole page:

CardCounts
StringsEvery string, and how many are switched off
SetActive strings that have a text
Not setActive strings with no text yet — users see the app's built-in words
ChangedAdded or edited in the last 30 days
Need translatingActive strings with a text that is missing Spanish or Russian

The filters narrow the table: Status (Active / Passive), Type (Sharing / Manual), Text (Set / Not set), Translation (Translated / Missing a language), and a search over ID, key and text.

The two types on this page ​

The Strings page holds two of the three kinds of words. Built-in words, the app's own buttons and labels, aren't here: they change with an app version.

  • Sharing strings are the sharing words: a fixed list with the subject and message the app proposes when a user shares a token, a reward, an event, a venue or an artist, and the card a pasted link shows in WhatsApp or iMessage. You rewrite, translate and switch these; the list itself is fixed. Each one comes with a Where it shows note from the developers, saying where the app uses it, and an Example of a good text. You can read both, but not change them. The full list with its limits is in Rules and limits.
  • Manual strings hold content words: text you add to use in a reward, a token, a section, a level or a push. A manual string does nothing by itself; it reaches users once a field uses it (Use a string in a reward, token, section, level or push).

Add a string ​

  1. Click Add string.
  2. Give it a key: lowercase words joined by dots, like reward.vip.title. The key is how everyone finds the string later, so pick one that says what the text is and where it goes.
  3. Write the Text — what users will see — or leave it empty to save the string as Not set.
  4. Optionally, open Translations and write the Spanish and Russian. They open once the English text is in.
  5. Click Create.

The key can't be changed after saving

Two strings can't share a key either. If you need a different name, add a new string and point the fields at it.

Write a text ​

  1. Open the string and click Edit.
  2. Under Text, write the words. Up to 2,000 characters for a manual string; a sharing string has its own limit, shown under the box.
  3. Where the app should fill something in, insert a tag with the buttons beside the box — {name} becomes the name of what is shared. A required tag can't be left out; a manual string needs none.
  4. Check Preview, which shows the text with its tags filled in.
  5. Click Save changes.

The form checks as you type and marks what to fix: a stray brace, a tag the string doesn't have, a required tag missing, a text over the limit. Length counts the text as written, tags included, an emoji once.

Use example

A sharing string shows its Example above the box. Use example copies it into the box, where you can change it — a quick way to see where {name} goes.

Once a text is set it can be rewritten but not emptied. To take it out of use, switch the string off.

Translate a string ​

  1. Open the string, click Edit and go to Translations. Spanish and Russian are listed; a search box and Missing only find the one you want.
  2. Open a language. The English text is shown above the box as what to translate.
  3. Write the translation under the same rules as the English — the same tags, the same limit.
  4. Click Save changes.

A language left empty shows the English text to those users, so translations can be filled in at any pace. The Need translating card and the Missing a language filter keep the list of what's left.

English first

A translation can be written only once the string has its English text.

Switch a string off ​

  1. Open the string.
  2. Click Deactivate.

Users see the app's built-in words again in that spot. The text and the translations are kept, and Activate puts them back — a seasonal message can come back next season. There is no delete.

A string in use can't be switched off

If a reward, token, section, level or push points at the string, the console refuses and tells you where it is used. Take it out of those fields first. The same applies to adding a tag to a string in use.

Use a string in a reward, token, section, level or push ​

Every field whose words reach a user takes either plain text, as it always has, or a string.

FieldWhere users see the words
A token's nameThe Tokens tab, the Notifications list, the card of a shared token's link
A reward's name and descriptionThe Rewards tab, the reward page, My Rewards, the card of a shared reward's link
A section's title and subtitleThe Rewards tab, and the section's "see all"
A level's nameThe level card
A level's push notificationThe push a user gets on reaching the level
A push's title and messageThe push, a test push, and the Notifications list when the push is listed there
  1. Open the record — the reward, say — and go to the field.
  2. Type @. A list opens with the strings that can be used there, narrowing as you type.
  3. Pick one. The field now shows the string's words, highlighted, in place of the key. Point at them to see the whole text, the key, the string's ID and which languages are translated, with a link to open the string.
  4. Save the record.

Only a manual string that is Active, has a text and has no tags can be used — a tag would reach users as braces, since nothing in a reward fills it in. The list shows the others greyed out with the reason beside them (Passive, Not set, Has a tag), and they can't be picked. If a key typed by hand names one, the reason shows under the field and saving is refused.

After saving, the console shows the words, not the key: in lists, record views, pickers, confirmation dialogs, the cards and the dashboard. Editing the record shows the words too, and the field keeps its link to the string when you save.

Two places show the key

UpTop's own dashboard shows a reward's name as typed. The console's search box matches the key, not the words — search for reward.vip rather than for the text.

Location and group names never reach users, and event descriptions come from the event sources, so those fields take plain text only.