Docs/decisionlog timezones (#131)

* docs/decisionlog-timezones * update readme * update changelog * update decisionlog * Apply suggestions from code review Co-authored-by: Jamie Rodriguez <[email protected]> * update readme --------- Co-authored-by: Jamie Rodriguez <[email protected]>
fivetran · Jan 15, 2025 · a82f473 · a82f473
1 parent e3cc112
commit a82f473
Show file tree

Hide file tree

Showing 3 changed files with 33 additions and 1 deletion.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,3 +1,8 @@
+# dbt_ad_reporting version.version
+
+## Documentation
+- 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
 
 ## Breaking Changes

diff --git a/DECISIONLOG.md b/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 |
diff --git a/README.md b/README.md
@@ -44,6 +44,8 @@ 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.
 
+## 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?