This article explains the time zone used by Data Cloud and describes how to handle cases where ingested data is displayed at an unexpected time.
Data Cloud uses UTC (Coordinated Universal Time) as its default time zone.
When ingesting data from a data stream, any datetime values that do not include time zone information are treated as UTC.
Data Cloud references different time zones depending on the feature being used.
Note that discrepancies can occur when the user time zone and the organization time zone are configured differently.
Features That Use the User's Time Zone
The following features display timestamps based on your individual user settings:
Data Explorer
Reports
The following features use the time zone configured for your Salesforce organization:
Segments
Calculated Insights
Note: If a date offset caused by a time zone mismatch causes segments or calculated insights to filter incorrectly, we recommend aligning both the user and organization time zones. For instructions, refer to Change the Default Time Zone for a User or Organization.
By ingesting data with explicit time zone information, you can prevent data from being processed in an unintended time zone.
The following example uses CSV file ingestion via Amazon S3 to illustrate the recommended configuration and expected behavior.
Add time zone information to the datetime values in the file before ingestion.
The following shows the recommended configuration when ingesting data timestamped at 2025/9/3 12:00 in Japan Standard Time (JST, UTC+9:00), with the user's time zone set to JST.
Recommended Configuration
|
Ingested Data |
DateTime Format |
Data Explorer |
Notes |
|
2025/9/3 15:00:00+0900 |
yyyy/MM/dd HH:mm:ssZ |
2025/9/3 15:00:00 |
Append the time zone offset (+0900) to the ingested data. Additionally, by adding "Z" to the format to represent the time zone, the data can be ingested at the intended time. |
Patterns That Result in Unintended Timestamps
|
Ingested Data |
DateTime Format |
Data Explorer |
Notes |
|
2025/9/3 15:00:00 |
yyyy/MM/dd HH:mm:ss |
2025/9/4 0:00:00 |
Data without a specified time zone is treated as UTC. Since Data Explorer displays in Japan Standard Time (JST, UTC+09:00), it shows 00:00:00 of the following day, which is 9 hours later. |
|
2025/9/3 15:00 |
yyyy/MM/dd HH:mm:ss |
2025/9/3 9:00 |
The ingested data is missing the seconds (ss) component, so it does not match the format. If the format cannot be correctly processed, the time cannot be identified and is treated as 2025/9/3 00:00 UTC. Data Explorer then displays this as 09:00 JST (UTC+9:00). |
About the DateTime Format
The DateTime format string is defined when creating a new data stream. While the format may be set automatically when ingesting a CSV file, manually correct it if the inferred value does not match your data.
Navigation path:
Data Streams > New
Select Amazon S3, then click Next
Select a connection
Enter the file name, then click Next
Under Supported Fields, click the ▼ icon next to the target field
Select DateTime from the list
Select Enter format manually, then enter the date format string
Note: The format string is case-sensitive. For example, uppercase MM represents months, while lowercase mm represents minutes.
For a full reference of date and datetime pattern strings, see Date and DateTime Formats.
You can create a derived field with a converted timestamp by using a Formula Field when setting up a data stream.
This approach does not require editing the source file, but must be configured individually for each data stream. Note that Formula Fields are not supported for data streams using a hidden connector.
To configure ingested data to be treated as JST (UTC+09:00), use the following steps.
The formula subtracts 9 hours from the UTC datetime to offset the system's automatic conversion.
Configuration Steps:
Data Streams > New
Select Amazon S3, then click Next
Select a connection
Enter the file name, then click Next
Click New Formula Field
Fill in the following fields and click Save:
Replace ◯◯ with the actual DateTime field name from the Attributes tab.
Field Display Label: (any name)
Return Data Type: DateTime
Formula: DATEADD('h', -9, sourceField['◯◯'])
005318677

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.