Language Targeting allows you to collect, analyze, and report on social data across different languages, making it easier to run research in global markets.

By default, Social Reports had previously been optimized for English-language content, meaning queries entered in English primarily return English results. With Language Targeting, you can now control both the language of the data you collect and the language of the report you deliver.

This helps ensure your datasets better reflect the markets you’re researching, especially when working with international audiences.

When setting up a query, you can choose a Source Language.

This determines the language of the social posts and comments that Social Reports will collect. For example, selecting Japanese will prioritize posts written in Japanese.

When setting up a query, you can choose which language your final report will be delivered in. Reports (including summaries, narratives, and charts) are then generated in the chosen language.

After selecting your languages, you’ll see a “Preview Translation” option.

Using it isn’t required—your query will run as expected without it. However, if you’re familiar with the target language and would like to review or refine the translated query before it runs, you can use this option to do so.

Once your report is ready, you’ll notice a few new features:

Language toggle: A dropdown at the top of the report lets you switch between available languages. Your selected output language will be included, and an English version is always provided automatically—no extra setup needed.

Report title: The title updates to match the language you’re currently viewing. An English version is always maintained as well, so your reports list remains consistent and easy to navigate.

Translated content throughout: All report content—summaries, narratives, charts, in-text citations, and highlighted comments—appears in the selected language. Every section is fully translated.

Toggle to view original text: In several areas (such as highlighted comments and the translated query), you’ll see a toggle option that lets you switch back to the original language. For example, if comments were collected in French and you’re viewing the report in English, you can toggle to see the original post language.

Sources: Collected source posts remain in their original language (based on the language selected during comment collection).

When you export or share a report, it will be in whichever language you're currently viewing. If you're in the French view and click export, you'll get the French version. Switch to English first if you need the English export.

Most of the report content is fully translated, but some platform-level elements will still appear in English. This includes things like section headings (e.g., "Key Findings," "Key Trends"), navigation buttons, and shared Dig One interface components. This is because Language Targeting applies specifically to Social Reports content, not the broader Dig One platform.

Language Targeting is especially useful when:

Will old reports be affected?

No. Existing queries and reports are unchanged. Language Targeting only applies to new queries.

Which languages are supported?

English, Arabic, Bulgarian, Chinese (Traditional + Simplified), Croatian, Czech, Danish, Dutch, Finnish, French, German, Greek, Hindi, Hungarian, Indonesian, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Romanian, Russian, Serbian, Spanish, Swahili, Swedish, Tagalog, Thai, Turkish, Urdu, Vietnamese

Why are some parts of the report still in English?

Platform-wide UI elements like the share button and section headings are shared across Dig One and are not translated in this release. The actual report content, narratives, summaries, charts, is fully translated.

Is this the same as location targeting?

Not exactly. Social platforms don't give us reliable location data at the post level. Language is the best available proxy- posts in Japanese are very likely from Japanese-speaking markets.