UPCOMING | Local Time Campaign Property Update on August 19
What it is
Starting August 19, 2026, local-time email sending will primarily use the editable HubSpot Timezone contact property, falling back to IP Timezone only if that property is empty.
Why it matters
The old IP Timezone property couldn't be edited and was unreliable for imported contacts or contacts who travel — it derives from IP address, not from anything a person actually confirmed. Making HubSpot Timezone the primary source gives you a property you can actually correct, instead of one that just guesses.
The Take
If you send local-time email and you've never touched the HubSpot Timezone property on your contacts, go check it now.
This one has a real date attached to it, so don't file it under someday: August 19, 2026 is when the source priority flips. If you send local-time email and you've never touched the HubSpot Timezone property on your contacts, go check it now — every record where it's empty is about to start relying on IP Timezone as the fallback, which is the exact property this update is trying to get away from.
My actual advice: pull a report of contacts with an empty HubSpot Timezone property before the 19th, and figure out whether that's a handful of records or a meaningful chunk of your list. If it's meaningful, this is worth an hour of cleanup before the cutover, not after.
FAQ
When does this change take effect?
August 19, 2026.
What changes on that date?
Local-time email sending will primarily use the editable HubSpot Timezone contact property instead of the old IP Timezone property, falling back to IP Timezone only if HubSpot Timezone is empty.
Do I need to do anything before August 19?
Check whether your contacts have a populated HubSpot Timezone property. If it's mostly empty, your local-time sends are about to lean on IP Timezone by default — worth cleaning up before the cutover, not after.
Who does this affect?
Marketing Hub Professional and Enterprise customers using local-time sending.
Produced by Value-First Media