Forum Stats

  • 3,679,581 Users
  • 6,528 Discussions


Date discrepancy for some user time zones in Eloqua when retrieving date-only fields from SFDC CRM (

OMC Documentation-Oracle
OMC Documentation-Oracle Posts: 103 Employee
edited Apr 29, 2022 6:27AM in Eloqua


With the arrival of Eloqua release 18D (November 16 - 17, 2018), a change will be made to correct an issue related to importing strict date fields from via Eloqua’s native integration. Prior to the 18D release, customers with the date field mapped may notice in the values imported from strict date field (date only, not date/time) being incorrect by one day.

What’s changing?

For customers using Eloqua’s native integration, and have any date fields mapped, a change is being introduced with the arrival of the 18D Release that will correct an issue that resulted in day values as being incorrect by one day. Currently date-only field values being retrieved from are shown and evaluated in Eloqua as the prior day. This is due to a time stamp that is applied to the field value during import to Eloqua.

With the arrival of Eloqua release 18D (November 16 - 17, 2018) a change will be made to correct an issue when importing strict date fields from via Eloqua’s native integration.

Specifically, this will be corrected per the resolution detailed below:


  1. A working time offset will be added to all inbound date-only fields while storing in Eloqua database. This will be in contrast to a zero offset (e.g. 9/25/2018 0:00 am) that was being stored pre-18C.
  2. A date of 9/25/2018 in will have a time stamp of 10:45 am UTC applied prior to importing to Eloqua. When displayed in Eloqua or evaluated in filters and/or programs, the time stamp is subjected to localisation based on the user’s timezone (set in the user’s profile).
  3. This approach will address the date change issue, though the time stamp will vary based on a user’s profile preference of time zone.
  4. This change is isolated to data from date fields being imported via Eloqua’s native integration only. Other sources of input to Eloqua will not be affected.


Eloqua 18D release, anticipated to arrive between November 16 - 17, 2018. Check the Eloqua Release Center for specific dates and times.

Next Steps

If you have any date fields mapped, and if you have experienced issues with date only field values being imported from since, it is recommended to re-import the data after Eloqua’s 18D release is in production.


Q: Will this change revert the functionality to how it was before 18C?

A: No. This change will apply a timestamp of 10:45 am UTC.  Prior to the 18C release, the timestamp was 12:00 am UTC.  The updated timestamp will result in the correct date in Eloqua in field values imports from date fields in all user timezones with the exception of UTC-12, UTC-11, UTC+13 and UTC+14.

Q: Do I have to worry if I am adopting Eloqua after 18C, or, I have not synched any data between Eloqua and SFDC between 18C and now?

A: No. No action required.

Q: Will one auto synch after 18D release correct all my bad data?

A: Yes. A one-time “full” sync will re-import all records in the selected object, applying the new timestamp described in this document to all date only fields.  A “full” sync can be performed by manually running the auto-sync and choosing to ignoring the date filter.

Post edited by OIT Integration User on