What This Update Actually Is
HubSpot is changing how it determines send time when you schedule a marketing email using the "Send in recipient's local timezone" option.
Before this update, HubSpot relied entirely on the IP Timezone property to figure out where a contact is. That property is read-only. You can't edit it, and it updates based on where a contact's browser or device last connected.
After August 19, HubSpot will check the HubSpot Timezone property (hs_timezone) first. If that property has a value, HubSpot uses it. If it's empty, HubSpot falls back to IP Timezone. The send logic is a simple two-step check: editable property first, passive signal second.
The HubSpot Timezone property is one you can write to. You can populate it via import, workflow, integration, or direct edit on a contact record.
Why HubSpot Shipped This
IP Timezone has three real problems. First, it's empty for contacts you import from a spreadsheet. If you've ever built a list from a trade show or a CRM migration, those contacts likely have no IP Timezone value at all.
Second, VPNs corrupt the signal. A contact based in Chicago who uses a corporate VPN routed through Frankfurt will show a European timezone. Your 9 AM send becomes a 4 PM send for them, and you never know it happened.
Third, IP Timezone doesn't follow humans who travel. A London-based contact visiting New York for a week still shows their UK timezone until HubSpot picks up a new IP signal, which may or may not happen before your next send.
HubSpot's answer is to give you an editable property you can control. When you know where a contact is, you can write it down. Now that value actually drives the send time.
How to Use It Step by Step
- Audit your contact database before August 19. Filter for contacts where HubSpot Timezone is unknown and IP Timezone is also unknown. Those contacts will receive your local time sends at your account's default timezone, which is probably not what you want.
- Populate hs_timezone on import. If you're bringing in a new list, add a Timezone column mapped to HubSpot Timezone. Use IANA timezone strings like "America/Chicago" or "Europe/London." HubSpot accepts this format on import.
- Build a workflow to backfill known segments. If you have contacts segmented by region or country, you can use a workflow to set HubSpot Timezone automatically. Use the "Set property value" action with a branch for each region.
- Edit individual records when you know the right timezone. For high-value contacts where timezone accuracy is critical, update the HubSpot Timezone field directly on the contact record.
- Leave HubSpot Timezone empty when you want IP Timezone to govern. If IP Timezone is accurate for a contact and you trust it, don't populate hs_timezone. The fallback logic will handle it.
- Schedule your next local time email as usual. No change to the send setup flow. HubSpot handles the property lookup behind the scenes when you select "Send in recipient's local timezone."
What It Touches in Your HubSpot Strategy
This update sits at the intersection of contact data quality and email deliverability strategy. If your HubSpot Timezone data is wrong, your send times are wrong. That's not a minor issue. Open rate windows are narrow, and missing the right hour can cost you real engagement.
Key Takeaway
The quality of your hs_timezone data is now a direct lever on email performance. Treating it as a throwaway property is no longer an option if you send to global or imported lists.
On the workflow side, this update gives RevOps teams a new automation hook. You can write workflows that set HubSpot Timezone based on country, IP data, form submissions, or even a custom preference center. That kind of automation didn't have a meaningful destination before this update.
It also reinforces something we say constantly: your CRM properties are your strategy. If the data in a field drives a business outcome, that field needs governance. You can see how that same principle applies to the updated property history table, which gives you better visibility into who changed what and when across your contact records.
On the reporting side, consider building a simple contact report showing how many contacts have HubSpot Timezone populated versus empty. Make that a dashboard tile. It'll tell you quickly whether your local time sends are actually local.
Key Takeaway
If you send to imported lists regularly, build a workflow or import template that always populates hs_timezone. One hour of setup prevents months of misaligned send times.
This update pairs directly with broader email deliverability discipline. If you want to understand what else in your list health is quietly hurting performance, our deep dive on why your B2B email list might be killing inbox placement covers the patterns we see most often across portals.
Who Should Care Most
This update matters most to specific roles and portal types. Here's who should act before August 19.
- Marketing ops leaders who manage imported lists: if your contacts came from a spreadsheet, trade show scan, or CRM migration, they almost certainly have no IP Timezone data. HubSpot Timezone is now your only lever for accurate local time sends.
- RevOps teams at companies with global audiences: humans in multiple countries, time zones, or traveling frequently are exactly the contacts where IP Timezone fails. Populating hs_timezone via workflow gives you durable, reliable send timing.
- HubSpot administrators running Marketing Hub Pro or Enterprise: this is the only tier where local time sending is available. If you're on one of these tiers and you send any volume of emails, this change is live for you on August 19.
- Businesses in tech, consulting, or professional services: these industries skew heavily toward VPN-using contacts, making IP Timezone especially unreliable. The editable property closes that gap.
George's Take
I've been inside hundreds of HubSpot portals, and I can tell you that contact data quality is almost always the invisible bottleneck. Humans spend serious time crafting email subject lines and optimizing copy, then send that email to the wrong timezone because nobody thought to govern the hs_timezone field. This update doesn't just fix a technical gap. It gives you a clear signal about where your data strategy stands. If you can't populate hs_timezone for most of your contacts, that's a conversation your marketing and RevOps teams need to have before the next big send.
“Your send time is only as smart as your data. HubSpot just gave you a writable property that drives real outcomes. Now the question is whether your team will treat it like the lever it actually is.”
If you want to pair this with a broader look at what's actually moving the needle on B2B email in 2026, check out the quick wins most B2B marketers are still missing. Timezone accuracy is one piece of a larger deliverability and engagement puzzle.
If you want a team to audit your contact data before August 19, map hs_timezone governance into your workflows, and make sure your local time sends actually hit when your contacts are ready to read, that's exactly what we do at Sidekick Strategies. Book a strategy call and let's look at your portal together.
Frequently Asked Questions
What is the HubSpot Timezone property and how is it different from IP Timezone?
The HubSpot Timezone property (hs_timezone) is an editable contact field you can populate via import, workflow, or direct record edit. IP Timezone is a read-only property HubSpot infers from a contact's browser or device location. Starting August 19, 2026, HubSpot checks hs_timezone first and falls back to IP Timezone only if hs_timezone is empty.
Will this update change how I schedule emails in HubSpot?
No. The scheduling flow in Marketing Hub stays the same. You still select "Send in recipient's local timezone" when scheduling. HubSpot handles the property lookup change in the background. The only action required from you is making sure the HubSpot Timezone property is populated with accurate data for the contacts you care about.
What happens if neither HubSpot Timezone nor IP Timezone is populated?
If both properties are empty on a contact record, HubSpot will send the email based on your HubSpot portal's default timezone. This is the same behavior that applies today when IP Timezone is missing. Contacts imported without timezone data are the most at risk for this scenario.
What timezone format does HubSpot accept for the hs_timezone property?
HubSpot accepts IANA timezone strings such as "America/New_York," "Europe/London," or "Asia/Tokyo." These are the standard timezone identifiers used across most databases and platforms. Use this format when populating via import file or workflow property-set action to ensure HubSpot recognizes the value correctly.
Can I use a workflow to bulk-set HubSpot Timezone for existing contacts?
Yes. You can build a contact-based workflow in Marketing Hub Pro or Enterprise that sets the HubSpot Timezone property using the "Set property value" action. Branch the workflow by country or region to assign the correct IANA timezone string to each segment. This is the fastest way to backfill the property across a large existing database.
Who has access to the local time email sending feature and this update?
Local time email sending, and therefore this timezone property update, is available on Marketing Hub Professional and Marketing Hub Enterprise. It's not available on free or Starter tiers. If your portal is on Professional or Enterprise and you send marketing emails, this change is live for your account starting August 19, 2026.
