Reports in Transifex show you how many words were translated, edited, and reviewed by your translators, along with the Translation Memory (TM) leverage and the Transifex AI, TM, and Machine Translation (MT) fill-ups used. It's helpful to see who your most active translators are or figure out how much you should pay your Translators and Reviewers.
🔒 Available on: Growth and up · Who can do this: Organization Administrator, Project Maintainer, Team Manager · Compare plans
📝 Note:
Translation Activity Reports are available on our Growth plan and up.
Reports update each day at 04:30 UTC.
The report lists all users associated with the project, including Admins, Project Maintainers, and Team members.
Accessing Reports
Any user who belongs to an organization where the reports feature is available can access the reports page.
Collaborators (language coordinators, translators, and reviewers) can only view their translation activity.
Team Managers can only view the translation activity of the teams they manage.
Project Maintainers are authorized to view the translation activity for the teams and projects they are maintainers for.
Organization Administrators are authorized to view all collaborators' activities.
You can learn more about various user roles in Transifex in Understanding user roles.
Using Reports
Here's a look at how Reports work:
Click the Reports tab in the main navigation.
Here, you see the number of words filled up by AI and TM, and the number of words translated by MT.
Below you can see the translation activity by your team members. You can filter the data by project, language, or date. For instance, you can find out who worked on translations for a project in July.
To sort data in a column, click on the header bar above that column. Click once to sort by ascending order. Click it again to sort by descending order.
To download a copy of your report as a CSV file, click the Download CSV button in the header.
Seeing a month-over-month breakdown of translation activity
Sometimes, you may want to know how much work your translators and reviewers have done month over month. To get such a report, click the down arrow next to Download CSV on the Reports page and click Download CSV (Monthly).
The report will include columns that break down each translator’s activity by year and month. Note that the report will only include data from your selected date range. So if you choose January 1 to January 15 on the Reports page, the work a translator did on January 16 will not be included in the CSV.
Translated, edited, and reviewed words
The main metrics in Reports are translated, edited, and reviewed words. Here's what each one means:
Translated Words: Translated words are the number of newly translated words. Only the first translation for a string is counted. This means each source string only appears in the new word count once.
Edited Words: Edited words are changes made to an existing translation. It's important to note that Edit words are not reviewed words.
Reviewed Words: Reviewed words are translations marked as reviewed or proofread.
The "First Time Edited/Reviewed Words" toggle allows you to distinguish between all edits/reviews (total count) and only the first ones. When this toggle is enabled, the report will count only the first edit or review performed by a user on each string during the selected time period.
This toggle is available in both the People and My Work tabs, allowing individual translators and reviewers to view their own activity using the same first-time edit and review metrics.
This functionality is also accessible via the API Organization Activity Reports API Endpoint by setting the first_time_edits boolean attribute.
📝 Note: A first-time edit is counted when a user modifies a string after a status change (e.g., from untranslated to translated, or from reviewed to unreviewed). If a string is edited multiple times without a status change, only the first edit is counted when the toggle is enabled.
If the string is reviewed and then edited again, that subsequent edit will be counted as a new first-time edit.
The count is based on the number of words in the source string for all these metrics. For example, the source string "Hello world" has 2 words. If it is translated to "Hola mundo," the new word count is still 2, because the count uses the source string, not the translation.
Reviewed words based on origin
It is also possible to see the breakdown of the origin for reviewed words, meaning you can see how much reviewed content came from AI, MT, TM, or other sources:
Each translation bar displays reviewed word counts broken down by translation origin:
Transifex AI: words reviewed that were originally translated by Transifex AI.
Machine Translation: words reviewed from MT services.
Translation Memory: words reviewed that were auto-filled by TM.
Other: all remaining sources, including the Editor, API, integrations, etc.
Hovering over the distribution will display the word count for each category:
📝 Note: Toggling the First Time Edited/Reviewed Words option will also affect what will be displayed in the distribution. The same data will also be available when downloading the report in CSV format.
How First-time Action Words are Calculated
This section explains how First-Time Action words are calculated and how the final word counts are derived in the Translation Activity Report.
A First-Time Action is counted when an action is performed on a string for the first time, unless the action is considered a re-action (for example, a re-review after an unreview).
Below is an example using a 5-word source string and a sequence of actions performed on it.
Example: Action History and Counting Logic
Action | Counted As |
Translator A translates the string | 1st Time Translation |
Translator A edits their own translation to fix a typo | 1st Time Edit |
Translator A edits again to rephrase | Added to Total Edits only |
Reviewer B marks the string as Reviewed | 1st time Review |
Reviewer B edits the translation | 1st Time Edit |
Reviewer B unreviews the string | (no count) |
Reviewer B edits again | 1st time Edit |
Reviewer B marks it as Reviewed again | Added to Total Reviews |
Translation Deleted | (no count) |
Translator A translates the string | 1st Time Translation |
Reviewer B marks the string as Reviewed | 1st Time Review |
Reviewer B unreviews the string | (no count) |
Reviewer B marks it as Reviewed again | Added to Total Reviews |
Final Word Count Results
With First Time Edited/Reviewed ENABLED
Translated Words: 10 (Steps 1 and 10)
Edited Words: 15 (Steps 2, 5, and 7)
Reviewed Words: 10 (Steps 4 and 11)
With First Time Edited/Reviewed DISABLED
Translated Words: 10 (Steps 1 and 10)
Edited Words: 20 (Steps 2, 3, 5, and 7)
Reviewed Words: 20 (Steps 4, 8, 11, and 13)
How Re-reviews Are Identified
A review is considered a re-review only when a Review action follows an Unreview action in the string’s history.
In that case:
The words are not counted as First-Time Reviewed
They are added only to Total Reviews
Proofread and Auto-reviewed Strings
Proofread actions are treated as review actions for reporting purposes.
If a string is auto-reviewed (for example, via 100% TM match, or a high TQI score)
And a human user later marks it as Proofread
This action is counted as a First-Time Review, unless it follows an Unreview step
Action | Counted As |
String is auto-translated and auto-reviewed (100% TM match or high TQI score) | (no user action counted) |
Reviewer B marks the string as Proofread | 1st Time Review |
Reviewer B edits the translation after proofreading | 1st Time Edit |
Reviewer B unreviews the string | (no count) |
Reviewer B marks the string as Proofread again | Added to Total Reviews |
TM Leverage and Fill-ups
You can see the number of words filled up by AI, TM, and MT under the filter bar.
Translation leverage
Next to the new word count in the report, the TM leverage for the new words a translator translated (translation leverage) and for the words they edited (edit leverage) is displayed as a bar chart. With it, you can see how much a translator relied on TM for the new words they translated or the updates they made to existing translations.
📝 Note: The TM leverage information in Reports shows the leverage of translated and edited strings. The Export TM leverage view shows the TM leverage before translation or post-editing.
Activity Report use cases and scenarios
To better understand the information in Transifex Activity Reports, please take a look at the scenarios described below.
Scenario 1
User A translates the following untranslated string:
Source string: "Please provide a username".
Number of source words: 4
In the translation activity report, for the specific translator, the following information will be available:
Translated Words: 4
Edited Words: 0
Reviewed Words: 0
Scenario 2
User A translates an untranslated string. After the initial translation is saved, User B edits the translation submitted by User A.
Source string: "Please provide a username"
Number of source words: 4
In the activity report, the following user activity will be available:
User A
Translated Words: 4
Edited Words: 0
Reviewed Words: 0
User B
Translated Words: 0
Edited Words: 4
Reviewed Words: 0
Scenario 3
TM automatically translates an untranslated string (100% TM match found, and TM auto-fill up is enabled). The TM suggestion was introduced by User C in the past.
Source string: "Please provide a username"
Number of source words: 4
In this case, no activity will be available for user C in the translation activity report since the specific translator did not work on that string - the system automatically translated the string based on previous work done in another string in the past.
Scenario 4
TM automatically translates an untranslated string. After that, user A edits the existing translation and submits an updated translation version for that string.
Source string: "Please provide a username"
Number of source words: 4
In the activity report for user A, the following information will be available:
User A
Translated Words: 0
Edited Words: 4
Reviewed Words: 0
This scenario is true regardless of the match %.
📝 Note: If a translator manually selects a suggestion to translate an untranslated string within the Editor and presses the save button, it is considered manual work done by the specific user. As a result, the number of source words translated in the report will be counted as translated words for that user.
Scenario 5
An untranslated string is translated by User A via the Transifex API, the Transifex CLI (tx), or a file upload.
Source string: "Please provide a username"
Number of source words: 4
In the activity report for user A, the following information will be available:
User A
Translated Words: 4
Edited Words: 0
Reviewed Words: 0
Scenario 6
User A (maintainer) edits the source text of the following source string within the Editor. The option "Save and Keep translations" is selected.
Source string: "Please provide a username"
Number of source words: 4
The string is translated already in 2 languages (fr, de)
In the activity report, for User A, for fr, and de, the following information will be available:
User A
Translated Words: 8 (4 words per target language)
Edited Words: 0
Reviewed Words: 0
📝 Note: When an already translated source string is modified within the Editor, the string returns to its untranslated state since the words in the source language are no longer the same.
So, when User A changes the source text of the string from "Please provide a username" to "Provide a usernameplease", the option "Save and keep the translations" allows User A to re-apply the previous translation for languages the old version of the string was translated to already. So, what happens is that User A re-translates the new version of the string the same way as before.
Scenario 7
User A gives the first translation for Source string - version #1. After that, the source text is modified, and the string returns to its untranslated state. User B submits a translation for the new version of the string.
Source string - version #1: "Please provide a username"
Number of source words: 4
Source string - version #2: "Please provide a username to login"
Number of source words in version #2: 6
In the activity report for users A and B, the following information will be available:
User A
Translated Words: 4
Edited Words: 0
Reviewed Words: 0
User B
Translated Words: 6
Edited Words: 0
Reviewed Words: 0
Scenario 8
An untranslated string is automatically translated by MT (MT auto-fill is enabled).
Source string: "Please provide a username"
Number of source words: 4
In the translation activity report, the number of words translated by MT automatically will be available at the top of the reports page:
📝 Note: Since February 2, 2026, the Autosave action for MT and AI translations, through the buttons in the Editor for single strings, sets the translation origin to MT or AI. The word count is not counted for the user who pressed the button.
Scenario 9 (case1)
User A translates an untranslated string and reviews this string. After the initial translation & review of the string, User A edits the translation.
Source string: "Please provide a username"
Number of source words: 4
In the activity report, the following user activity will be available:
User A
Translated Words: 4
Edited Words: 4
Reviewed Words: 4
The result is the same with the First Time Edited/Reviewed Words toggle on or off, because User A makes only one edit and one review of the string.
Scenario 9 (case2)
User A translates an untranslated string and also reviews it. After the initial translation & review of the string, User A un-reviews the string, edits the translation, and reviews it again.
Source string: "Please provide a username"
Number of source words: 4
In the activity report, the following user activity will be available:
User A
Translated Words: 4
Edited Words: 4
Reviewed Words: 8
This example assumes the First Time Edited/Reviewed Words toggle is turned off, which counts the re-review in Total Reviews.
Scenario 10
Source string: "Please provide a username"
Number of source words: 4
Available TM suggestion: 67%
Machine translation runs and translates an untranslated string. Machine translations are saved to the TM only after someone reviews them. User A edits the machine-translated string and submits a new translation version, which is saved to the TM when it is submitted, unless the project only adds reviewed translations to the TM.
In the activity report, the following user activity will be available:
User A
Translated Words: 0
Translation leverage: -
Edited Words: 4
Edit leverage: 50-74% leverage, 4 words
Reviewed Words: 0
After User A submits the translation, the available TM suggestions for the above string are:
100% TM suggestion based on the translation submitted by User A
67% TM suggestion based on similar strings translated in the past
Now, User B edits the translation done by User A and submits a new translation version for the same string.
In the activity report, the following user activity will be available:
User B
Translated Words: 0
Translation leverage: -
Edited Words: 4
Edit leverage: 50-74% leverage, 4 words (the 100% TM suggestion created by User A is already used as a translation, so it's not taken into consideration)
Reviewed Words: 0
Cost Calculation and Estimation
Cost Calculation Reports
These reports show the actual cost of a translation job after completion, based on already translated strings. Found under the "People" tab in the Reports section, they provide a breakdown of translation, editing, and review activities, along with the Translation Memory (TM) leverage available at the time of translation. This allows for an accurate assessment of costs tied to each contributor’s work.
Cost Estimation Reports
These reports help estimate the potential cost of translating untranslated strings or editing existing translations. They reflect the Translation Memory (TM) leverage as it stands at the moment the report is generated—essentially showing what the cost would be if the work were done now. This report is available under the "TM Leverage Estimation" tab.
📝 Note: For details on how the above Cost Calculation & Cost Estimation Reports can be used to calculate cost and assist you with billing, see Streamlining translation tracking and invoicing with Transifex reports.
How are reports affected when a project is updated?
If a target language is being removed from a project, the related translation activity will still be available in the reports
If a resource is being removed/updated, the related translation activity will remain in the report results.
If a project is deleted, the translators' activity that is related to that project won't be available in the reports anymore.
💡 Tip
Looking for more help? Get support from our Transifex Community Forum!
Find answers or post to get help from Transifex Support and our Community.









