Skip to main content
TextSetu gives you two complementary views into the state of your localization: analytics (where do things stand?) and activity logs (what happened, and who did it?).

​
Project dashboard / analytics

Each project’s Dashboard turns the raw translation data into a picture of progress. It includes:
  • Overview cards — headline numbers: total keys, languages, overall completion, and how many values are outdated. Each card is clickable — e.g. clicking Outdated opens the Translations grid pre-filtered to outdated values.
  • Approval status — three clickable cards (Approved / Pending review / Draft). Clicking one opens the Translations grid filtered to that status. These cards appear only when the approval workflow is on for the project.
  • Language completion — a card per language with a progress bar showing how far each target language is from done, so you can see which locales lag.
Use the dashboard to answer questions like “Can we ship French this week?” or “Which language needs more translators?” — and click straight through to the exact set of keys that need work.

​
Activity logs

Activity logs are the audit trail. They record actions over time at several levels:
  • Organization activity — org-wide events (members invited, projects created, settings changed).
  • Project activity — keys added/edited, values changed, approvals, imports, merges.
  • Glossary activity — term changes.
  • Translation memory activity — entry changes.
Each entry captures what happened, who did it, and when — giving you accountability and a way to reconstruct exactly how the current state came to be. Timestamps read as relative time for recent events (“5 minutes ago”, “3 hours ago”) and switch to the exact date and time once an event is a day or more old.

​
How analytics and history relate

  • Analytics = the aggregate, current snapshot (counts, charts, completion).
  • Activity logs = the chronological stream of actions across an object.
  • History = the change record for a single value (or glossary term / TM entry), with rollback.
Together they answer “how complete are we?”, “what’s been happening?”, and “what exactly changed on this string?”.
Related: History & Rollback · Approval Workflow