You may experience situations where the numbers in Campaigns (for example, number of orders on X date) do not match to the same date in Metrics or IQ/Snowflake. This can be caused, in part, by the underlying timezone of the data
Input Data to CDP is ingested in UTC time (*Unless a special request has been made to change it)
Input Data is converted from whatever timezone it was originally in to UTC (ie.. GMT). If this is not appropriate, we can change the input data timezone.
Dates in Campaigns are transformed to client tenant timezone
In Campaigns+/Legacy Campaigns, this data is converted to the tenant local timezone.
Dates in 360 Profiles are transformed to client tenant timezone
Dates in Metrics is displayed as UTC (*Unless a special request has been made to change it)
By default, the data in Metrics is displayed in UTC. This can be overridden by special request.
Dates in IQ/Snowflake is displayed as UTC
The IQ/Snowflake data is displayed in it's native UTC. You would have to write a timezone transform SQL query to transform it from UTC to your local timezone.