Note: Lokalise Analytics includes data from both Lokalise Expert and Lokalise Vantage. Use the Workspace dropdown to view analytics for Expert, Vantage, or both.
The Usage dashboard in Lokalise Analytics helps you understand how localization resources are used across your projects. You can analyze processed word usage and translation methods, monitor Over-the-Air (OTA) activity, track translation memory leverage, and explore workflow and automation performance, configuration, and usage.
This article covers the reports and metrics available in the Usage dashboard. For an overview of Lokalise Analytics, including how to access Analytics and choose a product, see Lokalise Analytics.
Accessing the Usage dashboard
To access the Usage dashboard, open the corresponding tab on the Analytics page.
Processed words
You may want to review the Processed words article to better understand how Lokalise measures usage.
The Processed words tab in the Usage dashboard provides insights into processed word usage and translation methods across your projects. Using the Processed words tab, you can analyze historical usage data, estimate future resource requirements, and better plan localization costs.
Filtering data
You can filter Usage dashboard data by:
Date
Product — Expert, Vantage, or both
Project ID
Project name
Target language
Combine filters to narrow the data to specific projects, products, languages, or time periods.
Translation methods overview
The Processed words overview table displays the number of processed words and translation methods used for each language, based on the selected date range and filters.
Columns:
Language — click a language name to filter results by that language. If multiple projects use the same language name but different language IDs, they are grouped together.
Processed words — shows the total number of processed words for the selected language.
Translation methods — shows how many words were translated using each translation method, including Pro AI and Standard AI/MT.
Base processed words by month
The Base processed words by month chart shows how many words were processed in your projects each month. This includes words added or updated in the base language, as well as target-language words modified through translation activity, imports, automations, or AI/MT actions.
Chart details:
Dark blue — processed words originating from base language changes, such as new content or source text updates.
Light blue — total processed words for the month, including target-language words created or modified through translation activity.
Skipped words — words that were detected during processing but not counted toward processed word usage, for example because they had already been counted through another workflow such as an API import. Skipped words are shown for visibility but are not included in processed word totals.
Word counts are cumulative across all base languages used in your projects.
Processed words by month
The Processed words by month chart shows how processed words are distributed across different translation methods over time. Each bar represents the total number of processed words for a specific month, grouped by translation method.
Translation methods include:
Human translation
Translation memory
Standard AI/MT
Pro AI
API
Import
Other
Hover over a chart segment to see the processed word count and percentage for each translation method for the selected month.
Base processed words by translation method
This chart shows how base processed words are distributed across different translation methods.
Each bar represents the total number of processed words for a specific translation method and is divided into:
Created — newly added base-language content.
Updated — existing base-language content that was modified.
Skipped words — words that were detected during processing but not counted toward processed word usage, for example because they had already been counted through another workflow such as an API import. Skipped words are shown for visibility but are not included in processed word totals.
This helps you understand how base content enters or changes in your localization workflow across imports, API updates, and other sources.
Processed words by project and action
The Processed words by project and action table shows created, updated, and total processed words for each project. Use this table to compare usage across projects and understand where most content is being created or updated.
Columns:
Product — shows which Lokalise product the project belongs to. For example, Expert for standard localization projects or Vantage for document and long-form content workflows.
Vantage is Lokalise’s solution for translating documents and long-form content, including formats and sources such as DOCX, Google Docs, and Strapi. To learn more, see What is Lokalise Vantage?
Project — shows the project name.
Created processed words — shows the number of processed words from newly added content.
Updated processed words — shows the number of processed words from existing content that was modified.
Total processed words — shows the combined total of created and updated processed words.
Processed words by project and method
The Processed words by project and method table shows processed words for each project, grouped by translation method.
Use this table to compare how different projects rely on different translation methods, such as human translation, translation memory, AI/MT, API, imports, offline work, or other sources.
Columns:
Product — shows which Lokalise product the project belongs to (Expert or Vantage).
Project — shows the project name.
Translation memory — processed words translated using translation memory.
Human translation — processed words translated manually by users or vendors.
Standard AI/MT — processed words translated using standard AI or machine translation.
Pro AI — processed words translated using Pro AI.
API — processed words created or updated through the API.
Import — processed words created or updated through file imports.
Offline — processed words translated or updated through offline workflows.
Other — processed words that do not fall into the listed methods.
Translation method breakdown
The Translation method breakdown section shows detailed metrics for each translation method, such as Translation memory, Human translation, Pro AI, and Standard AI/MT.
Each method has its own section with summary metrics and a monthly chart, making it easier to compare how different translation methods contribute to your localization workflow.
Metrics include:
Translations created — the number of new translations created using this method.
Translations updated — the number of translations created by this method that were later meaningfully changed.
Created vs. updated by month — a monthly breakdown showing how many translations were created and how many were later updated.
Use these metrics to compare translation methods and understand how often translations created by each method are later changed.
You can customize this section to view metrics for Processed words or Translations using the dropdown in the right corner:
OTA
The OTA tab in the Usage dashboard provides insights into Over-the-Air (OTA) activity across your projects and bundles.
Using the OTA tab, you can monitor OTA adoption, analyze traffic and download activity, track platform distribution, and identify usage trends across your localization workflows. The available reports help you understand how OTA is being used across projects, bundles, and platforms such as iOS, Android, and Flutter.
Filtering data
You can filter OTA analytics data using the following filters:
Date — select the time range for the displayed analytics data.
Time grouping — group data by day, week, month, quarter, or year, depending on the level of detail you need.
Project ID — filter results by specific Lokalise project IDs.
Project — filter data by project name.
Platform — filter OTA activity by platform, such as iOS, Android, or Flutter.
These filters can be combined to analyze OTA usage trends across specific projects, platforms, and time periods.
Current drivers
The Current drivers section provides a high-level overview of OTA activity for the most recent period within the selected date range.
The period depends on the selected Time grouping filter. For example, if Week is selected, this section shows activity for the most recent week in the selected date range.
It highlights overall traffic and download trends, along with the most active projects and bundles in your OTA workflow.
Metrics include:
Traffic — the total amount of OTA traffic generated during the selected period.
Downloads — the total number of OTA bundle downloads.
Projects with traffic — the number of projects that generated OTA traffic.
Bundles with traffic — the number of OTA bundles that generated traffic during the selected period.
Each metric also shows how the current period compares to the previous one, helping you identify usage growth or declines over time.
The section also includes:
Most active project (current period) — shows the project with the highest OTA traffic, including traffic distribution across supported platforms.
Most active bundle (current period) — shows the bundle with the highest OTA traffic, including its platform and total traffic volume.
Traffic by platform
The Traffic by platform chart shows the distribution of OTA traffic across supported platforms during the selected time period. Traffic is measured in gigabytes (GB) and represents the amount of OTA content delivered to client applications.
Use this chart to understand which platforms generate the most OTA traffic and how OTA usage is distributed across your mobile ecosystem, such as iOS, Android, or Flutter.
Hover over a chart segment to view the exact traffic volume and percentage for each platform.
Downloads by platform
The Downloads by platform chart shows the distribution of OTA bundle downloads across supported platforms during the selected time period.
Use this chart to understand which platforms generate the highest number of OTA downloads and how bundle adoption is distributed across your applications.
Hover over a chart segment to view the exact number and percentage of downloads for each platform.
Traffic over time by platform
The Traffic over time by platform chart shows OTA traffic trends across supported platforms over time. Traffic is measured in gigabytes (GB) and grouped by the selected time interval, such as day, week, or month.
Use this chart to monitor how OTA traffic changes over time for platforms such as iOS, Android, or Flutter. Traffic spikes may reflect application releases, increased user activity, or large OTA bundle rollouts.
Hover over a chart segment to view the exact traffic volume for each platform during a specific time period.
Downloads over time by platform
The Downloads over time by platform chart shows OTA download trends across supported platforms over time.
Downloads are grouped by the selected time interval, such as day, week, or month, making it easier to identify changes in OTA adoption and bundle delivery activity.
Use this chart to monitor how OTA downloads evolve across platforms such as iOS, Android, or Flutter. Changes in download volume may reflect release frequency, adoption growth, seasonal usage patterns, or rollout activity.
Hover over a chart segment to view the exact number of downloads for each platform during a specific time period.
Most active project
The Most active project section highlights the project that generated the highest amount of OTA traffic across the current time period.
The report includes the total OTA traffic for the project, traffic distribution by platform, and the date of the most recent OTA activity.
Use this section to identify which projects generate the most OTA usage and monitor platform-level traffic distribution across your applications.
Most active bundle
The Most active bundle section highlights the OTA bundle that generated the highest amount of traffic during the current time period.
The report includes the bundle name, bundle ID, platform, total OTA traffic, and the date of the most recent activity.
Use this section to identify which OTA bundles are most actively distributed across your applications and platforms.
Projects overview
The Projects overview table provides a detailed view of OTA traffic and activity metrics for each project.
Use this table to compare OTA usage across projects, monitor recent activity, and identify traffic trends over time.
Columns include:
Project — the project name.
Total traffic (GB) — the total amount of OTA traffic generated by the project.
Last active on — the date of the most recent OTA activity for the project.
Previous period traffic (GB) — OTA traffic generated during the previous comparable time period.
Change from previous period (GB) — the traffic increase or decrease compared to the previous period.
% change from previous period — the percentage change in traffic compared to the previous period.
Android traffic (GB) — OTA traffic generated by Android applications.
iOS traffic (GB) — OTA traffic generated by iOS applications.
Flutter traffic (GB) — OTA traffic generated by Flutter applications.
Use the table to identify the most active projects, compare platform distribution, and monitor changes in OTA usage over time.
Bundles overview
The Bundles overview table provides detailed OTA traffic and activity metrics for individual bundles.
Use this table to analyze bundle-level OTA usage, compare traffic across releases, and monitor activity trends over time.
Columns include:
Bundle name — the bundle name and release identifier. Click on the name to download the bundle.
Bundle ID — the unique OTA bundle ID.
Project — the project associated with the bundle.
Platform — the platform the bundle belongs to, such as iOS, Android, or Flutter.
Bundle size (MB) — the size of the OTA bundle in megabytes.
Total traffic (GB) — the total OTA traffic generated by the bundle.
Last active on — the date of the most recent OTA activity for the bundle.
Previous period traffic (GB) — OTA traffic generated during the previous comparable time period.
Change from previous period (GB) — the traffic increase or decrease compared to the previous period.
% change from previous period — the percentage change in traffic compared to the previous period.
Use this table to identify the most actively distributed bundles, compare release adoption, and monitor OTA traffic patterns across platforms and projects.
TM leverage
The TM leverage tab in the Usage dashboard shows how much translated content was actually produced using translation memory during the selected period.
The available reports help you understand how translation memory is used across your projects and language pairs, measure TM adoption over time, and identify opportunities to improve translation reuse. Unlike Processed Words, TM leverage includes all translations created from TM matches, regardless of whether they are billable.
Filtering data
You can filter TM leverage data using the following filters:
Date — select the time range for the displayed analytics data.
Time grouping — group data by day, week, month, quarter, or year, depending on the level of detail you need.
Project ID — filter results by specific Lokalise project IDs.
Project — filter data by project name.
Target language — filter data by target language.
Base language — filter data by base language.
These filters can be combined to analyze TM usage across specific projects, language pairs, and time periods.
TM leverage overview
The summary cards at the top of the dashboard show the following metrics for the selected period:
TM-leveraged words — the total number of target words translated using a translation memory match, regardless of the match percentage.
TM translations — the total number of translations created using a translation memory match.
TM share of all words — the percentage of all translated target words that were produced using translation memory. It is calculated by dividing TM-leveraged words by the total number of translated words.
TM leverage over time
The TM leverage over time chart shows how translation memory usage changes over the selected period.
You can switch between viewing the total number of TM-leveraged words and TM translations to identify trends and compare usage over time.
Words leveraged by TM match
The Words leveraged by TM match chart breaks down translated target words by the translation memory match percentage that was applied.
Use this report to understand how much of your translation memory usage comes from exact matches (100%) versus fuzzy matches (50%, 75%, 85%, and 95%).
Top 10 language pairs by TM leverage
The Top 10 language pairs by TM leverage chart shows the 10 language pairs with the highest translation memory usage.
You can switch between TM-leveraged words and Translations to compare the number of translated target words and translations that used translation memory matches.
TM leverage by project
The TM leverage by project table provides a project-level breakdown of target words and translations that used translation memory matches. Use it to compare translation memory usage across projects and identify which projects benefit most from translation memory.
The table includes the following columns:
Project — the project name.
Words — the total number of translated target words.
TM-leveraged words — the number of target words translated using translation memory matches.
TM-leveraged words share — the percentage of translated target words that used translation memory matches.
Translations — the total number of translations.
TM-leveraged translations — the number of translations that used translation memory matches.
TM-leveraged translations share — the percentage of translations that used translation memory matches.
Most leveraged language pair — the language pair with the highest translation memory usage in the project.
Users
The Users dashboard helps you understand how your team members use Lokalise, monitor seat usage, and identify users who may no longer need access to certain projects.
You can also explore individual members' activity, permissions, and project access.
Workspace members
The Workspace members section provides an overview of team membership, Advanced seat usage, and user activity. Use the Date filter at the top of the dashboard to select the reporting period.
The following metrics are available:
Total seats in use — the total number of seats currently occupied by users in your team. Each user occupies one seat, regardless of how many projects they belong to.
Advanced seats purchased — the total number of Advanced seats available under your team's subscription.
Advanced seats in use — the number of Advanced seats currently occupied by team members.
Active members — the number of team members who performed an activity in at least one project during the selected period.
Idle members — the number of team members who have access to at least one project but did not perform any project activity during the selected period.
Comparing Advanced seats purchased with Advanced seats in use helps you understand how much Advanced seat capacity remains available.
The Active members and Idle members metrics help you identify how many people are using their project access. For example, a high number of idle members may indicate that some users no longer need access to certain projects.
For more information about seat types, limits, and how to manage them, see Teams and roles and Team quotas.
Member roster
The Member roster table provides detailed information about each team member, including their roles, seat usage, project access, and activity. You can use this table to see who has access to your projects, how actively they use Lokalise, and which members may need their permissions reviewed.
The following columns are available:
User ID — the unique identifier of the user in Lokalise.
Member — the user's name.
Email — the email address associated with the user's account.
Team role — the user's role within the Lokalise team, such as Owner, Admin, Biller, or Member.
Status — the user's activity status. Possible values include:
Active — the user performed an activity in at least one project during the selected period.
Idle — the user has access to at least one project but did not perform any project activity during the selected period.
Never logged in — the user has never signed in to their Lokalise account.
Billable seat — the type of seat assigned to the user for billing purposes.
Seat roles — roles associated with the user's team or project permissions, such as Owner, Content creator, or Custom. This column does not necessarily list every role the user holds across all projects.
Account created — the date when the user's Lokalise account was created.
Joined team — the date when the user joined the team.
Last login — the date of the user's most recent sign-in to Lokalise.
Last activity — the date of the user's most recent recorded activity.
Days active — the number of days on which the user was active during the selected period.
Projects with access — the number of projects the user has permission to access.
Projects used — the number of projects in which the user performed an activity during the selected period.
Processed words — the number of processed words attributed to the user during the selected period.
Keys processed — the number of translation keys processed by the user during the selected period.
Languages — the number of languages the user worked with during the selected period.
Use Projects with access and Projects used together to identify members who have access to multiple projects but actively work in only a few of them. Combined with activity and seat information, this can help you review project permissions and seat allocation.
Composition & access hygiene
This section helps you understand how team members are distributed across roles, seat types, and project access.
Members by role and seat
This chart shows the distribution of team members by team role and seat type, including members who do not have access to any projects.
The inner ring shows the proportion of members with a Billable seat or No seat, while the outer ring breaks these groups down by team role. The center shows the total number of team members.
Use this chart to understand how seats are distributed across different roles and identify opportunities to review seat allocation.
User groups and project access
This table shows the user groups in your team, their types, and the number of members and projects associated with each group.
The following columns are available:
Group — the name of the user group.
Group type — the type of group, such as Admin.
Members — the number of users belonging to the group.
Projects in scope — the number of projects the group provides access to.
Use this table to understand how project access is distributed through user groups and identify groups that may have broader access than necessary.
Membership and activity over time
This chart shows how team membership and user activity change over time. Use the Date and Time grouping filters to choose the reporting period and how the data is grouped.
Each bar shows the number of members in different categories:
Idle — members who remained inactive during the period.
Dormant — members who were previously active but became inactive.
Reactivated — members who resumed activity after a period of inactivity.
Active — members who continued to be active.
Joined — new members who joined the team during the period.
Removed — members who were removed from the team during the period.
Use this chart to track changes in team size, identify periods of increased or decreased activity, and see how many inactive members return to using Lokalise.
User insights
The User insights section provides detailed information about individual team members, including their activity and project access.
By default, this section does not display any data. To view a member's insights, click their row in the Member roster table above or use the User ID dropdown in the User insights section to select a member. The charts will then show information for the selected member.
Member activity
This chart shows the selected member's activity during the selected period, broken down by action and how it was performed.
Activities can include updating translations, adding or modifying keys, importing or exporting projects, closing task items, and many other actions.
The chart distinguishes between three activity types:
Manual — actions performed directly by the user in Lokalise.
API — actions performed through the Lokalise API.
Account-level — account-related activities, such as signing in, signing out, or changing Analytics filters.
Each bar shows the number of recorded events for a particular action. Less common actions may be grouped under Other.
Use this chart to understand how the member interacts with Lokalise and whether their activity comes mainly from manual work, API operations, or account-level actions.
Sign-ins
This table shows the selected member's sign-in history during the selected period, including when and where they accessed Lokalise.
The following columns are available:
Date — the date when the member signed in.
Member — the member's name.
Country — the country from which the member signed in.
City — the city from which the member signed in.
Sign-ins — the number of recorded sign-ins for that date and location.
Use this table to understand how frequently a member signs in to Lokalise and review their sign-in locations.
Project access and activity
This table shows which projects the selected member has access to and how they used those projects during the selected reporting period.
The following columns are available:
Project — the name of the project.
Project ID — the unique identifier of the project in Lokalise.
Roles — the roles assigned to the member in this project.
Seat — the seat type associated with the member's project access.
Use — indicates whether the member was active in the project during the selected period.
Last activity — the date of the member's most recent recorded activity in the project.
Processed words — the number of words processed by the member in this project during the selected period.
Keys processed — the number of translation keys processed by the member in this project during the selected period.
Use this table to compare the member's project access with their actual activity. For example, you can identify projects where the member has access but has not performed any work during the selected period.
Words by target language
This chart shows the selected member's activity across different target languages during the selected reporting period.
For each target language, the chart displays two metrics:
Processed words — the number of words processed by the member for that target language.
Keys processed — the number of translation keys processed by the member for that target language.
Use this chart to see which languages the member works with most frequently and compare their activity across languages.
Workflows
The Workflows dashboard helps you monitor workflow activity across your projects, identify workflows that may need attention, and understand how your workflows perform over time.
You can track workflow statuses, review failed runs, and explore workflow activity and results.
Workflow overview
The Workflow overview section provides a summary of workflow statuses and failed runs. Use the filters at the top of the dashboard to narrow down the data:
Date — select the reporting period.
Time grouping — choose how data is grouped over time, such as by month.
Project ID — filter workflows by project ID.
Project — filter workflows by project name.
Workflow — select specific workflows to include in the dashboard.
Top projects — specify how many projects with the most workflows to display in the project breakdown (10 by default).
Hide idle runs — choose whether to exclude workflow runs that found no keys to process from the displayed statistics.
The following metrics are available:
Live workflows — the number of workflows currently active.
Canceled workflows — the number of workflows that have been canceled.
Paused workflows — the number of workflows currently paused.
Failed runs — the number of workflow runs that failed during the selected reporting period.
These metrics help you quickly assess the overall state of your workflows. For example, paused or canceled workflows may require further investigation, while failed runs can indicate issues that prevent workflows from completing successfully.
Workflows by state and project
The Workflows by state and project chart shows how workflows are distributed across your projects, grouped by their current status.
Each bar represents a project, with different colors indicating workflow states (such as Draft and Live). This helps you identify which projects have the most workflows and how many of them are currently active.
Projects are sorted by name. By default, the chart displays up to 10 projects with the most workflows. You can change this number using the Top projects filter at the top of the dashboard.
Note: This chart is not affected by the Date filter. It reflects the current workflow states regardless of the selected reporting period.
All workflows
The All workflows table provides an overview of all workflows across your projects, including their current states, configurations, and execution history.
Live workflows are listed first. The following columns are available:
Workflow — the name of the workflow. Click a workflow to select it and explore its details.
Project — the project the workflow belongs to.
State — the workflow's current state, such as Live, Draft, or Paused.
Trigger — the type of event that starts the workflow, such as a scheduled trigger.
Schedule — the configured execution schedule, including the time and time zone where applicable.
Steps — a summary of the actions configured in the workflow.
Target languages — the number of target languages covered by the workflow.
Last run — the date and time when the workflow last ran.
Last did work — the date and time of the most recent run that processed at least one key.
Succeeded runs — the number of completed runs that processed at least one key during the selected reporting period.
Idle runs — the number of runs that processed zero keys during the selected reporting period.
Version — the workflow's version number.
Last updated — the date and time when the workflow was last modified.
The Last run, Last did work, Succeeded runs, and Idle runs metrics follow the selected Date filter.
The Steps column provides a general summary of the workflow's actions. To review their actual execution order and detailed settings, refer to the Workflow steps table below.
Workflow steps
The Workflow steps table provides a detailed breakdown of each workflow's steps, including their execution order, types, and configuration.
Each row represents a single step, starting with the workflow's trigger. You can select specific workflows using the Workflow filter at the top of the dashboard or find them in the All workflows table.
The following columns are available:
Workflow — the name of the workflow.
Project — the project the workflow belongs to.
Version — the version number of the workflow.
Current version — indicates whether the step belongs to the latest version of the workflow.
Step — the step's position in the execution sequence.
Step name — the name assigned to the step, such as Trigger and scope or Apply Translation Memory.
Step type — the action performed by the step, such as Trigger, Clear translations, Apply TM, or End.
Details — the step's configuration, including relevant settings such as schedules, trigger conditions, target languages, or translation options.
Use the Show latest version only filter to control which workflow versions appear in the table. By default, only the latest versions are displayed. Set this filter to No to include older versions.
Rows are color-coded to make the table easier to navigate:
Blue — indicates the first step (trigger) of a workflow.
Yellow — indicates steps belonging to older workflow versions when Show latest version only is set to No.
This table helps you review how workflows are configured and understand the sequence of actions they perform.
Workflow executions
The Workflow executions section provides an overview of workflow runs during the selected reporting period, helping you understand how successfully your workflows execute and whether they process any content.
The following metrics are available:
Succeeded runs — the number of workflow runs that completed successfully.
Idle runs — the number of workflow runs that found no keys to process. A high number of idle runs usually indicates that workflows run more frequently than the content changes.
Waiting on task — the number of workflow runs currently waiting for a task to be completed before proceeding.
Success rate — the percentage of successful workflow runs.
Use these metrics to monitor workflow execution and identify potential issues. For example, a high number of idle runs may indicate that you should review your workflow schedules.
You can use the Hide idle runs filter at the top of the dashboard to exclude idle runs from the displayed execution statistics.
Runs over time
The Runs over time chart shows how many workflow runs occurred during each reporting period, grouped by their outcome.
The chart distinguishes between different run statuses, including:
Succeeded — runs that completed successfully.
Failed — runs that encountered an error.
Waiting on task — runs waiting for someone to complete a translation or review task.
Running — runs that started within the last day.
Use the Time grouping filter to adjust how runs are grouped over time. You can also use Hide idle runs to exclude runs that found no keys to process.
This chart helps you track workflow activity over time, identify changes in execution patterns, and spot periods with unusually high numbers of failed or incomplete runs.
Live but idle for 30 days
The Live but idle for 30 days section identifies active workflows that have not processed any keys in the last 30 days.
A workflow appears in this section if:
All its runs during the last 30 days processed zero keys.
It did not run at all during that period.
Workflows with failed runs are excluded from this section. You can investigate them separately in the Failed runs section.
If a workflow appears here, consider adjusting its schedule to run less frequently, expanding its scope to include more content, or pausing it to free up a live workflow slot.
Note: This section always uses the last 30 days of activity and is not affected by the Date filter.
What workflows delivered
The What workflows delivered section shows how much work your workflows have performed during the selected reporting period, including the number of keys affected, tasks created and completed, and words processed.
The following metrics are available:
Keys touched — the number of keys affected by workflow runs during the selected period.
Tasks created — the number of tasks created by workflows.
Tasks completed — the number of workflow-created tasks that have been completed.
Processed words — the number of words processed through workflows, including Translation Memory steps and workflow-created tasks. This corresponds to the Workflows category in the Processed words by delivery method chart.
Processed words via workflow tasks — the number of words processed through tasks created by workflows. Words processed by AI/MT or Translation Memory steps that do not create tasks are excluded.
These metrics help you understand how much translation work is handled by workflows and how much of that work involves tasks.
Processed words of workflow tasks
The Processed words of workflow tasks chart shows the number of words processed through workflow-created tasks over time, broken down by task type (such as Lokalise AI).
Use the Time grouping filter to change how the data is grouped over time.
Words are attributed to the period when the corresponding task was created, not when it was completed.
This chart helps you understand which types of tasks contribute to the translation volume delivered by your workflows and how that volume changes over time.
Processed words by delivery method
The Processed words by delivery method chart shows how your team's translated words are distributed across different delivery methods over time. Only words in target languages are counted.
Each stacked bar represents 100% of translated words for a given period, divided into the following categories:
Editor — translations entered through the editor, including manual editing and bulk actions.
API and integrations — translations delivered through the API or integrations.
Automations — translations delivered through automation rules.
File uploads — translations delivered through file imports, including offline XLIFF files and Figma.
Workflows — translations delivered through workflows, including Translation Memory steps and workflow-created tasks.
Manual tasks — translations delivered through manually created tasks.
API tasks — translations delivered through tasks created via the API.
Use the Time grouping filter to adjust the reporting intervals.
This chart helps you compare the contribution of workflows with other translation delivery methods and understand how your team's translation activity changes over time.
Automations
The Automations dashboard helps you monitor how automations are configured and used across your projects, track available automation capacity, and understand how much translation work they perform.
You can review automation settings, explore their action chains, and track their usage and results over time.
Automation overview
The Automation overview section provides a summary of configured automations, purchased capacity, and automation usage across your projects.
Use the filters at the top of the dashboard to narrow down the data:
Date — select the reporting period.
Time grouping — choose how data is grouped over time, such as by month.
Project ID — filter automations by project ID.
Project — filter automations by project name.
Monitored language — filter automations by the languages they monitor for content changes.
Automated language — filter automations by the languages they automatically translate.
Created by — filter automations by the users who created them.
The following metrics are available:
Automations — the number of automations currently configured.
Automations purchased — the total number of automations available under your subscription. See the Team quotas article to learn more.
Projects with automations — the number of projects that have at least one automation configured.
Actions configured — the total number of actions configured across your automations.
Comparing Automations with Automations purchased helps you understand how much of your available automation capacity is being used.
The Projects with automations and Actions configured metrics provide additional insight into how widely automations are used and how many actions they contain.
What changed over time
The What changed over time chart shows how the number of automations changes across reporting periods.
Automations are grouped into three categories:
Added — automations created during the period that still exist at its end.
Removed — automations that existed at the beginning of the period but were removed before its end.
Unchanged — automations that remained active throughout the entire period, existing at both its start and end.
Automations that were both created and removed within the same period are not counted.
The total number of automations at the end of each period is the sum of Added and Unchanged.
Use the Time grouping filter to adjust the reporting intervals. This chart helps you track changes in automation usage and understand whether the number of configured automations is growing, decreasing, or remaining stable.
Actions configured in automations by order
The Actions configured in automations by order chart shows how translation actions are distributed across the fallback chains of your currently configured automations.
Each horizontal bar represents an action type, such as Translation Memory, Machine Translation, or Lokalise AI. Colors indicate the action's position in the chain:
1st — the first action attempted when an automation runs.
2nd and subsequent positions — fallback actions that are attempted only if an earlier action does not apply.
The length of each bar indicates how many times that action is configured at the corresponding position across all automations.
The chart counts individual actions, not automations. For example, an automation that uses Translation Memory first and Lokalise AI second contributes one action to each category.
Use this chart to understand which translation methods are configured most frequently and how they are prioritized within your automation chains.
Automations by project
The Automations by project table shows how automations are distributed across your projects, including their language coverage, configured actions, and recent changes.
The following columns are available:
Project — the project where the automations are configured.
Automations — the number of automations in the project, counted separately for each monitored and automated language pair.
Rules — the number of configured automation rules in the project, regardless of how many language pairs each rule covers.
Cascading rules — the number of cascading automation rules in the project, which may be triggered as a secondary effect of another automation.
Actions configured — the total number of actions configured across the project's automations.
Last change — the date when an automation in the project was most recently created or modified.
Last changed by — the user who created or most recently edited an automation in the project.
Each automation rule is counted once for every monitored and automated language pair it covers, regardless of how many actions are included in its fallback chain.
For example, a rule that monitors English and translates into French and German counts as two automations but only one rule.
Use this table to compare automation usage across projects, review language coverage, and identify where automation configurations have recently changed.
All automations
The All automations table provides a detailed overview of the automations configured across your projects, including their language settings, action chains, and creation details.
The following columns are available:
Project — the project where the automation is configured.
Index — the automation's index within the project.
Monitored language — the language monitored for content changes that can trigger the automation.
Automated languages — the target languages that the automation processes.
Actions — the sequence of translation actions configured for the automation, such as Translation Memory followed by Lokalise AI. Actions are attempted in the specified order.
Created by — the user who created the automation.
Active since — the date when the automation became active.
Cascade — indicates whether cascading is enabled for the automation.
Use this table to review automation configurations, check which languages are covered, and understand how translation actions are organized across your projects.
Automation actions
The Automation actions table provides a detailed breakdown of the actions configured in your automation rules, including their execution order and settings.
Each row represents a single action within a rule, listed in the order it is attempted.
The following columns are available:
Project — the project where the automation rule is configured.
Index — the rule's index within the project.
Monitored language — the language monitored by the automation rule.
Action order — the action's position in the fallback chain. 1 - Try indicates the first action, while 2 - or and subsequent positions represent fallback actions.
Action — the translation method used by the action, such as Translation Memory, Lokalise AI, or Machine Translation (DeepL).
Action settings — the configuration applied to the action, such as clearing translation statuses or marking translations as unverified.
The first action of each rule (1 - Try) is highlighted in blue, making it easier to identify where a new rule begins.
You can also use this table as a reference when migrating from Automations to Workflows, as it provides an inventory of existing rules, monitored languages, and configured actions.
What automations delivered
The What automations delivered section shows how much translation work your automations have performed during the selected reporting period.
The following metrics are available:
Keys touched — the number of translation keys affected by automations during the selected period.
Translations performed — the number of segments translated by automation rules during the selected period, using Translation Memory, Machine Translation, Lokalise AI, or other automated actions.
Processed words — the number of words processed through automations during the selected period.
Pro AI words — the number of billable Pro AI words triggered by automation rules during the selected period. This metric is different from the number of words processed by Pro AI.
These metrics help you understand how much content your automations process and track the Pro AI usage associated with automation rules.
Share of Processed words from automations
The Share of Processed words from automations chart shows how your team's billable processed words are distributed across different delivery methods over time.
Each stacked bar represents 100% of billable processed words for a given period, divided into three categories:
Automations — words processed through automation rules.
Workflows — words processed through workflows.
Other — words processed through other delivery methods, such as the editor, API, or file imports.
Use the Time grouping filter to adjust the reporting intervals.
This chart helps you understand what share of your team's billable processed words is delivered through Automations and Workflows compared to other delivery methods.
Processed words from automations
The Processed words from automations chart shows the number of words processed by automation rules over time.
Use the Breakdown by filter to choose how the data is grouped:
Method — break down processed words by translation method, such as Standard AI/MT, Translation Memory, or Pro AI.
Project — compare the number of words processed by automations across different projects.
Target language — see how processed words are distributed across target languages.
The chart follows the selected reporting period and Time grouping filter.
Use this chart to identify which translation methods contribute the most to your automation activity, compare usage across projects, and track translation volumes for different target languages.
Share of Pro AI words from automations
The Share of Pro AI words from automations chart shows what percentage of your team's billable Pro AI words is triggered by automation rules compared to other sources over time.
Each stacked bar represents 100% of billable Pro AI words for a given period, divided into two categories:
Automations — billable Pro AI words triggered by automation rules.
Other — billable Pro AI words generated through other sources.
Free AI Suggestions are excluded from these calculations. Use the Time grouping filter to adjust the reporting intervals.
Pro AI words from automations
The Pro AI words from automations chart shows the number of billable Pro AI words triggered by automation rules over time.
Use the Breakdown by filter to choose how the data is grouped:
Method — displays all billable Pro AI words in a single Pro AI category (default).
Project — compares billable Pro AI usage across different projects.
Target language — shows how billable Pro AI words are distributed across target languages.
The chart follows the selected reporting period and Time grouping filter.
Use this chart to track billable Pro AI usage generated by automations and identify which projects or target languages contribute the most to that usage. This chart helps you understand how much of your team's billable Pro AI usage comes from automations and how that share changes over time.