Gmail’s new address change feature: What email marketers actually need to know

Google has quietly rolled out one of the most significant changes to Gmail in two decades: users can now change the username portion of their @gmail.com address, the part before the @, without creating a new account. For anyone managing email programmes, the natural question is whether this introduces new deliverability or list health risks. The short answer is: not immediately, and here’s why.

The mechanics in brief

When a user changes their email address, the old address does not disappear. Instead, the system automatically converts the previous address into an alias. That alias continues to receive mail indefinitely. From a sending perspective, an email addressed to the old address lands in the same inbox as one addressed to the new address, same account, same user, same engagement signals.

The feature carries a frequency limit: once a user creates a new Gmail address, they cannot create another for the following 12 months. Documentation also describes a lifetime cap of up to three changes per account. This isn’t something subscribers will be cycling through regularly.

The rollout is gradual. Note that accounts managed by schools, workplaces, or organisations generally cannot change their addresses without administrator approval, so this affects personal @gmail.com accounts only, not Google Workspace domains.

The deliverability picture

The alias architecture is the key detail here. Because the old address remains active and points to the same inbox, mail sent to addresses already on your list will continue to deliver, open, and click exactly as before. There is no bounce risk, no sudden engagement drop, and no change to how Gmail’s filters or reputation systems process your mail. Your existing sending infrastructure and list data remain valid.

This is fundamentally different from the old behaviour, where a user wanting a new address had to abandon their account entirely, which did create real problems: hard bounces, lost engagement history, and the gradual decay of affected segments. This new feature avoids all of that.

Where there is a genuine consideration: Duplicate records and promo exploitation

The one scenario worth building into your thinking is re-registration. If a subscriber changes to a new Gmail address and then signs up to your programme again using that new address, your ESP will create a net-new record carrying none of the history attached to the old one, no engagement data, no suppression flags, no preference selections, no unsubscribe status.

The more pointed risk for many programmes is promotional exploitation. A subscriber who has claimed a sign-up offer on their old address can re-register with their new one and claim it again. Your system has no way of knowing it’s the same person. This is worth reviewing if your acquisition flows carry meaningful incentives.

This isn’t entirely new territory. Gmail’s tolerance for dots, plus tags, and other address variations has been exploited for years. sarah.jones@gmail.com, sarahjones@gmail.com, and sarahjones+offer@gmail.com all route to the same inbox, and many marketers have built normalisation logic to collapse those variants back to a single root address before applying suppression or offer eligibility checks. A genuine new @gmail.com username breaks that approach entirely. There is no algorithmic way to identify that sarahjones@gmail.com and sarah.jones93@gmail.com belong to the same person; the link only exists inside Google’s infrastructure.

That said, the 12-month cooldown and three-change lifetime cap do constrain the scale of abuse compared to the essentially unlimited dot and plus variations. It’s a more convincing alias per use, but a much lower-volume one.

Suppression list coverage remains the practical takeaway. If compliance or offer integrity is a concern, CRM-level matching on name, phone number, or other identifiers is your most reliable safeguard; email address alone is no longer sufficient as a unique customer identifier for these purposes.

A note on sign in with Google

For subscribers who originally connected to your platform via Sign in with Google, the picture is actually more stable than you might expect. According to Google’s own documentation, after a username change, Google continues to pass the old address to third-party apps by default. Your ESP or CRM will keep receiving the old address through that OAuth connection; nothing updates silently on your side.

The new address only surfaces in a third-party app if the user manually updates it in their account settings, which most people won’t proactively do. In practice, this means Sign in with Google connections are largely unaffected by an address change, and represent no new identity resolution risk beyond what already exists.

The bottom line

Gmail’s address change feature is good news for consumers, and largely a non-event for email marketers in the short term. The alias mechanic preserves continuity, your sends reach the same inboxes, your engagement data stays intact, and your deliverability isn’t affected.

The area to watch is acquisition hygiene and suppression coverage as the feature becomes more widely used. Programmes that rely on an email address as the sole customer identifier will have the most exposure. If that’s you, it’s a reasonable prompt to review how your stack handles duplicate contacts and whether your suppression logic extends beyond address-level matching.

For now: monitor, don’t panic, and make sure your list hygiene fundamentals are in good shape.