Primary email changes triggers an "Added to segment" event

[TMathew]

I’m trying to determine the best way to handle what appears to be a broader issue with how HubSpot handles active segment membership when a contact’s primary email address changes.

When an existing contact’s primary email address changes, HubSpot Support has confirmed that HubSpot reevaluates that contact’s segment and workflow eligibility. In our case, the contact already belonged to numerous active segments before the email change and continued to meet exactly the same criteria afterward.

However, HubSpot treated the reevaluation as though the contact had just been added to those segments. Most importantly, the contact’s “Added to segment” date changed to the time of the email update.

That creates two broader problems:

1. “Added to segment” is not necessarily the date the contact actually joined the segment.

It appears that this date can be reset simply because the contact’s primary email address changes. The underlying contact record hasn’t changed and the contact hasn’t stopped qualifying for the segment and then requalified. Only the email associated with the contact has changed.

That makes “Added to segment” unreliable as a representation of when the contact actually became a member of the segment. It seems to be influenced by changes to the contact’s email identity rather than solely by actual changes in segment membership.

2. Segment-based workflows can unexpectedly trigger from an email-address change.

This is potentially the larger concern for us.

We have numerous workflows where enrollment is based on a contact joining or being a member of a particular segment. If changing a contact’s primary email causes HubSpot to effectively treat that contact as newly added to existing segments, then workflows can trigger even though nothing relevant to the purpose of the workflow actually happened.

We have active segments that represent everyone currently subscribed to a particular email subscription. When someone becomes subscribed, we may want to trigger a welcome workflow. The desired behavior is:

• Existing subscriber + primary email changes → remains in segment, does NOT trigger “joined segment” automation
• New subscriber → joins segment and triggers automation
• Former subscriber who resubscribes → rejoins segment and triggers automation

HubSpot Support suggested adding date criteria to prevent older activity from triggering enrollment, but that doesn’t really solve the underlying issue. For subscription segments, for example, someone could have subscribed years ago, unsubscribed along the way, and then resubscribed. We legitimately want that person to rejoin the segment and potentially trigger the workflow again but attempting to exclude by date would prevent that.

More importantly, adding date filters doesn’t address the broader problem that an mere primary-email change can apparently create a new “Added to segment” event and consequently trigger any automation that relies on segment membership.

Anyone else experienced this? Is there a recommended way to build workflows around genuine segment-entry events without primary-email changes causing unintended enrollment?

[dylan123]

Hi there!

I agree that relying solely on segment membership for subscription-related workflows can create unexpected enrollment behavior.

One approach worth exploring is using a subscription-related event as the enrollment trigger, with segment membership as an additional filter.

This would allow the workflow to respond to the relevant subscription event while checking whether the contact meets your segment criteria.

There are a couple of things to keep in mind:

• Timing: Additional enrollment filters are evaluated when the event occurs. If the contact joins the segment afterward, that original event won’t automatically trigger enrollment.

• Re-enrollment: If you want resubscribers to enter the workflow again, check whether your chosen trigger supports repeat enrollment and configure it accordingly.

• Subscription changes: Make sure the trigger represents an actual opt-in to the relevant email subscription type, rather than simply a change to another contact property.

For reporting, I’d also recommend tracking the relevant subscription or welcome-email event separately from segment membership dates. If you use a custom date property, make sure it’s updated at the point you actually want to measure.

Finally, I’d recommend reviewing the segment membership history and checking with HubSpot Support to understand why the membership date appears to be changing.

Hope this helps!

- Moderator note: This post has been edited for accuracy -

[Berangere]

Hi @TMathew and welcome back, it’s a pleasure to have you again on the HubSpot Community!

Thanks for sharing this with the HubSpot Community! And thanks @dylan123 for your help!

This is definitely worth looking into, especially if changing a contact’s primary email is causing an existing active-segment membership to appear as a new membership and enroll them in the workflow again.

For subscription-based automation, I’d recommend using the Updated email subscription status event as the workflow trigger where possible, refined to the relevant subscription type and status. This more closely aligns the workflow with the action you want to capture: a new subscription can trigger the welcome workflow, and a resubscription can trigger it again when re-enrollment is enabled.

I’d also recommend raising this with our Support Team, sharing the membership history, workflow enrollment record, and confirmation that neither the segment criteria nor subscription status changed should help with the investigation.

Here are some resources on the topic:

• Set event enrollment triggers

• Review segment membership history

Also, I’d love to put you in touch with our Top Experts: Hi @danmoyle, @trevordjones and @RomyFuchs1 do you have suggestions for @TMathew, please?

Have a lovely day and thanks so much in advance!

Bérangère

[trevordjones]

Hi @TMathew and thanks for the tag @Berangere !

I like @TMathew 's approach here, but mainly because apart from addressing your immediate problem, it puts the emphasis on the event that should trigger your welcome email and uses segment membership as a filter.

One caveat is that Segment Memberships process slowly in HubSpot relative to other triggers, so it’s possible the subscription event could trigger the workflow and a filter in the segment that would remove them has not processed yet. As a result, I’d add a 1-2 minute delay after enrollment and then use a branch on segment membership as an additional filter to ensure that new subscriptions that don’t meet all the segment criteria are not sent the email.

[danmoyle]

Hey @TMathew. I haven’t run into this, and dang that sounds like a serious issue HubSpot should solve for. +1 for what @Berangere mentioned about raising this with Support. I’d also post it in the Ideas forum. For me personally, it’s nothing I’ve had to deal with that I know of, nor have I had clients bring it up. But I’ll definitely keep an eye out now.

Wish I had a solution, but anything I’d offer would literally be unchecked AI research, since it’s not anything I’ve had to solve for. I’ll leave suggestions to others. As a fellow Community member and user, thank you for bringing this up. I’ll be curious if a solution comes through!

[JayaSinha]

Hello @TMathew ,

This can happen because when the primary email is changed HubSpot may recheck the contact’s segment membership. This change can also alter the date shown as “Added to segment.” Therefore using segment membership as a trigger may not always show a real new subscription or a real re‑entry.

For subscription‑based workflows, I recommend using the contact’s subscription status or subscription‑related properties or events as the enrollment criteria, rather than relying only on “Added to segment.” This way, the workflow will respond to a subscription change instead of a simple contact record update like an email address change.

I also suggest checking whether the workflow is set to allow re‑enrollment. This will let a contact who really unsubscribes and later resubscribes enter the workflow again. An email‑address change by itself will not become the business event you are trying to capture.

I would recommend testing the workflow with a few different scenarios: change the email address of an existing subscriber, add a new subscriber and have an existing subscriber who unsubscribe and resubscribes. This can help confirm whether the workflow is triggering only when the actual subscription status changes.

With Regards,
Jaya Sinha.

[TMathew]

Thanks for the input! @Berangere I looked into changing the workflow trigger to using the “Updated marketing email subscription status” event; however, I’m not seeing a way to refine that to pick the specific subscription type. My only criteria options are:

I’ve raised it with Support but they unfortunately didn’t have a solution.

[Berangere]

Hi @TMathew and all, Happy Friday!

Thanks for getting back to us about this and for sharing the screenshot!

While you can combine the event with a contact’s subscription status, this won’t reliably distinguish between new subscriptions, resubscriptions, or changes to other preferences.

At the moment, there isn’t a way to identify which subscription type changed. I’d suggest creating a new topic on our Ideas forum here to bring more visibility to it.

That said, let’s consult with our Top Experts: Hi @danmoyle and @trevordjones can you think of a workaround for this, please?

Thanks so much and enjoy the weekend!

Bérangère

- For information, I’ll be out of the office on Monday 19th of October -