Help · Audience
Your store's time zone
Every date in the app runs on your store's own clock. That is the time zone set in your Shopify admin. The app reads it and never offers a second setting that could disagree with it. Settings shows it, read-only, and if you change it in Shopify the app follows within a minute or so — no reconnecting needed. Your store's currency follows Shopify the same way.
A campaign you scheduled with Pick a date and time keeps the moment it was set for: one set for 9am goes out at that same moment, which reads as a different hour on the new clock. If you want 9am on the new clock, open the campaign and pick the time again. A campaign scheduled In each person's time zone needs nothing from you: people whose location the app knows still get your hour on their own clock, and everyone else gets it on your store's new clock. A campaign that has already started keeps the times it worked out when it started.
Businesses exist all over the world, and plenty of them sell all over the world too. So your store's day is the day that counts here, not a single world clock picked because it is convenient for the machines. Turning one time zone into another is just math, and machines are very good at math, so there is no reason your store should have to think in anyone else's hours. And no, this is not Y2K: nobody is worried about the machines breaking at midnight.
Until your store is connected to Shopify there is no time zone to read, and dates fall back to UTC rather than guessing from whichever browser happens to be open.
Dates you pick
When a rule names a day, it means that whole day on your store's clock.
- Since September 4 starts at midnight on September 4 in your store's time zone, and counts everything from then on.
- Between August 1 and August 31 starts at your midnight on August 1 and runs to your midnight at the end of August 31, so both days count whole.
- Before September 4 counts everything up to your midnight at the start of September 4. Nothing on September 4 itself counts.
- A profile property compared as a date — is before, is after, is on — reads each answer as a day on your store's calendar. Somebody whose answer says 11pm on the 3rd in your time zone is on the 3rd, even if the same moment was already the 4th somewhere else.
- Daylight saving is taken into account for the day you pick, so a date in January and a date in July both start at your midnight.
"In the last N days"
For something a person did — an order, a checkout, a product view — in the last 30 days counts back 30 full days from the moment the segment is counted. For a campaign, that is when it starts sending. It is a rolling window, so the same rule catches slightly different people tomorrow. First seen counts the same way.
For a profile property that holds a date, in the last 30 days means today and the 29 days before it, by your store's calendar, and more than 30 days ago means the days before that. The two meet with no gap and no overlap.
Discount codes
A discount code the app makes for one person ends at the very end of a day on your store's clock — 11:59:59pm in your time zone, never at midnight somewhere else. If the discount it comes from ends sooner, the code ends then instead. The date printed with a code on one of your forms is your store's date too.
When an email arrives is a different clock
Your store's clock decides who is in an audience; a person's own clock can decide when it reaches them. A campaign scheduled In each person's time zone goes out at the hour you pick on each person's own clock, where the app knows where they are.
The Campaigns page covers it, and texts always wait for a decent hour where the person is — the Quiet hours for texts page says how.
Rules you import
When you import rules from a tool that counts its days on one world clock, the app turns their dates into the same days on your store's clock. That can move a few people at the edges, and the import report says how many on each segment's row.
That way every date rule here means the same thing. An imported rule for "August 1 to August 31" becomes between August 1 and August 31 in your time zone. Their "after September 3" excludes September 3 itself, so it becomes since September 4 on your store's clock.
That can move a few people at the edges: an order placed at 10:42pm on July 31 in New York was already August 1 on the world clock, so it counted there and does not count here. Once the import finishes, the import report says, on each segment's row, how many people the change moved in or out. Until that count is done, the row says it has not been counted rather than showing a number. The app tries a few more times over the next half hour; if the count still cannot finish, the row says it could not be counted, and that is its final answer.