Jeto Ideas

Let us know what you want to see next in Jeto!

Date/Time Form Fields - Unify Entries and Configure Input/Output format and Times zones

Given: Users entering date values might be in a different timezone than the required date output.
Given: Jeto currently only works with UTC Time, but users are familiar with using their local times when planning campaigns
Given: Currently multiple fields must be filled by collaborators to input different timezones.
Give: Auto Launch requires that the admin calculates the offset based on GMT which is a bit tricky.

When: ...Creating a Launcher with date and time fields.

Then: the admin should have the ability to set a "default input timezone" and a "date output timezone" for each date field. The "date output timezone" should allow for multiple optiosn to be selected.

Then: When Jeto creates\updates date token in Marketo, it should output all the date and time information present in "date output timezone", in addition to the GMT time as a separate token.

Then: There should be an option to psuh a dedicated token with URL encoded time stamp: Ex: For Agical, ancodinf the + if timezone is a positive offset. 12:34:56%2B04:00, not 12:34:56+04:00 (literal plus signs have special meaning)

For Collanorators

When: Creating a campaign
Then: the collaborators should have the ability to enter time, on one single field in their preferred timezone.

Good source of timezones listed out in a dropdown menu including Daylight savings time:

  • Catherine Champoux
  • Nov 26 2020
  • Attach files
  • Catherine Champoux commented
    8 Dec, 2020 02:17pm


    Yes, that looks great! This will be for "add to calendar" scripts, so the plain text fields will continue to be leveraged in assets as there are too many formats to cover due to preferences and localization.

  • Admin
    David Desrosiers commented
    7 Dec, 2020 10:50pm

    Thanks @Cat for passing this request.

    Here is a first draft of what we envision for supporting entry and output of multiple date/time formats and timezones in Jeto Campaigns. Do you think this would cover for use cases you've encountered? Looking forward to getting some feedback.

    User Story:

    Requirement (I want to…):Allow user to enter time and date on a single timezones, yet allow to communicate the date/time in a different localized date/time.

    Expected Result (So that I can…): Send Global Event/Webinar times and dates that will match the local timezone of each audiences.

    Benefit (And enjoy….):
    - Same time, reduce errors: by avoid the collaborator from having to input multiple timezone entries in Jeto form. Avoid Administrators the need to convert date/time entries in various timezones manually. Automate the output of multiple date elements manually to build standard ISO date format outputs. Be compatible with calendar link date elements used in URLs.
    - Increase engagement: sending webinar and event date in the recipient's timezone and localized date format.

    Acceptance Criteria

    Jeto to offer a new field for "Date-Time" that combines both date & time entry into a single value, so that it can be later "converted" into various date-time formats and across timezones.

    For Jeto Launchers (Administrators)

    Launcher field property allows Admin to set default timezone that will be applied as the campaign input form is loaded.

    • Time output format would include ISO ISO 8601 as default format. i.e.:

      • Complete date plus hours and minutes: YYYY-MM-DDThh:mmTZD (eg 1997-07-16T19:20+01:00) where:

        • YYYY = four-digit year

        • MM = two-digit month (01=January, etc.)

        • DD = two-digit day of month (01 through 31)

        • hh = two digits of hour (00 through 23) (am/pm NOT allowed)

        • mm = two digits of minute (00 through 59)

        • TZD = time zone designator (Z or +hh:mm or -hh:mm)
          Folowing items would NOT be included in date-time format

        • ss = two digits of second (00 through 59)

        • s = one or more digits representing a decimal fraction of a second

    • Time output format would also allow additional output formats (optional) includes

      • Date+time (Common formats (TO BE COMPLETED)

      • Date only (Common formats TO BE COMPLETED)

      • Time only (Common formats TO BE COMPLETED)

      • Date + Time as URL encoded (compatible with calendar link tools such as Agical)

    • The time output formats and timezone can allows to select multiple formats and multiple timezones.

    • Jeto will push 1 token and corresponding for each combination of format and timezone selected.
      For Jeto Campaigns (Marketers)

    • Campaign form field allow the marketer to select timezone entry (ex: via single select pick-list).

    ISO 8601 Date Time Standard formats.
    ISO 8601-1:2019 Date and time — Representations for information interchange — Part 1: Basic rules

    ISO 8601-1:2019/AWI AMD 1 Date and time — Representations for information interchange — Part 1: Basic rules — Amendment 1

    ISO 8601-2:2019 Date and time — Representations for information interchange — Part 2: Extensions

  • +2