Push Notification Best Practices for Indian Websites

A push notification playbook tuned for Mumbai is not the same as one tuned for Manhattan. Send times shift, copy length shifts, the device mix is overwhelmingly Android, and the most engaging promotion of the year is Diwali — not Black Friday. Here is what works specifically for Indian web push audiences.

The device reality

India is roughly 95% Android by share of web traffic, with Chrome dominating browser share. Practically, that means:

• Full web push coverage — every modern Android Chrome user can subscribe with one tap. No app required.
• Truncation is harsher — Android notification rows are narrow, especially on budget devices. Aim for titles under 45 characters and bodies under 90.
• Slow networks matter — heavy images make pushes slow to render on 2G/3G slices of traffic. Test on a throttled connection; many users still see your image before your text.
• iOS is a bonus — Safari iOS push works only for Home Screen sites. Treat it as a delighter for power users, not your base case.

Send-time windows that work

Engagement curves across Indian campaigns we see cluster around three peaks. Translate these into per-campaign rules:

• 8–10 am — morning commute and tea-time scroll. Good for news, deal-of-the-day, content sites.
• 1–2 pm — lunch break, especially in Tier-1 office hubs. Good for food, quick-commerce, transactional follow-ups.
• 7–10 pm — prime engagement window across geographies. Highest CTR for promotional and editorial pushes.

And the rule almost no one breaks twice: no sends between 10:30 pm and 8 am. One mistimed 2 am promo costs you subscribers permanently because Android shows it as a banner the moment they unlock their phone in the morning.

Language and tone

English is fine — until it is not

English-medium copy works for most metro and Tier-1 audiences. But for FMCG, regional news, education, and fintech reaching beyond, regional language pushes lift CTR by 30–60% in our customer data.

You do not need to translate everything. Translate the first three words and the CTA. The middle of the body can stay English.

Title: नया ऑर्डर मिला!
Body: Rahul, your Daraz cart still has the OnePlus Buds — checkout in 30 seconds.

Personalisation that lands

• City + weather — "Rain in Pune? Get your umbrella delivered today" outperforms generic by 2-3x in delivery apps.
• Cricket — match-day promotions converted exceptionally for food, sportswear, and OTT during the last two IPL seasons. Schedule pushes around innings breaks, not after the match ends.
• Festival calendar — Raksha Bandhan, Onam, Karva Chauth, Pongal, Diwali, Christmas, Republic Day. Plan a year ahead; queue the campaigns in a single sprint each quarter.

Frequency caps and quiet hours

Indian users are notification-sensitive — most Android phones display tens of app notifications a day. A single noisy web push channel earns a fast Block.

• Cap promos at 3-4/week for most brands, 7/week max for news.
• Always enforce quiet hours at the platform level so a campaign mistake cannot override them.
• Frequency capping per-user beats per-campaign; if someone got 2 pushes today, the third one should not fire even if the segmentation matches.

Opt-in mechanics tuned for India

Default opt-in rates on web push are 5–15% globally. In India we see consistently higher acceptance — often 12-20% — when soft prompts are localized and value-led.

• Soft prompt with value — "Pehle pata chal jaaye new drops ka? Allow करें" outperforms "Get notifications" on every brand we have tested.
• Delay the prompt — wait until second page view, 30+ seconds on first page, or post-cart-add. Never first paint.
• Phone-number prompt later — if you want WhatsApp opt-in too, ask after the first conversion event, not on prompt #1. Stacking permissions backfires.

Compliance: DPDP and consent

The Digital Personal Data Protection Act applies to push subscribers too — they are personal data. Ship these basics:

• A linked privacy policy listing push notifications as a data category.
• A preference center (one-click pause and unsubscribe) reachable from your footer.
• Honour withdrawal — when a user revokes, drop the subscription record server-side, not just locally.
• Retention default of 18-24 months of inactivity, then auto-cleanup.

What to skip

• Generic morning blasts — "Good morning, check our app!" earns Blocks. Reserve mornings for transactional and triggered.
• Aggressive fake urgency — "Last chance" 4x a week trains users to disbelieve you.
• Image-heavy pushes on every send — beautiful, but data-cost-sensitive users mute channels they perceive as bandwidth-eaters.

Frequency caps, quiet hours, regional templates, UTM auto-append, and DPDP-friendly preference centers are built into every ReachBell project including the free tier. Spin up a free project, add the snippet to your site, and ship your first India-tuned push this week.