Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs/decisionlog timezones #131

Merged
merged 7 commits into from
Jan 15, 2025
Merged
Show file tree
Hide file tree
Changes from 5 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -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
Expand Down
27 changes: 26 additions & 1 deletion DECISIONLOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 |
fivetran-catfritz marked this conversation as resolved.
Show resolved Hide resolved
| Facebook Ads | Day | CLIENT SET in Facebook Ads |
| Google Ads | Hour - aggregated to daily in the package | CLIENT SET in Google Ads |
fivetran-catfritz marked this conversation as resolved.
Show resolved Hide resolved
| Linkedin Ad Analytics | Day | UTC |
| Microsoft Advertising | Hour - aggregated to daily in the package | CLIENT SET in Microsoft Ads, UTC if not set|
fivetran-catfritz marked this conversation as resolved.
Show resolved Hide resolved
| 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 |
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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?
Expand Down