Push notifications are higher-leverage in Japan than in many markets — JP users tolerate higher notification volume if the writing is relevant — and lower-leverage if the writing reads as translated. This article covers what works.
For broader localization context, see the complete guide to Japanese app localization.
What Makes JP Pushes Different
Three things that shape strategy:
1. JP users tolerate more notifications than US users for the same app, if the content is relevant. The threshold for muting an app is higher.
2. JP users mute aggressively when content isn't relevant. A push that says nothing useful gets the app muted, often forever.
3. Tone calibration matters more. A push that's too casual reads as over-familiar; too formal reads as cold. The right register depends on the app and the user.
The combination: more volume is fine, but every push has to earn its place.
The Push Notification Format
iOS and Android push notifications have:
- Title: ~30–40 characters visible.
- Body: ~50–80 characters visible (longer expanded).
- Optional badge, sound, and rich attachment.
For Japanese, the visible character counts are similar (Japanese characters take similar pixel width to wide Latin characters at notification font size).
Push Copy Patterns
Pattern 1: Notification + question
Title: 今日の食事、記録しましたか？ Body: あと2回の記録で、連続記録10日達成です。
The title asks; the body provides the motivation.
Pattern 2: Status update + action
Title: 新着メッセージ：山田さん Body: 「明日の打ち合わせの件で…」
Pure status notification. The user opens to read more.
Pattern 3: Achievement / celebration
Title: 🎉 連続記録30日達成！ Body: 素晴らしいペースです。引き続き頑張りましょう。
Light celebration. Don't overdo emojis or hyperbole.
Pattern 4: Soft reminder
Title: そろそろ休憩しませんか？ Body: 集中時間が90分を超えました。少し休んで、また再開しましょう。
A wellness or productivity nudge. Conversational tone, gentle.
Pattern 5: Feature awareness (use sparingly)
Title: 新機能：レシートの自動読み取り Body: カメラで撮るだけで、家計簿に自動反映されます。
Time-bound, infrequent. Not for repeat use.
Tone Calibration
The four registers from keigo in app copy apply to pushes too. A few examples of the same notification in different registers:
Polite-neutral (default)
今日の食事を記録してみましょう。記録すると、月の摂取カロリーがグラフでわかります。
Honorific (finance / formal)
ご利用明細をお知らせします。本日のお支払い：1,200円
Casual (social)
ねえ、今日のごはん記録した？ 続けてる人、すでに10日目だよ！
Plain (productivity)
タスクが期限切れです 「企画書のレビュー」 — 期限：今日
Same notification surface, four valid versions. Match to your app's overall voice.
Avoid
Generic motivational copy
❌ 「あなたならできる！」 ❌ 「がんばって！」
These read as patronizing without context. JP users don't want to be cheered on by an app that doesn't know what it's doing.
Vague urgency
❌ 「重要：アプリを開いてください」 ❌ 「すぐにご確認ください」
If the user can't tell what's urgent, the urgency reads as manipulation. Either be specific or don't claim urgency.
English idiom carryover
❌ 「あなたのストリークがリスクにあります」 ✅ 「連続記録が途切れそうです」
Direct translation of "your streak is at risk" sounds wrong. Native phrasing names the consequence directly.
Overuse of 「あなた」
❌ 「あなたのアカウントに新しい通知があります」 ✅ 「新しい通知があります」
Push notification copy is short; pronouns waste characters and feel translated.
Foreign emoji conventions
- 🥳 / 🎉 — fine, used the same.
- 👇 ("look down") — used differently in JP; can read as commanding.
- 🚨 / ⚠️ — read as alarmist if the content isn't actually urgent.
Use emoji sparingly. JP push notifications tend to be more text-led than emoji-led.
Timing and Frequency
Time-of-day patterns
JP users have predictable engagement windows:
- Morning commute (7:30–9:00): high engagement, especially on commuter trains.
- Lunch break (12:00–13:00): high engagement.
- Evening commute (18:00–19:30): high engagement.
- Late evening (21:00–23:00): medium engagement, especially for content/lifestyle apps.
Mid-morning and mid-afternoon (10:00–11:30, 14:00–17:00) are working hours; engagement is lower for non-work apps.
Don't ping after 22:00 by default
Late-night notifications (23:00+) are tolerated for messaging apps but generally read as inconsiderate for other categories. Default to a 22:00 cutoff for non-essential pushes.
Don't ping before 7:00
Same logic. Morning notifications before commute time are intrusive.
Frequency
Reasonable frequency by category (rough guidelines):
| Category | Daily | Weekly |
|---|---|---|
| Messaging | Per-message | — |
| Social | 1–3 | — |
| News | 2–5 | — |
| E-commerce | 0–1 | 3–7 |
| Productivity / Habit | 1–2 | — |
| Finance | 0–1 | — |
| Health / Wellness | 1–2 | — |
| Game | 1–2 | — |
Above these thresholds, mute rates rise sharply.
Personalization
JP users respond well to personalized notifications when the personalization is meaningful. "Hi {name}!" feels generic; "今日の支出は予算の80%です" feels useful.
Personalization that works:
- User's progress against a personal goal.
- Content tailored to their stated interests.
- Time-of-day aware ("おはようございます" before 10am).
- Recent-activity-aware ("先週は3回記録しましたね").
Personalization that doesn't:
- Just inserting their name.
- Generic location ("〇〇市の今日の天気" if the user lives somewhere else).
- Forced friendliness.
A Notification Volume Budget
For a habit-tracker or similar engagement app, a workable weekly notification budget per user:
- 5–7 daily reminders (one per habit per day).
- 1 weekly summary push (Sunday evening).
- 1 occasional achievement push (when triggered).
- 0–1 feature/marketing push per month.
Total: 35–50 pushes per week. JP users tolerate this if every push is useful. They mute fast if even 20% are noise.
Quiet Hours and User Control
Default to:
- Configurable quiet hours.
- Notification category settings (Daily reminders / Achievements / News / Marketing) so users can mute selectively.
- An easy in-app "pause notifications for X days" option.
JP users use these controls more than US users. Making them visible is trust-building.
Localized vs. Global Notification Tools
If you use a marketing automation tool (Braze, Iterable, OneSignal, CleverTap), the platform is multilingual but the content is yours.
Common failure: a campaign set up in English with English copy is sent globally; JP users get an English push. Set up:
- Locale targeting on every campaign.
- JP-language variants for every recurring campaign.
- A QA review where someone reads every JP push before scheduling.
- A monthly review where you read the JP pushes you've been sending.
Your monthly review will catch the pushes that read as translated. Iterate them.
Measuring What Works
For each push, track:
- Delivery rate (depends on token validity).
- Open rate (push → app launch).
- Conversion rate (push → intended action).
- Mute rate within 7 days of receiving the push.
A high mute rate indicates the push wasn't worth sending — even if open rate looks fine. Optimize for the mute rate, not just the open rate.
JP open rates for well-targeted pushes typically run 8–15% for non-time-sensitive content, 30–50%+ for time-sensitive (e.g., a friend posted in chat). Compare to your category baseline.
A Self-Check Before Launching a Push Campaign
- Title and body are in Japanese, written by a native (not auto-translated).
- Copy fits the app's brand voice register.
- No 「あなた」 / 「あなたの」 unless intentional.
- No untranslated English idioms.
- Time of day is appropriate (not before 7am or after 22:00 for non-messaging).
- Frequency fits the per-category budget.
- Users have a way to mute this category if they want.
- Campaign has a measurable success metric (open, conversion, retention).
- You've read the push aloud and it sounds like a person.
Where to Go Next
- Japanese UX Writing: Microcopy That Feels Native
- Keigo in Apps: When to Use Polite, Plain, or Casual Japanese
- Mobile UI Conventions Japanese Users Expect
- How to Make App Copy Sound Native in Japanese
We write Japanese push notification copy for marketing automation campaigns and one-off launches. Contact us for a push copy engagement.