Changelog
Follow up on the latest improvements and updates.
RSS
improved
Visualization
Order Line Revenue measure re-organization (Enterprise)
We have just released an update that will group measures in the Order Line Revenue explore by aggregation type. This means all count, total, average, and percent measures will be grouped together
fixed
Integrations
Amazon Ads Sponsored Products sync key change
The sync key for
amazon_ads.sponsored_products_v3_reports
has been updated so that it does not include campaign name or ad group name. We were seeing duplicative data in the raw data when campaign or ad group names were updated because there would be a record with the old names and a second record with the new names.new
Visualization
Calendar v2 Beta
(This is an opt-in beta currently only available for Enterprise merchants who began using Daasity after September 2023.)
Overview
Time comparisons in Daasity are about to get a big upgrade, and you can now preview this feature before it's rolled out to all merchants in late April.
The new Calendar v2 upgrade brings the following improvements:
- Easier comparison calculations.To compare a measure between periods, all you need to do is choose the measure and one of its companion comparison-period measures and you're done — no more table calculations or additional filtering required.
- Plot current & previous periods on the same chart.Create the same types of charts you're used to seeing and creating in Shopify, Google Analytics, and Looker Studio.
- Simplified calendar dimensions.We're going back to the essentials and cutting the available calendar dimensions down by 40% to make an easier, more intuitive experience for the business users on your team.
Here's a quick demo of these new features in action:
How to get it
To get this feature, contact support@daasity.com. Or, if you're comfortable editing your LookML code, add the following code to your addons.lkml file:
include: "/extras/calendar_v2/*"
If it turns out you don't like the new functionality, all you need to do is remove this line of code (and then please let us know your feedback on how we can improve).
How the new time comparisons work
Comparison measures
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:
- Total Gross Sales= Total Gross Sales for the last 7 days (2/8-2/14)
- Total Gross Sales (Comp)= Total Gross Sales for the preceding 7-day period (2/1-2/7). You can also use the new Comparison Type toggle to instead compare it to the previous year. In that case, the comp measure would represent Total Gross Sales for 2/8-2/14 of the previous year.
- Total Gross Sales (Change)= Total Gross Sales minus Total Gross Sales (Comp)
- Total Gross Sales (% Change)= Total Gross Sales (Change) divided by Total Gross Sales (Comp)
New date filtering
There are two new date filters to use in your reports:
- Date (Custom Period): Use this if you want to build a comparison period on the fly, e.g.: Last 7 days, Last 2 weeks, a specific date range like 2/1/2025 - 2/5/2025
- Date (Preset Periods): Use this if you want to use one of our pre-built periods, e.g.: Yesterday, Month to date, Last retail month, Latest 4 weeks. The logic for these preset periods work the same way as the old calendar's "Pivot by" dimensions and are useful for doing apples to apples comparisons. For example, choosing the Month to date preset period will allow you to compare this month to date vs the same period last month, e.g.: 2/1-2/14 vs 3/1-3/14
Compare to Previous Period or Previous Year
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
Comparison Type
parameter:
Getting metadata about the comparison
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
Show Comparison Date (Yes/No)
toggle to update the date label to show what date is being used for the comparison:
Or you can add the
Date Comparison Info
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:
Will this affect
all
explores?It will affect most explores, with some exceptions like LTV and Product Affinity.
What will happen to existing reports?
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.
Additionally, the old calendar dimensions will still be available until we roll this feature out to all merchants in late April. (They'll continue to work after that point, but the dimensions will be hidden from the field picker.)
What about LookML customizations that I've made?
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:
- Add 2 new joins to any custom explores to include the new calendar v2 view. After enabling Calendar v2, you should add the following joins to your custom explores:
join: calendar_v2 {
relationship: one_to_one
sql: {% if calendar_v2.date_filter_preset._is_filtered %} CROSS JOIN calendar_v2 {% endif %} ;;
sql_where: {% if calendar_v2.date_filter_preset._is_filtered %} ${calendar_v2.date_in_period_date} IS NOT NULL {% endif %} ;;
}
join: calendar_labels {
view_label: "Calendar v2"
from: retail_calendar
relationship: many_to_many
sql_on: ${calendar_v2.date_in_period_date} = ${calendar_labels.calendar_date} ;;
fields: [calendar_labels.retail_month,calendar_labels.retail_week,calendar_labels.retail_year]
}
- Update any refinements or custom views. You will need to add a filter for any existing measures you want to be able to work with Calendar v2 and will need to create the Comp, Change, and % Change measures for any custom measures you have created. We have created a web app to help you make your custom code compatible with Calendar v2. (It's what we used when we made the existing views compatible with Calendar v2, and it saved us hours.) Just upload or paste your lookml code, and it will make the updates automatically. You may need to make additional tweaks, but it will at the very least do the majority of the work for you.
new
Visualization
Klaviyo List & Segment Growth explore and dashboard
This new explore and dashboard allows you to analyze list and segment growth using the data from our new Klaviyo Summary Statistics integration.
These new resources enable you to track growth and contraction of your Klaviyo lists and segments over time, which you were previously unable to do with Daasity.
You will need the new Klaviyo Summary Statistics integration for this explore and dashboard to work. Please read our changelog post highlighting key features and how to set up.
Here's an example version of the dashboard:
new
Visualization
Klaviyo Campaign & Flow Performance explore and dashboard
This new explore and dashboard allows you to analyze campaign & flow performance data from our new Klaviyo Summary Statistics integration.
These new resources enable you to analyze campaign & flow performance data that will match more closely with reporting within the Klaviyo admin. They include all of the following important KPIs for assessing the effectiveness of your Klaviyo Email/SMS program: Delivered, Cicks, Opens, Orders, Revenue, Unsubscribes, and more.
If you don't have the Klaviyo Summary Statistics integration, read our changelog post highlighting key features and how to set up.
Here's an example of the new dashboard:
improved
Visualization
Adding measures to Transactional Sales explore (Enterprise)
Added the following measures to the Transactional Sales explore:
- Count Customers- Count of unique customer IDs associated with purchases
- Count New Customer Orders- Count of purchase transactions where first first order flag = Yes
- Total New Customer Gross Sales- Sum of gross sales where first order flag = No
new
Integrations
Klaviyo Summary Statistics integration
The Klaviyo Summary Statistics integration pulls aggregated reporting data from Klaviyo for:
- Campaigns & Flows: Contains performance data such as Sends, Opens, Clicks, Conversions, and Conversion values segmented by Campaign and Flow
- Lists & Segments: Contains profile counts by day for lists & segments
If you simply want high-level reports on campaign and flow performance and list and segment growth, this is the Klaviyo integration to use.
This integration is an alternative to our existing Klaviyo V2 integration. The main benefits of using this new integration are:
- Speed. This integration pulls from a summary reporting API rather than the more-granular events API. This means you can pull a year's worth of campaign and flow performance data in a matter of minutes.
- Revenue KPIs.This integration pulls aggregated order & revenue attribution data straight from Klaviyo. This data is not included in our existing Klaviyo V2 integration because Klaviyo does not make that data available at an event level.
- Consistency with Klaviyo reports.Since this integration uses the same summary data as the reporting in the Klaviyo admin, it means all of the performance data will match almost exactly with the Klaviyo admin (the exception being that the numbers in the Klaviyo admin are real-time, while the numbers from this integration will reflect performance metrics at time of extraction.)
Documentation
Explores & dashboards that use this integration
Load More
→