Skip to main content

Localization & timezones

This article covers how Glowtify handles languages, timezones, and multi-region audiences. Timezone behavior in particular has real consequences for scheduling — read this if your audience spans multiple regions or if you're unclear why a post went out at 3 AM.

Interface language​

Each user picks their preferred language for the Glowtify UI in Account settings. By default, Glowtify uses your browser language.

Content languages are separate — you can have a French UI and still publish in English, or vice versa.

Content languages​

The language of content generated by Glowtify is driven by two inputs:

  1. The primary language declared in your Business DNA (often matches your audience)
  2. The channel defaults — some channels (e.g., CyberImpact) ask for language at publish time (fr_ca / en_ca)

If you run multilingual marketing, you have two choices:

  • One store, multiple languages — manage per-epic language selection inside each epic
  • Multiple stores, one per language — cleaner separation of Business DNA, audiences, and analytics per language

Most teams pick one store per language once they cross a meaningful volume in each.

Timezones — the critical details​

Store timezone​

Every store has a default timezone (set in Workspace manager). Scheduled times you enter in the app are interpreted in this timezone unless explicitly overridden.

User timezone​

Every user has a profile timezone (set in Account settings). The app uses your user timezone to display timestamps (e.g., "published at 3 PM your time") but scheduling is always in the store's timezone.

Soft scheduling and timezones​

For social + ads, Glowtify stores the scheduled datetime in UTC internally and uses the store's timezone for display. At publish time, Glowtify pushes to the platform in UTC — the platform handles any timezone-related display on the recipient side.

Real scheduling and timezones​

For email + blog, Glowtify hands the datetime + timezone to the platform:

  • CyberImpact: receives sendAt + timezone explicitly
  • Mailchimp: receives the schedule time in UTC, Mailchimp applies its own user timezone logic
  • Klaviyo: receives datetime with send_strategy: static, applies its own timezone logic
  • WordPress / Shopify blog: receive UTC datetime, the platform displays it in its own timezone

Consequence: if your email audience is in Europe but your Glowtify store is set to Eastern time, double-check the scheduled time — a 9 AM Eastern schedule is 3 PM in Europe. Use the store's timezone consistently or switch store timezone when planning campaigns for a different region.

Daylight saving​

Glowtify handles DST transitions correctly by storing UTC internally. A publication scheduled "at 9 AM store time on November 3" will go out at 9 AM local on that date, even if DST flips in between.

Edge case: the two ambiguous hours during the DST "fall back" transition. Glowtify defaults to the earlier instance (pre-transition). If this matters for a specific publication, pick a time outside the transition window.