Data 360 Ingested Datetime Not Displayed as Expected

Data 360 uses Coordinated Universal Time (UTC) by default. When ingesting data from data streams, any date/time data that does not include time zone information is treated as UTC.

Time Zones Used by Each Feature

Data 360 references different time zones depending on the feature. Caution is required if the user and organization time zone settings differ.

Features Using User Time Zone

The following features display time based on your individual user settings:

Data Explorer
Reports, etc.

Features Using Organization Time Zone

The following features use the time zone configured for your entire Salesforce organization:

Segments
Calculated Insights, etc.

If datetime values shift due to time zone differences, filters for segments or calculated insights may not function correctly. To ensure the displayed time matches the processing time, it is recommended to align the user and organization time zones. For details on configuring each time zone, refer to Change default time zones for Users and the organization.

How to Align Time Zones

By considering the time zone when ingesting data, you can prevent unintended time zone shifts. This section explains the configuration methods using an example of importing a CSV file via Amazon S3.

Method 1: Modify Ingestion Data

Modify the data in the import file to add time zone information. The following tables show the recommended settings and unexpected patterns when importing data with a user time zone of Central Standard Time (CST, UTC-06:00), but the same behavior applies to any time zone.

Recommended Settings

Ingested Data	DateTime Format	Data Explorer	Remarks
2026/3/3 05:00:00-0600	yyyy/MM/dd HH:mm:ssZ	2026/3/3 05:00:00	Add time zone information (-0600) to the ingested data. Also, adding "Z" representing the time zone to the format enables ingestion at the expected time.

Unexpected Patterns

Ingested Data	DateTime Format	Data Explorer	Remarks
2026/3/3 05:00:00	yyyy/MM/dd HH:mm:ss	2026/3/2 23:00:00	Data without a specified time zone is processed as UTC. Since Data Explorer displays time in CST, it shows 23:00:00 the previous day (6 hours earlier).
2026/3/3 05:00	yyyy/MM/dd HH:mm:ss	2026/3/2 18:00	The ingested data lacks seconds (ss), so it does not match the format. If the format cannot be processed correctly, the time cannot be determined and is processed as 2026/3/3 00:00 UTC. Data Explorer displays it as 2026/3/2 18:00.

Configuration Steps for DateTime Format

Define the format of the ingested data when creating a new data stream. If the automatically configured format differs from your expected values, modify it manually.

Navigate to [Data Streams] | [New].
Select [Amazon S3] and click [Next].
Select the connection source.
Enter the file name and click [Next].
Under [Supported Fields], click the ▼ icon for the target field.
Select [DateTime] from the list.
Enter the format in [Enter date format here] under Input format manually.

Note: Formats are case-sensitive (e.g., uppercase "MM" represents month, lowercase "mm" represents minute). For strings and definitions of each date/time pattern, refer to Date and Datetime Formats.

Method 2: Create a Separate Field Using Formula Fields

Create a separate field that converts the time by using a Formula Field during data stream creation. Modifying the original file is unnecessary, but this task is required for each data stream. Note that this method is not supported for data streams using connectors where Formula Fields are hidden.

The following steps describe how to configure the ingested data as CST (UTC-06:00). This setting adds 6 hours from the UTC datetime to offset the automatic system conversion.

Navigate to [Data Streams] | [New].
Select [Amazon S3] and click [Next].
Select the connection source.
Enter the file name and click [Next].
Click [New Formula Field].
Enter each field and click Save.
- Field Label: Any
- Formula Return Type: DateTime
- Transformation Formula: DATEADD('h', 6, sourceField['◯◯'])
  
  Note: Replace "◯◯" by clicking the actual DateTime field name from the Attributes tab.