Using the Language I/O Domo Dashboard
Before you begin
There are two ways you can access your Language I/O Usage Dashboard, depending on whether you use Google services or not:
- If your organization uses Google accounts for email:
- Select Single Sign-On, then Continue with Google.
- Sign in with your Google credentials to open the Dashboard.
- If your organization does not use Google accounts for email:
- Select Single Sign-On.
- Click on the Sign up link.
- Fill in the email address field with your corporate email address, create a password and click Continue.
- If the registration is successful, the Dashboard opens.
Once you are logged in, your usage dashboard gives you an up-to-date overview of how your team is using Language I/O. This data is updated daily. You can filter, export, and measure it across a variety of metrics. We explain some of these metrics in more detail in the next sections.
Dashboard Filters
One of the most useful ways to filter your usage reports is by date:
- In the upper right corner of the dashboard, select the filter button “Choose Date” to adjust:
- Changing the “Date Range” filters the data displayed across the entire dashboard to the selected period. You can use preset ranges, or create a custom range by using the “Between” option at the bottom:
- Set a “Graph by” value to adjust the granularity of the data across the entire dashboard for each data card. The default view is per month:
You can find additional filters by selecting “+” in the top left of the screen, to the right of Filter Views:
You can turn any of the listed fields into a filter for the dashboard. You can use multiple filters simultaneously.
To remove a filter, simply select the filter at the top of the screen and click the red “trash” icon:
Alternatively, you can select items in the data cards within the dashboard itself to filter the dashboard. You will find information about each card below. To use the cards as a filter, simply click on a datapoint (for example, a specific date), a legend item (for example, a specific translation type), or an axis label (for example, a specific language pair). This filters the entire dashboard to this specific item. This way, you can more easily measure this item against the variety of metrics presented on the dashboard.
Total Cards
The upper part of the dashboard shows your subscriptions details and your totals at a glance:
(Click to enlarge)
Subscription Details
This is the start and end dates of your current subscription term, and the percentage of credits that you have used to date:
(Click to enlarge)
Credits Used During Current Term
Below the table, you can see the number of credits you used in the current term (in orange), out of your total of allowed credits (in blue):
Next to the Credits Used During Current Term chart, three data cards aggregate your total usage in Words, Credits, and Sessions, respectively.
Words
Words is the total number of source words translated by the Language I/O solution.
Credits
Credits converts each translation to the credits total, according to their respective credit rates.
Sessions
Regardless of the CRM that you use with your Language I/O solution, Sessions indicates how many separate translation sessions were processed. For example, if you provide support for a client through an online chat service, the first message in this chat from a customer and all subsequent translations until the chat is closed represent one session.
Data Cards
The customer dashboard comes equipped with standard data cards. These cards present different dimensions of usage across various graphs and charts. Use the date filter to adjust all this information to show different date ranges as required.
Words Translated
The first data card, Words Translated, shows the number of words translated. The default view is per month. Use “Graph by” (see above) to show the quantity by day, quarter, year, etc.
Words Translated by Content Type
The next data card, Words Translated by Content Type, shows usage according to the origin of the translations. This means whether a given translation came from a chat interaction, the portal, an article, or from a submitted ticket, etc.
Content types can be the following:
- Chat: Chat package installed in CRM
- Ticket: Ticket/email package installed in CRM
- Social: Social package installed in CRM
- Portal: Machine Translation (MT) test portal and Machine Translation work submitted through XTM manually (either via customer submission or by the Language I/O Localization team)
- Article: Articles submitted through CRM, and MTPE (Machine translation with post edit ) and HT (Human translation) work submitted through XTM portal manually (either via customer submission or by the Language I/O Localization team)
- API: built API connecting Language I/O and the customer’s system
- Browser: Chrome browser extension
- TMs: Language I/O MT layer through XTM
- Bot: Chatbot package installed in CRM
Sessions Translated
As mentioned above, each Session aggregates all translations associated with one interaction (for example, a chat conversation or an email exchange). The Sessions Translated card shows this number across time on the horizontal axis:
Words Translated by Type
Words Translated by Type shows you the amounts of words translated based on the type of translation requested. This means machine translation, human translation, expensive languages, etc.
Translation types are:
- Machine: Machine translation
- Machine 2: Retranslated machine translation
- MT X: Machine translation with expensive languages
- HT/Human: Human translation
- HT X: Human translation with expensive languages
- MTPE: Machine translation with a human linguist post edit
- MTPE X: Machine translation with a human linguist post edit with expensive languages
Tracking language and language pair frequency
The standard dashboard shows two different data cards to track how languages are being used.
The first is Words Translated by Source/Target. This card uses a heat map chart to break down the frequency of language pairs. The left-hand axis shows the sum of words for each source language. This means the language that the requested translation is in before it is translated. The target language, across the horizontal axis, is the language that the translation request is translating to.
In the example below, it shows that most translations are English (US) to Spanish (Latin America):
(Click to enlarge)
The second card is Words Translated by Language Pair. It shows the sum of translated words grouped by language pairs, regardless of whether each given language was the source or the target language in each translation. This means for example that the “English <> Spanish” row shows the total sum of words translated both from English to Spanish and from Spanish to English:
See also
Interacting with and Exporting from the Domo Dashboard
Comments
0 comments
Please sign in to leave a comment.