spec sheet · stores & files

Google Play and Transglot, publish store copy in more languages.

Add your Google Play service account key, select your app, and map its languages in project settings. Sync listing copy, review translations, and publish the mapped target-language fields.

Import and publish translations

Direction: Import and publish translations
Plan: Starter and up
Scope: one app listing, per Play language
Authentication: a Google Play service account JSON key
Get started: Connect from your project’s CMS settings.

Create your project Setup

stores & files

the workflow

Connect your content. Review every language.

Connect once, choose your content and languages, then translate and review in the same project. The steps below show how it works in your tool.

Connect Google Play
In the project’s CMS settings, choose Google Play and provide a Google Play service account JSON key.
connect
Choose the content and locale mapping
Select the app and locale mapping. The connector reads one app listing, per Play language.
map
Sync and review the translations
Start Sync from CMS to bring the selected source into your project. Translate and review the resulting keys alongside the rest of your project content.
review
Publish to Google Play
Use Publish to CMS to send the translated values to the mapped target locales. Check the publish result in the project’s CMS settings.
deliver

Publish translated values back to the target locales you map in Google Play.

what moves

What you can translate and deliver.

Your whole Play listing as one entry: title, short description and full description per language. Every change happens inside an edit transaction that is committed at the end, and any error abandons the edit so nothing dangling is left on your account.

What you can translate and deliver.
Surface	What to expect
Source and scope	one app listing, per Play language
Translated output	Publish translated values back to the target locales you map in Google Play.
Keep in mind	This connector localizes store-listing copy. It does not translate the strings inside your app binary or submit a new app build.

get connected

A few steps to your first connection.

Follow your tool’s setup below: add the connection, choose what to sync, and try it with a small set of content. Your team can keep working in the tools they already use.

What you need

a Google Play service account JSON key.

A Transglot project with its source and target locales configured.
Save credentials in the connection settings so your team can work without copying secrets between files.
Hosted API access requires a paid Transglot plan. AI translation uses your workspace’s word allowance.

Create your project

Create a Transglot project and configure its source and target locales.
In the project’s CMS settings, choose Google Play and provide a Google Play service account JSON key.
Select the app and map its store locales to the project locales. Run Sync from CMS to import the listing copy.
Review the translations, then use Publish to CMS to write only the mapped target-locale listing fields.

same project, more possibilities