Discussions

Time Zones Across Eloqua

Chris Seepe
Chris Seepe Posts: 8 Bronze Medal
edited Apr 29, 2022 6:21AM in Eloqua

Update 2014-04-14: Contact List Upload Time Zone Details Updated

Update 2017-12-06: API Endpoint Details Updated

As most of you know, the Eloqua servers are set to the Eastern (North America) time zone. That means, all dates/times are stored in the database adjusted to GMT-5 (and most likely GMT-4 when Daylight Saving Time is active). I still don't have an exact, technical description of what happens when the time zone switches from GMT-5 to GMT-4, and back; the system just compensates somehow.

Anyway, the times in different parts of the application are adjusted to, or displayed in, different time zones. The problem is, there's little-to-no indication of what time zone is being used for each of the date/time displays. I'm trying to compile a list of the different parts of the application, and what time zone is being used. HINT: Most of it is Eastern Time (GMT-5 at least; not sure entirely about DST/GMT-4).

The following is my understanding of the current state of the system, and pulled from various Topliners posts (e.g. , , ). The first link above has a good overview of this information; might also be worth the time to vote. This is not complete nor authoritative. If anything is incorrect or needs clarification, let me know. Tested at least most of these in E10; I believe the majority should apply to E9.

Component / Module / ThingTime Zone UsedNotes
Contact List UploadGMT-5

DST Not Observed

(example below)

Contact Filters / Segment Filters / Shared Filters DateTime FieldsEastern (North America) TimePossibly between GMT-5 and GMT-4 depending on Daylight Saving Time*
Campaign Canvas Compare Contact Fields on a DateTime Field / Program Builder Date ComparisonEastern (North America) TimePossibly between GMT-5 and GMT-4 depending on Daylight Saving Time*
Contact Details / Campaign Contact Entry and Next Evaluation Time / Contact Filter Results

Eloqua User Time Zone

Configurable under Setup > Profile
Insight Subscription Report Scheduling / Insight DateTime Fields / Insight DateTime Range PromptsEastern (North America) TimePossibly between GMT-5 and GMT-4 depending on Daylight Saving Time*

Cloud Connectors (Last Run Time, Date Calculator, etc.)

This needs to be retested for the new AppCloud Framework apps.

Greenwich Mean TimeSet to GMT/UTC. DST Ignored.
Form Submission Data (View in Eloqua)Eloqua User Time ZoneConfigurable under Setup > Profile
Form Submission Data (Export) / Form Submission NotificationsEastern (North America) TimePossibly GMT-5 / GMT-4 depending on DST*
Program Builder Test Mode (System Date and Time Override Input)Eastern (North America) TimePossibly GMT-5 / GMT-4 depending on DST*
Program Builder Test Mode (Display Entered Date and Time Override)Eloqua User Time ZoneConfigurable under Setup > Profile
Program Builder Entry / Exit / Evaluation Histories, Last UpdateEloqua User Time ZoneConfigurable under Setup > Profile
CRM Integration External Calls - Actual Data Written to the CRM - Date/Time Stamps (Date Modified, Date Created, etc.), Activity Dates/TimesEastern (North America) TimePossibly GMT-5 / GMT-4 depending on DST*
API Integration (Input and Output) / Asset Last Modified Date through APIEastern (North America) TimePossibly GMT-5 / GMT-4 depending on DST*
Asset Last Modified Date (View in Eloqua)Eloqua User Time ZoneConfigurable under Setup > Profile
CRM Integration Auto Synch Scheduling - Default TimeEastern (North America) TimeAlthough the interface says "10pm EST", that is not accurate; it follows DST.

*Switching between DST needs to be verified.

API Endpoint Details

bulk/2.0/contacts/exports (Specifically, the resulting contact export sync data)

By default, all times are in Eastern Time and the same as shown in the UI (if your profile is set to Eastern Time). This applies to system-level fields (e.g. {{Contact.CreatedAt}}) as well as customer-created fields (e.g. {{Contact.Field(C_Inquiry_Capture_Date1)}}).

Now, you can add a parameter to your export definition -- "areSystemTimestampsInUTC":"true" -- and this will change only the system-level fields to UTC. Customer-created fields will remain as Eastern Time.

NOTE: "Eastern Time" in this context varies between UTC-4 and UTC-5 depending on the date value in that particular fields.

For example, a Date Created (system field) value of "2017-04-30 04:58:49.423" without the areSystemTimestampsInUTC parameter will return "2017-04-30T08:58:49.423Z" with "areSystemTimestampsInUTC":"true" (meaning UTC-4, as DST was active in the Eastern Time Zone on 2017-Apr-30). Similarly, a Date Created value of "2017-12-06 22:01:34.680" without areSystemTimestampsInUTC will return "2017-12-07T03:01:34.680Z" (UTC-5 as DST was not active on 2017-Dec-07) with that parameter set to "true".

rest/2.0/data/contact/<id>

Here, all dates (system fields and customer-created fields) are exported in UTC, irrespective of user's profile settings (unlike the Bulk export, where even with areSystemTimestampsInUTC=true, only the system fields are exported in UTC). The timestamps are in epoch time/Unix time (number of seconds from 1970-01-01 00:00:00 UTC). For example, a date of "2017-12-06 22:01:34" as shown in the UI (Profile:Eastern Time) will be exported as 1493542729 (2017-12-07 03:01:34 -- UTC-5), while a date of "2017-04-30 04:58:49" will be 1493542729 (2017-04-30 08:58:49 -- UTC-4).

bulk/2.0 fields, definition, and sync createdAt and updatedAt timestamps are UTC.

Just to stress this again: If you created a new Contact date field, the Bulk API will always export that value in Eastern Time (UTC-4/UTC-5 depending on that value's date), irrespective of the "areSystemTimestampsInUTC" parameter. However, the REST API will always export that value in UTC with no option to export the as-is database value.

Update: Times in list uploads are processed according to GMT-5 (NO DST).

List Upload Example: Your Eloqua user profile is set to GMT+2. You upload a list with a date/time of "10/13/2014", which is interpreted as "2014-Oct-13 00:00:00". Currently, Eastern (North America) is observing DST, so it's really GMT-4, here. When you view the contact, the time will show as 7:00AM (not 6:00AM).

Update: It seems like Eloqua User Profile Time Zones do not observe DST whatsoever; whatever GMT±XX is shown in the selection, that's the time zone offset used (at least for Contact date/time field displays). In the above example, if the Eloqua user profile is set to "(GMT-05:00) Eastern Time (US & Canada)", the time will show as 12:00AM (not 1:00AM).

Update: The default scheduling option for auto synchs is "Auto-Synch Runs on Selected Days at 10pm EST?", but that is not accurate. EST (Eastern Standard Time) is UTC-5, but the scheduling option actually switches between EST and EDT. So, if you were in Thailand (ICT, UTC+7, no DST), between Nov 2 and Mar 8 the synch will run at 10:00AM local time, but between Mar 9 and Nov 1, it will run at 9:00AM local time.

For details on the date/time text format for list uploads, see

Post edited by OIT Integration User on
Tagged:

Comments

  • Eastern Time Zone's Daylight Saving Time starts 2014-Mar-09 at 2:00AM EST (GMT-5). At that point, it will jump ahead to 3:00AM EDT (GMT-4). I guess we'll have to see how Eloqua handles this.

  • 1068694
    1068694 Product Specialist Posts: 1

    Eloqua user time zone adjustment:

    This only controls the DISPLAY of date/time fields in the Eloqua UI. This does NOT in any way, shape or form affect the stored data.

    Eloqua always stores uploaded data "as is" and assumes it's stored in Eastern Time (GMT -5:00). Eloqua does not adjust for daylight savings time and does not jump time zones to accomplish this.

    Time zone testing:

    Time zone in Windows = no effect to display or upload

    Time zone in Eloqua user = no effect to upload, effect is seen only if time zone is not GMT -5:00

    Text fields that store dates and times will remain unaffected regardless of what time zone you've set up in your Eloqua user profile or Windows.

    Exports should always be in the "as is" state of data as it's stored on the database.

    The external call testing area is a place of confusion. The "Eloqua Data to be Sent to Salesforce" is adjusted based on your Eloqua user's time zone. The "Salesforce Data Before Testing" and "Salesforce Data After Testing" is always "as is" and simply reads the raw date info from the CRM. This is NOT time-zone adjusted based on your user. So  if your Eloqua user is GMT-8 and sending a date/time value of 10/3/2014 6:00 AM (in your spreadsheet), after the upload, in Eloqua this time will be listed as 10/3/2014 3:00 AM. If you export it again, it will be 6:00 AM.

    I am currently testing segments and filters to see how this influences things and if I can create a scenario where it's prematurely picking up contacts if for example you automatically send out emails on their birthday.

  • Is there a way to change the time zone reflected in the form submission data exported from Eloqua insights?

    Thank you!

  • Chris Seepe
    Chris Seepe Posts: 8 Bronze Medal

    Is there a way to change the time zone reflected in the form submission data exported from Eloqua insights?

    Thank you!

    Hi,

    At the moment, I don't believe there is a way; everything is displayed is Eastern Time. Actually, I'm pretty sure it's displayed according to the Eastern time zone that was currently in effect when the submission happened; meaning, if the submission happened in December, it'll be shown aligned to EST (GMT-5), but if the submission happened in July, it'll be shown aligned to EDT (GMT-4), regardless of when you actually export the data.

    I haven't personally verified this, but I think that's what happens.

    Chris

  • Lorenzo Ruzzene
    Lorenzo Ruzzene Posts: 22 Red Ribbon

    Hi! Does this refer to any POD?

  • Cheli
    Cheli Austin, TexasPosts: 24 Gold Medal

    @chrissan1207 - any updates on Cloud Apps -- are they following the same timing as Cloud Connectors did?

    Thanks in advance...

    Cheli

  • Cheli
    Cheli Austin, TexasPosts: 24 Gold Medal

    @chrissan1207 - any updates on Cloud Apps -- are they following the same timing as Cloud Connectors did?

    Thanks in advance...

    Cheli

    And Program Canvas timings?

    BTW--thank you--this is very informative!

  • Chris Seepe
    Chris Seepe Posts: 8 Bronze Medal

    Hi! Does this refer to any POD?

    Hi @Lorenzo Ruzzene, yes, this is applicable to all PODs, irrespective of geographic location.

  • Chris Seepe
    Chris Seepe Posts: 8 Bronze Medal

    @chrissan1207 - any updates on Cloud Apps -- are they following the same timing as Cloud Connectors did?

    Thanks in advance...

    Cheli

    Hi @Cheli,

    I just added information about the Bulk and REST APIs, which is what Cloud Apps use to interact with Eloqua data. Unfortunately, it's not as straightforward as we'd like.

  • Chris Seepe
    Chris Seepe Posts: 8 Bronze Medal

    Hi @Cheli,

    I just added information about the Bulk and REST APIs, which is what Cloud Apps use to interact with Eloqua data. Unfortunately, it's not as straightforward as we'd like.

    Edit: @Cheli, I just re-read your question. I originally thought you were asking about the AppCloud framework (APIs), but it sounds like you're asking about the Oracle-developed Cloud Apps themselves. Sorry, I haven't tested the specific functionality of those apps, yet.

  • Cheli
    Cheli Austin, TexasPosts: 24 Gold Medal

    Edit: @Cheli, I just re-read your question. I originally thought you were asking about the AppCloud framework (APIs), but it sounds like you're asking about the Oracle-developed Cloud Apps themselves. Sorry, I haven't tested the specific functionality of those apps, yet.

    Thanks (belatedly), Chris.  Happy New Year!

  • rlnagelmaker
    rlnagelmaker Alphen aan den Rijn, NetherlandsPosts: 9 Silver Medal

    Dear ,

    How do i actually upvote this feature request?

    Kind regards,

    Robert