Time zone mis match when dealing with data from multiple data sources about dbt_ad_reporting HOT 4 CLOSED

Hi @teja-goud-kandula thanks so much for opening this issue and posing a thoughtful and relevant question!

Your reasoning does make sense to me and ensuring standardization of timezones across the platforms is necessary in order to generate an accurate view of your Ad performance. My initial understanding was that all Ad platforms synced via Fivetran were in UTC and therefore would be consistent. My team will do some more digging into this inquiry and will get back shortly with what we find.

Thanks again and we look forward to continuing this conversation 😄

from dbt_ad_reporting.

Hi @teja-goud-kandula! I've been digging into this with our product and engineering teams and I do believe that what you're seeing is very likely correct (UTC for Linkedin and account set timezones for Google and FB) and agree that this definitely could introduce a number of issues when performing analyses. I have a couple of follow up questions for you: 1. What is your destination warehouse? 2. Would you be able to check what timezone settings (if any) are currently set up in your warehouse instance?

from dbt_ad_reporting.

Hi @fivetran-sheringuyen ,
Here are the requested answers:

1. The destination warehouse is Snowflake.
2. I am able to check the default timezone settings on the warehouse, it is set to the default value, i.e. America\Los Angles.

from dbt_ad_reporting.

Hey @teja-goud-kandula! Hm that is strange, what should happen is the timestamps should be changed to the destination timezone so you wouldn't get the mismatched timezone issues using our package. I spoke to our product team about this and believe that this should be addressed at the connector level.

I believe the best way for you to proceed would be to file a support ticket with Fivetran which you can do here.

from dbt_ad_reporting.