Merge branch 'main' into MagicBot/add-model-counts

Author: fivetran-avinash

CHANGELOG.md

@@ -3,6 +3,7 @@
 ## Documentation
 - Added Quickstart model counts to README. ([#130](https://github.com/fivetran/dbt_ad_reporting/pull/130))
 - Corrected references to connectors and connections in the README. ([#130](https://github.com/fivetran/dbt_ad_reporting/pull/130))
+- Updated the [DECISIONLOG](https://github.com/fivetran/dbt_ad_reporting/blob/main/DECISIONLOG.md#timezone-considerations) and [README](https://github.com/fivetran/dbt_ad_reporting/blob/main/README.md#timezone-considerations) to include details about timezone differences across ad platforms. ([#131](https://github.com/fivetran/dbt_ad_reporting/pull/131))
 
 # dbt_ad_reporting v1.11.0
 

DECISIONLOG.md

@@ -30,4 +30,29 @@ tests:
   ad_reporting:
     not_null_ad_reporting__account_report_account_id:
       +enabled: false
-```
+```
+
+### Timezone Considerations
+
+The following table documents timezone differences across platforms in the `dbt_ad_reporting` package. These differences exist due to the following reasons:
+
+- Ad platforms send pre-aggregated data that cannot be back-calculated to a finer granularity to account for timezone differences. 
+- Some platforms offer hourly report data, which could potentially be standardized. However, this approach does not ensure full coverage due to non-standard timezones, such as ±30-minute and ±45-minute offsets.
+
+Although this presents challenges within this package, customers can achieve standardization by configuring all Ad accounts and connectors to UTC whenever possible.
+
+As of January 2025:
+
+| Platform | Grain of Data | Timezone |
+|----------|---------------|----------|
+| Amazon Ads | Day | CLIENT SET in Amazon Ads |
+| Apple Search Ads | Day | CLIENT SET in Fivetran Connector to either UTC or the Apple Search Ads account timezone |
+| Facebook Ads | Day | CLIENT SET in Facebook Ads |
+| Google Ads | Hour (account, campaign, ad group) and Day (ad) - package uses daily reports | CLIENT SET in Google Ads |
+| Linkedin Ad Analytics | Day | UTC |
+| Microsoft Advertising | Hour - package uses daily reports | CLIENT SET in Microsoft Ads, UTC if not set|
+| Pinterest Ads | Hour - package uses daily reports | UTC |
+| Reddit Ads | Day | UTC |
+| Snapchat Ads | Hour | UTC |
+| TikTok Ads | Hour | UTC |
+| Twitter Ads | Day | CLIENT SET in Twitter Ads |

README.md

@@ -44,6 +44,7 @@ Refer to the table below for a detailed view of final tables materialized by def
 
 > The individual platform models may have additional platform-specific metrics and fields better suited for deep-dive analyses at the platform level.
 
+
 ### Materialized Models
 
 Each Quickstart transformation job run materializes the following model counts for each selected connector. The total model count represents all staging, intermediate, and final models, materialized as `view`, `table`, or `incremental`:
@@ -63,6 +64,8 @@ Each Quickstart transformation job run materializes the following model counts f
 | [TikTok Ads](https://github.com/fivetran/dbt_tiktok_ads) | 19 |
 | [Twitter Ads](https://github.com/fivetran/dbt_twitter) | 26 |
 
+## Timezone Considerations
+Timezone differences across ad platforms impact standardization due to pre-aggregated data and non-standard timezones. See the [Decision Log - Timezone Considerations](https://github.com/fivetran/dbt_ad_reporting/blob/main/DECISIONLOG.md#timezone-considerations) for details.
 <!--section-end-->
 
 ## How do I use the dbt package?