When you ingest data into Data 360 (formerly Data Cloud), Data 360 converts the date-time field during ingest to UTC. You can view the system stored datetime in Query Editor when querying for the data. If you view the datetime field in Data Explorer, the date time will be converted into the user's default timezone. To view the raw data that was ingested in your data stream, query the data in Developer Console with SOQL like
```select <datetime field> from <DLO object>```
When activating DateTime attributes to Marketing Cloud Engagement, as stated in this article: Create a Marketing Cloud Engagement Activation for a Segment - DateTime gets converted to CST: Central Standard Time (UTC-6). This is only true for DIRECT ATTRIBUTE. For related attributes, when activated to marketing cloud, they are stored in JSON format Like seen here: Review Data in Marketing Cloud Engagement.
DateTime attributes in this JSON will not be converted to CST. They will remain as UTC string text within the JSON
002472165

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.