Individual Time Zones for Users

Individual Time Zones for Users

User-added image
This is a MUST have for any organisation that has individuals sending out Marketo emails from different time zones.  Its pain enough if someone from the east coast has to always adhere to their corprorate PST timezone, but it is too much to ask for Global regions in EMEA, APAC, US, and ANZ to all adhere to just one time zone system wide.  We need to have them be able to select time zone by user.
43 Comments
Anonymous
Not applicable
Marketo is now a global system, so it should act like one !
Anonymous
Not applicable
I would definitely benefit from this in my timezone as I'm GMT-8. This is essential for timing of sends. Think AND Act Global!
Anonymous
Not applicable
Agree, any update on when this feature will be introduced?  
Anonymous
Not applicable
it's a much needed feature
Anonymous
Not applicable
Great, please do!
Anonymous
Not applicable
I'd be curious to learn more about your use cases. For instance, how many time zone's are you currently thinking about at a time when scheduling? Would  presenting the scheduled time would it be sufficient to show your time zone so that you could see them side by side?
Anonymous
Not applicable
I'd be curious to learn more about your use cases. For instance, how many time zone's are you currently thinking about at a time when scheduling? Would  presenting the scheduled time would it be sufficient to show your time zone so that you could see them side by side?
Anonymous
Not applicable
Hi Michelle,

So its beyond just scheduling (althought I know many that would argue its worth it just for this).

When you look at your reporting, timestamps, data fields, etc, its all in one org timezone.  We need to be able to look at data fields or reports and see it localized.  I won't merge this conversation into the european dd/mm/yyyy formatting, but this is just another design request that nees to think about the localised users (s instead of z too 😉 ). 



Anonymous
Not applicable
Are you saying that the org time stamp should _not_be the record of the data? & that the data you look at should be localized to the user looking at the data?
Anonymous
Not applicable
We have multiple workspaces, which essentially are different Countries.

As our Head Office is in Australia users in the US, CA, UK, NZ and South Africa are all having to do their marketing Schedules using the Australian Timezone.

It would be a great idea for each workspace to have different time zone based on thier Locale.