From 758440916f1528947596f21adc9a68d0893e4e99 Mon Sep 17 00:00:00 2001 From: fivetran-catfritz <111930712+fivetran-catfritz@users.noreply.github.com> Date: Fri, 10 Jan 2025 17:49:27 -0600 Subject: [PATCH 1/7] docs/decisionlog-timezones --- DECISIONLOG.md | 25 ++++++++++++++++++++++++- 1 file changed, 24 insertions(+), 1 deletion(-) diff --git a/DECISIONLOG.md b/DECISIONLOG.md index 0f58667c..e8a9748d 100644 --- a/DECISIONLOG.md +++ b/DECISIONLOG.md @@ -30,4 +30,27 @@ tests: ad_reporting: not_null_ad_reporting__account_report_account_id: +enabled: false -``` \ No newline at end of file +``` + +### Ad Reporting Timezones + +The table below 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. + +| Platform | Grain of Data | Timezone | Hourly Custom Reports? | Can Configure Time Zones for Custom Reports? | +|----------|---------------|----------|------------------------|----------------------------------------------| +| Amazon Ads | Day | CLIENT SET - Timezone set by the "profile" to request the report | No | No | +| Apple Search Ads | Day | CLIENT SET - Configured in connector setup - either UTC or the Apple account's timezone | Yes | ORTZ, UTC | +| Facebook Ads | Day | CLIENT SET - Facebook Ads account's timezone | No | No | +| Google Ads | Hour - aggregated to daily in the package | CLIENT SET - Timezone used when creating manager account | Yes | No | +| Linkedin Ad Analytics | Day | UTC | No | No | +| Microsoft Advertising | Hour - aggregated to daily in the package | CLIENT SET - Microsoft Ads account's timezone or UTC if not set | No | No | +| Pinterest Ads | Hour - aggregated to daily in the package | UTC | Yes | No | +| Reddit Ads | Day | UTC | No | Customer can choose timezone in custom reports | +| Snapchat Ads | Hour | UTC | No | No | +| TikTok Ads | Hour | UTC | Yes | No | +| Twitter Ads | Day | CLIENT SET - Twitter Ads account's time zone | No | No | From 3f2f15998e7e314301e4ab291cf2cceac18d1a5d Mon Sep 17 00:00:00 2001 From: fivetran-catfritz <111930712+fivetran-catfritz@users.noreply.github.com> Date: Fri, 10 Jan 2025 17:56:56 -0600 Subject: [PATCH 2/7] update reamde --- DECISIONLOG.md | 2 +- README.md | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/DECISIONLOG.md b/DECISIONLOG.md index e8a9748d..af3aab12 100644 --- a/DECISIONLOG.md +++ b/DECISIONLOG.md @@ -32,7 +32,7 @@ tests: +enabled: false ``` -### Ad Reporting Timezones +### Timezone Considerations The table below documents timezone differences across platforms in the `dbt_ad_reporting` package. These differences exist due to the following reasons: diff --git a/README.md b/README.md index b814998e..30b16543 100644 --- 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. ## How do I use the dbt package? From 2c89fbbe8e34b7d60df4b0ce07125ac4385b0f2b Mon Sep 17 00:00:00 2001 From: fivetran-catfritz <111930712+fivetran-catfritz@users.noreply.github.com> Date: Mon, 13 Jan 2025 20:00:59 -0600 Subject: [PATCH 3/7] update changelog --- CHANGELOG.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index b0fb1fb7..3652e827 100644 --- 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 From 9d5faca5bc3cc8da32951427fb745676259273b6 Mon Sep 17 00:00:00 2001 From: fivetran-catfritz <111930712+fivetran-catfritz@users.noreply.github.com> Date: Mon, 13 Jan 2025 20:02:49 -0600 Subject: [PATCH 4/7] update decisionlog --- DECISIONLOG.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/DECISIONLOG.md b/DECISIONLOG.md index af3aab12..8ec7ef7b 100644 --- a/DECISIONLOG.md +++ b/DECISIONLOG.md @@ -43,14 +43,14 @@ Although this presents challenges within this package, customers can achieve sta | Platform | Grain of Data | Timezone | Hourly Custom Reports? | Can Configure Time Zones for Custom Reports? | |----------|---------------|----------|------------------------|----------------------------------------------| -| Amazon Ads | Day | CLIENT SET - Timezone set by the "profile" to request the report | No | No | -| Apple Search Ads | Day | CLIENT SET - Configured in connector setup - either UTC or the Apple account's timezone | Yes | ORTZ, UTC | -| Facebook Ads | Day | CLIENT SET - Facebook Ads account's timezone | No | No | -| Google Ads | Hour - aggregated to daily in the package | CLIENT SET - Timezone used when creating manager account | Yes | No | +| Amazon Ads | Day | CLIENT SET | No | No | +| Apple Search Ads | Day | CLIENT SET | Yes | ORTZ, UTC | +| Facebook Ads | Day | CLIENT SET | No | No | +| Google Ads | Hour - aggregated to daily in the package | CLIENT SET | Yes | No | | Linkedin Ad Analytics | Day | UTC | No | No | -| Microsoft Advertising | Hour - aggregated to daily in the package | CLIENT SET - Microsoft Ads account's timezone or UTC if not set | No | No | +| Microsoft Advertising | Hour - aggregated to daily in the package | CLIENT SET | No | No | | Pinterest Ads | Hour - aggregated to daily in the package | UTC | Yes | No | | Reddit Ads | Day | UTC | No | Customer can choose timezone in custom reports | | Snapchat Ads | Hour | UTC | No | No | | TikTok Ads | Hour | UTC | Yes | No | -| Twitter Ads | Day | CLIENT SET - Twitter Ads account's time zone | No | No | +| Twitter Ads | Day | CLIENT SET | No | No | From f4bd2f57f06fb0902fec052a7cd8ccfa18ffb1c2 Mon Sep 17 00:00:00 2001 From: fivetran-catfritz <111930712+fivetran-catfritz@users.noreply.github.com> Date: Wed, 15 Jan 2025 11:19:27 -0600 Subject: [PATCH 5/7] update decisionlog --- DECISIONLOG.md | 30 ++++++++++++++++-------------- 1 file changed, 16 insertions(+), 14 deletions(-) diff --git a/DECISIONLOG.md b/DECISIONLOG.md index 8ec7ef7b..9645d668 100644 --- a/DECISIONLOG.md +++ b/DECISIONLOG.md @@ -34,23 +34,25 @@ tests: ### Timezone Considerations -The table below documents timezone differences across platforms in the `dbt_ad_reporting` package. These differences exist due to the following reasons: +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. -| Platform | Grain of Data | Timezone | Hourly Custom Reports? | Can Configure Time Zones for Custom Reports? | -|----------|---------------|----------|------------------------|----------------------------------------------| -| Amazon Ads | Day | CLIENT SET | No | No | -| Apple Search Ads | Day | CLIENT SET | Yes | ORTZ, UTC | -| Facebook Ads | Day | CLIENT SET | No | No | -| Google Ads | Hour - aggregated to daily in the package | CLIENT SET | Yes | No | -| Linkedin Ad Analytics | Day | UTC | No | No | -| Microsoft Advertising | Hour - aggregated to daily in the package | CLIENT SET | No | No | -| Pinterest Ads | Hour - aggregated to daily in the package | UTC | Yes | No | -| Reddit Ads | Day | UTC | No | Customer can choose timezone in custom reports | -| Snapchat Ads | Hour | UTC | No | No | -| TikTok Ads | Hour | UTC | Yes | No | -| Twitter Ads | Day | CLIENT SET | No | No | +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 | +| Facebook Ads | Day | CLIENT SET in Facebook Ads | +| Google Ads | Hour - aggregated to daily in the package | CLIENT SET in Google Ads | +| Linkedin Ad Analytics | Day | UTC | +| Microsoft Advertising | Hour - aggregated to daily in the package | CLIENT SET in Microsoft Ads, UTC if not set| +| Pinterest Ads | Hour - aggregated to daily in the package | UTC | +| Reddit Ads | Day | UTC | +| Snapchat Ads | Hour | UTC | +| TikTok Ads | Hour | UTC | +| Twitter Ads | Day | CLIENT SET in Twitter Ads | From e12ce5dcbb0591f84ef15fbae1e48d482f7c1a62 Mon Sep 17 00:00:00 2001 From: fivetran-catfritz <111930712+fivetran-catfritz@users.noreply.github.com> Date: Wed, 15 Jan 2025 14:34:12 -0600 Subject: [PATCH 6/7] Apply suggestions from code review Co-authored-by: Jamie Rodriguez <65564846+fivetran-jamie@users.noreply.github.com> --- DECISIONLOG.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/DECISIONLOG.md b/DECISIONLOG.md index 9645d668..bdc15980 100644 --- a/DECISIONLOG.md +++ b/DECISIONLOG.md @@ -46,11 +46,11 @@ 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 | +| 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 - aggregated to daily in the package | CLIENT SET in Google Ads | +| Google Ads | Hour (account, campaign, ad group) and Day (ad) - aggregated to daily in the package | CLIENT SET in Google Ads | | Linkedin Ad Analytics | Day | UTC | -| Microsoft Advertising | Hour - aggregated to daily in the package | CLIENT SET in Microsoft Ads, UTC if not set| +| Microsoft Advertising | Hour - package uses daily reports | CLIENT SET in Microsoft Ads, UTC if not set| | Pinterest Ads | Hour - aggregated to daily in the package | UTC | | Reddit Ads | Day | UTC | | Snapchat Ads | Hour | UTC | From 371d4743888308d2c25ada54bd9478a3307319c8 Mon Sep 17 00:00:00 2001 From: fivetran-catfritz <111930712+fivetran-catfritz@users.noreply.github.com> Date: Wed, 15 Jan 2025 14:37:03 -0600 Subject: [PATCH 7/7] update readme --- DECISIONLOG.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/DECISIONLOG.md b/DECISIONLOG.md index bdc15980..a7394d3a 100644 --- a/DECISIONLOG.md +++ b/DECISIONLOG.md @@ -48,10 +48,10 @@ As of January 2025: | 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) - aggregated to daily in the package | CLIENT SET in Google 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 - aggregated to daily in the package | UTC | +| Pinterest Ads | Hour - package uses daily reports | UTC | | Reddit Ads | Day | UTC | | Snapchat Ads | Hour | UTC | | TikTok Ads | Hour | UTC |