Joost Boonzajer Flaes via Elementary: Fix unit mismatch between historical_orders and real_time_orders #414
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes a critical unit mismatch between the historical_orders and real_time_orders models that was causing anomalies in the RETURN_ON_ADVERTISING_SPEND metric.
Problem
cents_to_dollars
macro to convert amounts to dollarsThis resulted in a ~100× scale difference in the data feeding into downstream models, causing the ROAS calculation to be inconsistent.
Changes
Modified historical_orders.sql to:
Added documentation comment to real_time_orders.sql to clarify that all monetary values are in dollars
Impact
This fix will normalize all monetary values across the pipeline, ensuring that calculations like ROAS are consistent regardless of whether the data comes from historical or real-time sources.
Created by:
[email protected]