How to Set Up Language-Specific Goals in Google Analytics 4

Why this matters

Knowing which language drives conversions helps you allocate budget to the most profitable locales. If you see that French visitors convert at twice the rate of English visitors, you can shift ad spend or localization effort toward French‑language pages. This improves return on investment for translation work and avoids spending on languages that do not generate revenue.

Language‑specific conversion data also reveals gaps in user experience. A high bounce rate in a particular language may indicate translation quality issues or mismatched offers. By isolating conversion metrics per language, you can test changes locally and measure impact without affecting other markets.

How it works

GA4 treats every user action as an event. To segment conversions by language, you add a custom parameter (e.g., language) to each event. The parameter value is the content language, such as en, fr, or de.

When the event reaches GA4, the platform stores the parameter value. You then create an event‑scoped custom dimension that maps to that parameter name. Once processed, the dimension appears as a column in reports.

Finally, you mark a relevant event (e.g., purchase) as a conversion. In explorations or standard reports, you filter or break down the conversion metric by the language dimension to see conversion counts and rates per language.

Text diagram of the data flow:

Event (e.g., purchase) -->
  + parameter: language=fr -->
GA4 ingests event -->
  Custom Dimension (event‑scoped) reads 'language' -->
  Dimension value available in reports -->
  Conversion event marked -->
  Report: conversion count filtered by language=fr

Prerequisites

You need edit access to the GA4 property. Your website or app must consistently send a language identifier with every event. If you use a translation tool such as SeaText, it may already push a language parameter into the data layer, which you can reuse.

Verify that the parameter name is the same across all tags (e.g., language) and that its value reflects the page content, not the browser language setting.

Step‑by‑step setup

1. Send a language parameter with each event

   In Google Tag Manager, create a variable that reads the language from the URL path, a cookie, or the data layer. Add this variable to all GA4 event tags as a parameter named language. For a WordPress site using SeaText, you can pull the value from the data layer where SeaText stores the detected language.

2. Create a custom dimension for language

   Go to GA4 Admin > Custom Definitions > Custom Dimensions. Click Create custom dimension. Set Scope to Event. Enter the exact parameter name you used (e.g., language). Name it something clear like "Content Language". Save.

3. Verify the dimension is receiving data

   Trigger a test event (e.g., a page view) in DebugView. Look for the custom dimension under the event parameters. It may take up to 24‑48 hours for the dimension to appear in standard reports, but DebugView shows it instantly.

4. Mark a conversion event

   In Admin > Events, locate the event you want to track as a conversion (e.g., purchase). Toggle the Mark as conversion switch. This makes GA4 count every occurrence of that event as a conversion.

5. Use the language dimension in reports

   Open an Exploration report. Add the Language dimension as a row and the Conversion metric as a value. You can also add conversion rate by dividing conversions by total events. Filter or break down by language to see performance per locale.

6. Validate the setup

   Perform a test conversion in a specific language (e.g., switch site to French and complete a purchase). Check Realtime or DebugView to confirm the language=fr parameter arrives. Then run a report filtered by French to see the conversion count.

Limitations and when this approach doesn't work

If some events lack the language parameter, they appear under (not set) and dilute your language‑specific data. This can happen on single‑page applications where navigation does not reload the page and the tag fails to re‑fire the parameter.

Subdomain‑based multilingual sites (e.g., fr.example.com) can still use this method, but you must ensure the parameter is sent on every subdomain. Missing the parameter on one subdomain creates gaps.

Cookie consent banners that block analytics tags until consent is given will prevent the language parameter from being sent for the initial event, causing the first hit to be missing language data.

GA4 free properties limit event‑scoped custom dimensions to 50. If you already use many custom dimensions, you may need to reuse an existing one or upgrade to a paid tier.

The built‑in GA4 language dimension reflects browser language, not the content language, so it cannot be used for this purpose.

Comparison with other methods

Alternative ways to isolate language performance include filtering by URL path (subdirectories), hostname (subdomains), or creating separate GA4 properties.

Subdirectory filtering: If you use URLs like example.com/en/ and example.com/fr/, you can create a custom dimension that extracts the language code from the page path. This avoids adding a parameter but relies on consistent URL structure and can be fragile if URLs change.

Subdomain filtering: With en.example.com and fr.example.com, you can filter by hostname. This works well when subdomains are strictly separated, but it requires maintaining multiple hostnames and may complicate cross‑domain tracking.

Separate properties: Creating a distinct GA4 property per language gives completely isolated data. However, it multiplies administrative effort, makes cross‑language comparisons harder, and splits your quota limits.

Custom dimension with language parameter: This method works regardless of URL structure, keeps all data in one property, and lets you combine language with other dimensions (e.g., device, campaign). The trade‑off is the need to reliably send the parameter on every event.

Choose the approach that matches your technical constraints. If you already have a translation service that pushes a language value (like SeaText), reusing that parameter is often the simplest.

FAQ