{"id":13328,"date":"2026-04-14T19:15:00","date_gmt":"2026-04-14T19:15:00","guid":{"rendered":"https:\/\/www.mailgun.com\/blog\/gmail-permettant-changements-adresse\/"},"modified":"2026-04-15T03:19:22","modified_gmt":"2026-04-15T03:19:22","slug":"gmail-permettant-changements-adresse","status":"publish","type":"blog","link":"https:\/\/www.mailgun.com\/fr\/blog\/deliverability\/gmail-permettant-changements-adresse\/","title":{"rendered":"Gmail permet d\u00e9sormais aux utilisatrices de modifier leurs adresses email : Ce que cela signifie pour les exp\u00e9diteurs"},"content":{"rendered":"\n

Google recently announced that Gmail users in the US can now change their Google Account username, the part before @gmail.com<\/em>, once every 12 months, up to three times over the life of the account. Years of regretting a cringeworthy 2004 email address now finally have a resolution.<\/p>\n\n

For most users, it’s a simple quality-of-life win. For email marketers, it’s sparked some loud concern. Let’s look at what’s actually happening, sort through which worries hold up, and figure out what you should do about it.<\/p>\n\n

What actually changes<\/strong><\/h2>\n\n

When a user changes their Gmail username, the old address doesn’t disappear. Per Google’s own documentation: \u00ab\u00a0You’ll receive emails to both your old and new addresses.\u00a0\u00bb <\/strong>Both land in the same inbox. Users can see which address a message was sent to by checking the To field<\/strong>, and they can send from either. Their data, including messages, photos, and account history, is completely unaffected.<\/p>\n\n

This is much closer to \u00ab\u00a0one mailbox, multiple addresses\u00a0\u00bb than anything more disruptive. And honestly, many users already live this way. Apps like Apple Mail and Outlook routinely combine several accounts into one view, often without clearly showing which address a message was sent to. This Gmail change fits right into behavior that already exists.<\/p>\n\n

The concerns worth looking at<\/strong><\/h2>\n\n

Emails to the old address will go unseen<\/strong><\/h3>\n\n
    <\/ol>\n\n

    This worry comes from a misunderstanding of how delivery works here. Since both addresses route to the same inbox by default, engagement doesn’t automatically drop. Messages to the old address stop being seen only when users actively filter or block them, which Google offers as an option, not a default.<\/p>\n\n

    That kind of action is a meaningful signal. A user who filters out their old address has made a clear choice about what they want going forward. From a sender perspective, it looks the same as any other disengagement pattern. Whether someone filtered their old address, switched inboxes, or simply lost interest, the signal reads the same way. Watching engagement trends and responding to them is still the right move.<\/p>\n\n

    People will sign up twice and grab multiple discounts<\/h3>\n\n

    Some will. And when it happens, it’s more likely intentional than accidental.<\/p>\n\n

    Gmail has supported plus-aliasing for years, disposable addresses are easy to find, and creating a second account has never been hard. This feature makes that behavior a little more visible, but it doesn’t meaningfully expand it.<\/p>\n\n

    There are also natural limits built in. Users can only change their Gmail username a few times total. This isn’t an easy loophole so much as an occasional workaround from motivated users.<\/p>\n\n

    Acquisition models that are sensitive to this kind of behavior are worth reviewing on their own terms, separate from this Gmail update. And a subscriber who goes through the effort to sign up again and keeps engaging or buying can be read as a behavioral signal rather than a data quality problem.<\/p>\n\n

    We might end up messaging the same person twice<\/h3>\n\n

    This only happens when a user subscribes under both addresses.<\/p>\n\n

    In many cases, that’s intentional. In others, it might point to low brand recall or a very low-friction signup flow. Either way, this pattern already exists across email programs and isn’t new to Gmail’s update.<\/p>\n\n

    There’s some complaint risk around duplicate messages. But similar situations have existed for years through aliasing and multi-account setups without causing widespread problems. A spike in complaint rates is worth looking into. Outside of that, this is a manageable edge case, not a structural shift.<\/p>\n\n

    The opt-out and suppression gap<\/h3>\n\n

    This is one area where the change can surface a real issue, though it’s more nuanced than it first seems.<\/p>\n\n

    A subscriber who opts out using their new address will typically have that opt-out recorded against that address only. The original address may stay active as a separate record, even when the user expects the opt-out to cover everything.<\/p>\n\n

    Sometimes the separation is intentional. Many users already juggle multiple email identities. They might use different addresses for promotions, personal messages, or signups. Unsubscribing from one doesn’t always mean they want to stop hearing from you entirely.<\/p>\n\n

    The tricky part is that your systems can’t easily tell the difference between those two situations. It’s worth taking a closer look at how your suppression logic works and whether it lines up with both compliance requirements and what users would reasonably expect.<\/p>\n\n

    What should you do as a sender?<\/strong><\/h2>\n\n

    Most of the response here comes down to solid email fundamentals, with a few specific things worth revisiting.<\/p>\n\n

    Make it easy for subscribers to update their address<\/h3>\n\n

    A clear \u00ab\u00a0update your email preferences\u00a0\u00bb link and a simple preference center let users manage their relationship with your brand without having to unsubscribe.<\/p>\n\n

    Show subscribers which address you’re using<\/h3>\n\n

    A short note in your footer like \u00ab\u00a0This email was sent to [address]\u00a0\u00bb cuts down on confusion for users managing multiple inbox identities. It also gives them a clear path to update preferences or unsubscribe from a specific list.<\/p>\n\n

    Track Gmail engagement separately<\/h3>\n\n

    Changes in behavior are easier to spot when Gmail is its own segment. Shifts in engagement can then shape your re-engagement and sunsetting approach more precisely.<\/p>\n\n

    Refresh your re-engagement messaging<\/h3>\n\n

    Adding something like \u00ab\u00a0Recently changed your email alias? Update it here to stay connected\u00a0\u00bb keeps your outreach in step with how users are actually behaving.<\/p>\n\n

    Look at the full picture of engagement<\/h3>\n\n

    A subscriber who’s quiet in email but active on your site or in your product hasn’t walked away from your brand. Looking beyond the inbox gives you a more accurate read on where people actually stand.<\/p>\n\n

    Check your sending frequency<\/h3>\n\n

    Programs where duplicate subscriptions would noticeably change the numbers may already be sending at or near their limit.<\/p>\n\n

    Review your suppression logic<\/h3>\n\n

    Make sure opt-outs tied to one address are handled in a way that accounts for potential duplicates. Some users want a global opt-out. Others prefer more control. It’s worth knowing how your setup handles both.<\/p>\n\n

    The bottom line<\/strong><\/h2>\n\n

    Gmail’s username change feature is a genuinely useful update for users, and the questions it raised in the marketing community made sense.<\/p>\n\n

    A lot of the concern came from assumptions about how delivery and engagement work in this setup. In practice, the mechanics are pretty familiar. What’s left are existing challenges: engagement drift, suppression nuance, and the occasional duplicate subscription. None of these are new problems, but they’re all worth handling with care.<\/p>\n\n

    The questions were worth asking. The answers turn out to be more familiar, and a lot less dramatic, than the initial reaction suggested.<\/p>\n

    \r\n
    \r\n
    \r\n
    \r\n
    \r\n
    \r\n \r\n
    \r\n Please complete this required field. <\/div>\r\n <\/div>\r\n
    \r\n \r\n
    \r\n \r\n