How to Translate Shopify Store Push Notifications and Web Push Campaigns for International Customers
Push notifications have a median open rate of 5–10% according to CleverTap and Insider benchmarks — roughly 5× higher than email. Send one in the wrong language and that advantage disappears instantly: a French subscriber in Lyon who receives "Flash Sale — 24 hours only!" in English is likely to disable notifications rather than convert.
Shopify push notifications translation is not a single step. It requires coordinating subscriber segmentation, translated copy, localized timing, and destination pages that match the language of the notification. This guide walks through each stage with specific, actionable steps.
Why Push Notification Translation Is Harder Than Email Translation
With email, you control rendering and can send HTML. With push notifications, the browser or OS controls how much text is displayed, and those limits are real but vary:
- Title: Chrome on Windows typically truncates at around 50 characters; Chrome on macOS shows closer to 65. Android Chrome allows up to ~80 characters in expanded view.
- Body: Chrome on desktop typically shows 120–130 characters in the notification tray. Mobile Chrome may show as few as 40–60 characters collapsed.
- Action buttons: Most browsers cap button labels at 10–15 characters.
The takeaway: test on actual devices for each locale. Do not write copy that depends on a trailing word that disappears on mobile. German compound nouns, Japanese kanji-dense phrases, and Arabic right-to-left rendering all behave differently under truncation — which is exactly why copy must be written for each language, not mechanically translated.
This challenge is similar to translating on-site messages; the guidance in How to Translate Shopify Pop-Ups, Banners and On-Site Notifications for International Customers covers the same character-discipline thinking for smaller UI elements.
Segmenting Your Push Subscribers by Language
Before you can send localized notifications, you need to know which subscribers speak which language. Web push apps do not automatically capture this — you have to build the signal deliberately.
Three Signals Worth Combining
The most reliable segmentation approach combines three data points inside Shopify Markets:
1. Browser language (the primary signal)
When a subscriber opts in, most web push platforms pass the browser's Accept-Language header. Tag subscribers with that language at opt-in time. In PushOwl, for example, subscriber tags can be set via custom attributes during the opt-in flow. In Pushbase and similar apps, you can use the subscriber's locale captured through the subscription prompt.
2. Geography (the confirmation signal)
Browser language alone is unreliable — a Spanish speaker in Germany may have a German-language browser. Cross-reference against the subscriber's country (available from IP at opt-in). A subscriber tagged lang:fr + country:FR is a confident French-language send. A subscriber tagged lang:fr + country:CA likely prefers French-Canadian copy with slightly different idiom.
3. Shopify Markets checkout language (the strongest signal) If a subscriber has already purchased, Shopify stores the language they checked out in. Export this from your order data, map it to your subscriber list by email, and re-tag accordingly. This overwrites browser language where there's a conflict — a customer who browsed in English but checked out in German almost certainly prefers German.
Implementation in Shopify Markets:
- In your Shopify admin, go to Settings → Markets and confirm you have a market per language region (e.g., "France," "DACH," "Japan").
- In your push app, create a subscriber segment per market using the tags built above.
- Create a separate campaign for each segment, using translated copy in that segment's language.
- Set the click-through URL to the market-specific storefront domain or path (e.g.,
/fr/orstore.com/de-de/).
This three-signal approach is more robust than geography alone and significantly reduces mis-sends that erode unsubscribe rates.
Writing Push Copy That Actually Works in Multiple Languages
The Before/After Method
The best test of a push translation is to ask: does it communicate urgency and specificity without the English original as a crutch?
English original:
Title: "Flash Sale — 50% off sitewide" Body: "24 hours only. Shop now before it ends."
French translation (direct):
Title: "Vente flash — 50% sur tout le site" Body: "24 heures seulement. Profitez-en avant la fin."
That works because French has similar idiom density. Now test a less forgiving pair:
German translation:
Title: "Flash-Sale — 50% auf alles" Body: "Nur 24 Stunden. Jetzt shoppen, solange es läuft."
The German title is 30 characters — well within truncation limits. But "Jetzt shoppen" (now shop) is a loan phrase that feels slightly foreign in German e-commerce. A native German copywriter would more likely write "Jetzt entdecken" (now discover) or "Gleich sichern" (secure it now). Machine translation catches the meaning; a glossary catches the brand voice.
Japanese translation:
Title: "フラッシュセール — 全品50%オフ" Body: "24時間限定。今すぐチェックしてください。"
Japanese kanji characters are wider than Latin characters, so the same character count truncates sooner visually. Test on Android Chrome specifically. Also note that "今すぐチェックしてください" (please check right now) is polite but slightly formal — consumer-facing Japanese often drops the ください for "今すぐチェック" to feel more direct.
The pattern across all three: machine translation gets you to 70–80% quality. A glossary of brand terms and tone-of-voice rules gets you to 90%+. Human review catches the final 10%.
Timing Localized Campaigns
The obvious advice — don't send at 2 AM local time — is obvious. What is less obvious is that optimal send times differ meaningfully by locale even within business hours.
CleverTap's 2023 push benchmark data shows that e-commerce push CTR peaks at different windows by region:
- Germany and France: Tuesday–Thursday, 10–11 AM local time
- Japan: Weekday evenings, 7–9 PM (after work commute)
- Mexico: Saturday midday, 12–2 PM
If you are running a seasonal or holiday campaign across multiple markets simultaneously — say, a Black Friday push — schedule each market segment as a separate send with a local-time offset rather than a single global blast. A push hitting French subscribers at 10 AM Paris time and German subscribers at 10 AM Berlin time (the same UTC offset) is easy. Japan requires a separate scheduled send.
Most push apps support scheduled sends per segment. Use that feature for every localized campaign.
Translating the Destination: The Overlooked Step
A localized push notification that clicks through to an English-language product page destroys the experience and the conversion. The destination page must:
- Be in the same language as the notification
- Reflect any promotional pricing or messaging referenced in the notification
- Load the correct Shopify Markets storefront version
If you are running a promotion that involves translated discount banners or offer copy on the landing page, the guide to translating Shopify discount codes, banners and promotional content covers how to keep those consistent. For paid traffic destinations specifically, translating Shopify landing pages for international campaigns addresses URL structure and hreflang alignment.
Product pages need fully translated titles, descriptions, and SEO meta fields — not just the notification copy. If you are scaling translations across hundreds of products, bulk-translating Shopify products is the place to start.
Measuring Localized Push Performance
Metrics to Track Per Locale
Track these separately for each language segment, not in aggregate:
- Opt-in rate by locale: If French subscribers opt in at 8% and German at 3%, that is a prompt-language or timing problem, not a product problem.
- CTR by locale: Healthy web push CTR benchmarks run 5–10% for e-commerce (CleverTap, Insider). Below 3% in a specific locale typically points to mistranslated copy or mis-timed sends.
- Conversion rate from push by locale: A high CTR with low conversion usually means the destination page is not localized.
### Diagnosing Drop-Off
If CTR is acceptable but conversion falls short, audit the full path: notification → landing page → checkout. Translated checkout extensions and post-purchase pages are a common gap. So are email notification flows triggered after a push-driven cart addition — if those emails arrive in English, you have broken the localized experience mid-funnel.
Where StoreLingo Fits
StoreLingo translates the Shopify storefront content that push notifications point to — product pages, collection pages, landing pages, and SEO meta fields — using AI with a glossary to keep brand terms consistent across languages. It does not send push notifications itself, but it ensures the destination experience is fully translated before you drive traffic to it. If your push campaigns are ready but your store pages are still in English, that is the gap to close first.
Add StoreLingo on the Shopify App Store →
FAQ
Can I translate push notifications directly inside Shopify? Shopify does not have a native push notification feature — web push is handled by third-party apps like PushOwl or Pushbase. Translation of the notification copy must be done within those apps, using separate campaigns per language segment, while StoreLingo handles the translation of the store pages subscribers land on.
Do I need separate opt-in prompts per language? Yes, ideally. An opt-in prompt in English shown to a French-speaking visitor reduces your opt-in rate and immediately creates a language mismatch in your subscriber data. Configure your push app to show the opt-in prompt in the visitor's detected browser language, and tag the subscriber with that language at the point of capture.
Does GDPR affect how I can segment push subscribers by language in Europe? GDPR requires that push consent be specific, freely given, and informed. Segmenting existing subscribers by browser language or geography for the purpose of sending them more relevant content in their own language is generally considered compatible with the original consent — it improves the service rather than extending its scope. However, you should review your consent language with a legal adviser to confirm it covers behavioral segmentation in your specific markets.
Choose from 47 languages
StoreLingo translates products, collections, pages and articles with AI — review and approve by default. On paid plans from Starter, auto-translate is off by default and publishes new or updated products automatically. Keep your brand terms consistent.
Add to Shopify →