Email Deliverability in India: Why Gmail Inboxes Recipients Here Differently

Most email deliverability guidance is written from a US or European vantage point, and it is mostly correct everywhere: authenticate your domain, keep your list clean, do not mail people who did not ask. Those fundamentals do not change at a border.

What does change is everything layered on top. The advice assumes a provider mix, a device, a language, and a set of consent norms — and for an Indian audience, three of those four assumptions are different enough to matter. The result is a familiar pattern: a sender does everything the standard guide says, watches their metrics stay stubbornly mediocre, and cannot work out which rule they broke. Usually none. They applied rules calibrated for a different audience.

This is what is actually different, and what to do about it.

What Actually Differs

Four things, in rough order of how much they affect your results:

The fundamentals are unchanged. What changes is which of them carry the most weight.

The Provider Mix and What It Implies

Gmail’s share of Indian consumer email is high enough that, for practical purposes, you are optimising for one mailbox provider. Android’s dominance and Gmail’s default status on those devices reinforce each other.

That concentration is genuinely useful, because it makes your job more specific. Rather than balancing the quirks of four or five providers, you are largely satisfying one — and Google publishes what it wants:

• Authenticate with SPF and DKIM, and publish a DMARC record.
• Keep your reported spam rate low. Google’s guidance asks high-volume senders to stay under 0.3% and treats 0.1% as the level to aim for.
• Support one-click unsubscribe via the List-Unsubscribe header, and honour it quickly.
• Send from a domain with valid forward and reverse DNS.
• Keep your sending consistent rather than spiky.

Two secondary effects follow from the concentration.

Gmail’s tab placement matters more than in mixed-provider markets. Promotions is not the spam folder and is often the correct destination for marketing mail — recipients who shop go there deliberately. But if your transactional mail lands there, that is a real problem. The reliable separator is not subject-line wording; it is sending transactional messages from a different subdomain than marketing, so the two build separate reputations.

The long tail is old. Legacy consumer domains from India’s first internet wave persist in lists inherited from CRMs or bought years ago. These addresses are disproportionately abandoned, and hitting a cluster of them is a fast route to a bounce-rate problem. The list hygiene guide covers the cleaning cadence; the specific advice for an Indian list is to be more suspicious than usual of anything older than about a year.

Mobile-First Is Not a Slogan Here

Assume your email is being opened on a phone, on a mid-range Android device, possibly on a metered or congested connection. This is where most Western-authored template advice quietly fails.

What follows practically:

The preview pane is your subject line. On the Gmail Android app, a recipient sees the sender name, a truncated subject, and a short snippet. That is the entire basis for the open decision. Front-load the subject — the first 30 to 35 characters do nearly all the work.

Set the preheader deliberately. If you do not, the client pulls the first text in the body, which is frequently “View this email in your browser” or an alt-text fragment. That is a wasted line of prime real estate on every single send.

Single column, always. Multi-column layouts collapse unpredictably across Android mail clients. A single column that reflows is not a compromise for mobile; it is the correct design for this audience.

Watch total image weight. A design that loads instantly on office wifi can be sluggish on a congested mobile connection. More importantly, images are frequently not loaded at all by default — so an email whose message lives entirely inside a hero image communicates nothing.

Tap targets, not click targets. Buttons need real padding. A text link in a paragraph is hard to hit accurately on a phone and gets missed rather than tapped.

Language, Encoding, and the Subject Line

For B2B email in India, English is the safe default and rarely the wrong choice. For consumer email, the picture is more varied — and the mechanics of getting non-Latin scripts right are worth knowing before you attempt it.

Encoding is the first thing to get right. Devanagari, Tamil, Bengali, and every other Indic script require UTF-8, correctly declared. Get this wrong and recipients see replacement characters — a failure that looks, to a recipient, exactly like a phishing attempt.

Test rendering on real Android devices, not just a desktop client. Font fallback for Indic scripts varies by device and OS version. Conjunct characters and matras are where rendering breaks first, and a desktop preview will not show you the problem.

Be careful with transliteration. Hindi written in Latin script (“Aapka order confirm ho gaya hai”) reads naturally to some audiences and awkwardly to others, and it varies by region and age. It is not a safe default — it is a choice to validate against your actual list.

Emoji in subject lines render inconsistently across older Android builds. They are not forbidden, but they should never carry meaning the subject line needs — if the emoji fails to render, the line must still make sense.

Consent Expectations and the DPDP Act

India’s Digital Personal Data Protection Act, 2023 establishes a consent-first framework for processing personal data — and an email address is personal data. The operative concepts for an email sender:

• Consent must be free, specific, informed, and unambiguous, given by a clear affirmative action. A pre-ticked box is not consent.
• Notice must accompany the request — what you are collecting, and what for.
• Consent must be as easy to withdraw as it was to give. For email, that is your unsubscribe path, and it means a working one-click unsubscribe rather than a login-and-hunt flow.
• Purpose limitation applies. An address collected for order updates was not given to you for a weekly marketing newsletter.

The practical translation is unglamorous and almost entirely overlaps with what good deliverability requires anyway:

• Use double opt-in for marketing lists. It is the cleanest evidence of affirmative consent and it improves your metrics independently.
• Record consent properly — timestamp, source, and what the person was actually shown.
• Keep transactional and marketing consent separate. Order confirmations and a promotional newsletter are different purposes.
• Make unsubscribing genuinely one click.

That last point has a deliverability dimension that outweighs the compliance one. If unsubscribing is hard, recipients press the spam button instead — and Gmail weighs a spam complaint far more heavily than an unsubscribe. Complaints are the metric most likely to cause an actual sending problem, and a hard-to-find unsubscribe link is the most reliable way to generate them.

Send Time and the Indian Working Week

Mechanically simple, easy to get wrong:

Set IST correctly, and account for a single time zone. India spans one zone (UTC+5:30), which removes the staggering problem US senders deal with. The half-hour offset is where scheduling bugs hide — verify the actual send time rather than trusting the scheduler.

Saturday is a working day for many organisations. The Western Monday-to-Friday B2B assumption does not hold uniformly.

Festival calendars move, and they matter commercially. Diwali, Holi, Eid, Pongal, Onam and regional festivals shift year to year against the Gregorian calendar. Two consequences: the commercial peak around Diwali is genuinely the year’s most competitive inbox period, and a promotional send landing on a major festival day performs differently from an ordinary Tuesday. Neither is automatically bad — but both should be a decision rather than an accident.

Test rather than inherit. Published “best time to send” data is overwhelmingly derived from Western sending patterns. Your own opens by hour, from your own list, beat any benchmark.

Infrastructure Choices That Matter

A few setup decisions have outsized effect for this audience.

Separate your sending domains by type. Transactional mail from mail.yourdomain.com and marketing from news.yourdomain.com build independent reputations. When a promotional campaign underperforms, your password resets and order confirmations are unaffected. Given how much of your audience sits behind one provider, that isolation is worth more here than in a mixed market.

Authenticate before volume, not after. SPF and DKIM should be verified before your first real campaign. Brixus365 generates both records when you add a domain — an SPF TXT record with include:spf.brixus365.com, and a DKIM CNAME at bx1._domainkey.yourdomain.com — and verifies them for you. Publish your own DMARC record on top; the DMARC rollout guide covers reaching enforcement without breaking anything.

Warm up gradually. A new domain sending a large campaign on day one looks exactly like a compromised domain. Start small, send to your most engaged recipients first, and build volume over weeks.

Watch bounce and complaint rates from the first send, not the first problem. The thresholds that matter are low: a complaint rate above 0.1% is a warning sign well before it becomes a sending restriction. Catching a bad import on send one is a different problem from discovering it after four campaigns.

If you are setting this up now, Brixus365 handles domain authentication, per-campaign bounce and complaint tracking, and one-click unsubscribe headers by default — start free, 9,000 emails a month, no card. The email setup guide walks through the DNS side.

Frequently Asked Questions