Released: May 28, 2025

The last_month field in the drp.calendar table is currently returning values from the same month of the previous year instead of the previous month of the current year for the previous_month category.

Update the logic for the previous_month category to correctly reference the previous calendar month within the current year in the drp.calendar table. This will ensure accurate time-based categorizations for reporting and analysis.

Released: May 27, 2025.

The Marketing Attribution explore currently returns data for only the most recent 30 days. Historical data outside this window is largely missing (NULL values), with only occasional records populated.

Implement logic to accurately associate orders with a rolling 30-day update list. Update the logic in both dm_stg.mkt_order_revenue_attribution and dm_mkt.fct_vendor_level_performance to support incremental updates, focusing only on the most recent 30-day period.

This will ensure consistent and complete attribution data going forward.

Released May 27, 2025

Some Shopify orders are showing negative shipping amounts due to the shipping discount being subtracted twice during transformation. The shipping discount is currently included in the Total Cart Discount Amount, but not in the Total Discount Amount, leading to inconsistent discount representation.

Exclude the Shipping Discount from the Shipping Amount calculation in the Shopify Order Base transformation script. Adjust the Cart Discount calculation by explicitly subtracting the Shipping Discount from the Total Discount Amount in the same script. This update will ensure that shipping and discount values are accurately reflected in reporting and analytics.

Released: May 27, 2025

We identified an issue affecting two Calendar V2 custom-date-filter options:

These filters weren't functioning correctly because our underlying LookML logic expected both a start and an end date, but these options inherently provide only one date.

All explores utilizing Calendar V2 dimensions were affected.

We implemented a fix to update the logic so that it automatically fills in missing dates, ensuring that both filters always work correctly without manual adjustments:

This logic required both start and end dates, leading to errors when only one was provided.

For any questions or issues, please reach out via support or comment below.

Released: May 27, 2025

Klaviyo UNS tables were experiencing duplicate records due to both the "Klaviyo_v2" and "Klaviyo Summary Statistics" integrations sharing the same source_id in the platform.account_integrations table.

We updated our SQL JOIN logic to explicitly reference the integration source name, ensuring accurate data alignment and eliminating duplicates:

For any questions or further issues, please reach out via support or comment below.

This is a new source-specific Amazon Ads explore & dashboard to help you slice and dice their Amazon Ads data with more flexibility.

The new explore includes all available data loaded by the integration so you can segment and analyze performance in the same way you would using the Amazon Ads UI or downloaded reports. It gives you many more fields to work with than the existing Vendor-Reported Marketing Performance explore.

The new dashboard gives you a starting point for analyzing you Amazon Ads performance data in a way that mirrors the performance reports from the Amazon Ads UI. Additionally, some things you can do with this dashboard that you can’t do easily in the Amazon Ads UI:

*(This feature will be enabled who began using Daasity .)*

Time comparisons in Daasity are about to get a big upgrade.

The new Calendar V2 upgrade is coming out of beta and

The new Calendar v2 upgrade brings the following improvements:

Here's a quick demo of these new features in action:

Calendar v2 introduces new Comp, Change, and % Change companion measures that can be pulled into your reports. This makes it so you don't need to pull in comparison-period label dimensions and use table calculations to create comparison measures.

In this example, if your filter period is the last 7 days and you're analyzing on 2/14:

There are two new date filters to use in your reports:

Calendar v2 makes it easy to switch between comparing to the previous period or the previous year. By default, the Comp and Change measures compare to the previous period, but you can easily change that using the new parameter:

(Click to view full screen)

If you want to see what dates are being compared — either for QAing or just to include in a chart or dashboard — there are two days to do so.

You can use the toggle to update the date label to show what date is being used for the comparison:

Or you can add the dimension to your data table to show the overall dates being compared. This is useful if you want to add a tile to your dashboard that contains meta data about what periods are being used for the comparison:

It will affect the following explores:

We're rolling this out in a way so that all of your existing reporting using the old version of the calendar will still work. However, if you want your existing reports to leverage the new Calendar v2 setup, you will need to modify them manually to use the new dimensions and filters.

The old calendar dimensions will still technically be included in the above explores, but they will be hidden. If you want to re-expose them, you can reach out to our support team — or, if you have developers on your team, you can edit the parameter for the view in the explores. We have set the for the view to an empty string, which hides the view from the field picker but still allows them to work. Populating the will re-expose the view in the field picker.

If you need the old calendar dimensions back, create a generic lkml file in the folder in your Looker project, and add the following contents to the file:

If you have created refinements or new custom views or explores in your Looker project, you will need to do 2 things after enabling Calendar v2:

If the custom explore does not already have a join, you will also need to include the file and set up a join for it. The instructions below assume that is already joined in the explore.

Calendar V2 now gives the ability to use a dynamic date dimension and control whether that dimension displays the date, week, month, or year. This makes it easy to quickly toggle back and forth between different types of trend charts in your dashboards.

We have added field descriptions to 16 Looker views to provide additional context when interacting with reports.

When adding orders to the BSD with a non-default currency, our transformation code was not properly converting the currency amounts into the default currency. We have updated our code to fix that.