Daasity
Home
Feature Requests
Changelog

Changelog

Follow up on the latest improvements andΒ updates.

RSS

new

πŸŽ‰ New: Custom Revenue and Order Metrics

We're excited to announce the launch of our new Custom Revenue & Order Metrics Framework! This powerful update enables you to easily define and manage your own revenue calculations and order definitions directly within Daasityβ€”without needing custom code or developer resources.
Explore these new capabilities now and take greater control over your business metrics today!
πŸ“ˆ Tailored Revenue Calculations
  • Customize your revenue logic to match your specific business rules (e.g., excluding wholesale discounts or refunds). This metric definition will persist throughout all of your Daasity data models and downstream metrics that include the [Revenue] or [Orders] metric (ex:
    Avg Order Value (AOV)
    , Returning Customer Revenue).
  • UI allows you to quickly toggle inclusion/exclusion of discounts, refunds, and credits.
  • Default: [Net Sales]
πŸ“¦ Define Your Valid Orders
  • Set your own criteria for "valid orders" to ensure your analytics align perfectly with your business practices.
  • Easily configure logic to exclude subscription, duplicate, or canceled orders directly in the interface.
  • Default: Excludes all special cases (gift-card only, fraudulent, free, cancelled and voided orders), add any of these back in using the UI.
πŸš€ Empowering Merchant Control
  • No more costly or time-consuming customizations.
  • Gain immediate control and clarity over critical business metrics.
This lays the groundwork for future advanced analytics features, ensuring your insights are always accurate, impactful, and fully aligned with how your business operates.
Where to find it:
In the Daasity app, navigate to:
Data β†’ Digital Analytics β†’
Revenue Metric
image
Data β†’ Digital Analytics β†’
Valid Order Metric
image

new

Important Update: Analytics Explore Name Changes

We’ve updated the naming conventions for several analytics Explores across Omni, Marketing, Ecommerce, Retail, and Retailer Portalsβ€”not just to keep you on your toes, but to make our platform easier to use, more consistent, and ready for what's next.
These changes create a cleaner foundation for upcoming AI-powered features and enhanced analytics experiences. Each new name improves clarity while aligning with our long-term roadmap, including enriched metadata, standardized metric definitions, and improved contextual insights.
Here’s a complete list of updated Explore names:
Omni
  • Omnichannel Weekly Sales β†’
    Company Performance
    (360-degree view, filtered to owned-brand and non-duplicative markets.)
  • Omnichannel Weekly Sales β†’
    Omnichannel Sales
    (Detailed, product-level insights across all channels.)
Marketing
  • Order & Order Line Revenue β†’
    Ecommerce Orders & Revenue (by Order Date)
  • Vendor-Reported Marketing Performance β†’
    Marketing Ad Performance
  • Email & SMS Campaign Performance Details β†’
    Email & SMS Performance
  • Marketing Attribution β†’
    Marketing Attribution
Ecommerce
  • Daily Plan to Actual β†’
    Forecast vs Actual: Ecommerce
  • Customer Flags & Info β†’
    Customer Analysis
  • LTV Time Series β†’
    Customer LTV & Repurchase
  • Customer Segments - Historical β†’
    Customer Segment Performance
  • Current Inventory Level β†’
    Ecommerce Inventory
  • Product Page β†’
    PDP Performance
  • Product Affinity β†’
    Product Affinity
  • Shopping Stage β†’
    Shopping Funnel
  • Subscriber Monthly Churn Rates β†’
    Subscription Churn
  • Traffic β†’
    Traffic
  • Customer Retention Performance MTD β†’
    Customer Segment Performance (MTD)
  • Transactional Sales Report β†’
    Ecommerce Orders & Revenue (by Transaction Date)
  • Product Repurchase Rates β†’
    Product Repurchase Rates
  • Subscription Churn Time Series β†’
    Subscription Churn by Tenure
  • Subscribers β†’
    Subscription Customer Details
  • Subscription Future Charges β†’
    Subscription Forecast
  • Subscription Shipment Series β†’
    Subscription Shipment Lifecycle
  • Site Search - Detail β†’
    Algolia Search
  • Amazon Business Reports - By Day β†’
    Amazon Business Reports - Daily Summary
  • Reviews and Orders β†’
    Yotpo Reviews and Orders
Retail (Unified Data Models)
  • URMS β†’
    Retail Promotional ROI Analysis
    (Unified syndicated retail and POS sources aggregated to the market-level, with baseline and promotional lift metrics, merchandising conditions designed for analyzing promotional efficiency and comparing different tactics across markets and products, including competitors..)
  • URMS β†’
    Retail Brand & Category Performance
    (Unified syndicated retail data, advanced competitive insights.)
  • URS β†’
    Retail Store Performance
    (Store-level sales from POS and wholesale data.)
  • Retailer Sales - Costco Circana β†’
    Costco (Circana)
Retail (Syndicated Data)
  • Retail-Market Sales - Latest Period (Circana) β†’
    Circana - Aggregated
  • Retail-Market Sales - Weekly (Circana) β†’
    Circana - Weekly
  • Retail-Market Sales - Latest Period (Nielsen) β†’
    Nielsen - Aggregated
  • Retail-Market Sales - Weekly (Nielsen) β†’
    Nielsen - Weekly
  • Retail-Market Sales - Latest Period (SPINS) β†’
    SPINS - Aggregated
  • Retail-Market Sales - Weekly (SPINS) β†’
    SPINS - Weekly
Retailer (POS)
  • Retailer Sales - Amazon Vendor Central β†’
    Amazon Vendor Central
  • Retailer Sales - Sephora Portal β†’
    Sephora
  • Retailer Sephora Inventory β†’
    Sephora Inventory
  • Retailer Sales - Sephora EDI β†’
    Sephora Store Performance
  • Retailer Sales - ULTA β†’
    ULTA
  • Retailer ULTA Inventory β†’
    ULTA Inventory
  • Retailer Sales - Ulta EDI β†’
    ULTA Store Performance
  • Retailer Sales - Whole Foods β†’
    Whole Foods
For any questions or support, please us at support@daasity.com.
Warm regards,
The Daasity Team

fixed

Fix for incorrect "previous_month" logic in [last_month] field

Released: May 28, 2025
Overview
Issue:
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.
Solution:
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.

fixed

Fix for Incomplete Historical Data in Marketing Attribution

Released: May 27, 2025.
Overview
Issue:
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.
Solution:
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.

fixed

Correction to Shipping Amount and Discount Calculation Logic

Released May 27, 2025
Overview
Issue:
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.
Solution:
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.

fixed

Calendar V2 Filter Enhancement: Custom Date Range Bug Fix

Released: May 27, 2025
Overview
Issue:
We identified an issue affecting two Calendar V2 custom-date-filter options:
  • "is before"
  • "is on or after"
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.
Impact:
All explores utilizing Calendar V2 dimensions were affected.
Solution
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:
  • "is before"
    now defaults to a start date of
    Jan 1, 2000
    when start date is null.
  • "is on or after"
    now defaults to an end date of
    today's date
    when end date is null.
Technical Details
Prior Logic:
This logic required both start and end dates, leading to errors when only one was provided.
{% if date_filter_custom._is_filtered %}
{% date_start date_filter_custom %}
{% elsif date_filter_preset._is_filtered %}
{% date_start date_filter_preset %}
{% else %}
${TABLE}.current_period_start
{% endif %}
New Updated Logic:
Start Date Adjustment:
{% if date_filter_custom._is_filtered %}
COALESCE({% date_start date_filter_custom %},'2000-01-01')
{% elsif date_filter_preset._is_filtered %}
{% date_start date_filter_preset %}
{% else %}
${TABLE}.current_period_start
{% endif %}
End Date Adjustment:
{% if date_filter_custom._is_filtered %}
DATEADD(day, -1, COALESCE({% date_end date_filter_custom %}, ${todays_date}))
{% elsif date_filter_preset._is_filtered %}
{% date_end date_filter_preset %}
{% else %}
${TABLE}.current_period_end
{% endif %}
Recommended Actions
  • Developers should verify custom explores that utilize these filters to ensure compatibility.
  • Update internal documentation as needed.
Support
For any questions or issues, please reach out via support or comment below.

fixed

Klaviyo UNS Tables Duplicate Records Bug Fix

Released: May 27, 2025
Overview
Issue:
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.
Solution:
We updated our SQL JOIN logic to explicitly reference the integration source name, ensuring accurate data alignment and eliminating duplicates:
INNER JOIN platform.account_integrations ai
ON p.__source_id = ai.source_id
AND ai.source = 'klaviyorevision'
Support
For any questions or further issues, please reach out via support or comment below.

new

Visualization

Enterprise Only

Amazon Ads explore & Dashboard

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:
  • See overall performance by campaign type
  • See performance from multiple ad profiles aggregated
  • Switch currency KPIs easily between the original reported currency and your Daasity account master currency
(Click to view full-size image)
image

new

Visualization

Calendar V2

*(This feature will be enabled
only for Enterprise merchants
who began using Daasity
after September 2023
.)*
Overview
Time comparisons in Daasity are about to get a big upgrade.
The new Calendar V2 upgrade is coming out of beta and
was released on April 24.
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 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.
image
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:
image
  • 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:
(Click to view full screen)
2025-02-14_14-03-42 (1)
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:
image
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:
image
Will this affect
all
explores?
It will affect the following explores:
  • Amazon All Orders
  • Amazon Business Reports - By ASIN
  • Amazon Business Reports - By Day
  • Amazon Settlement Report
  • AppLovin
  • Daily Company Metrics
  • Daily Plan to Actual
  • Daily Plan to Actual Marketing
  • Inventory Levels
  • Klaviyo Campaign & Flow Performance
  • Klaviyo Events
  • Loop Returns
  • Marketing Attribution
  • Okendo Reviews
  • Order & Order Line Revenue
  • Shipstation
  • Shopping Stage
  • Subscribers
  • Traffic
  • Transactional Sales
  • Vendor-Reported Marketing Performance
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.
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
view_label
parameter for the
retail_calendar
view in the explores. We have set the
view_label
for the
retail_calendar
view to an empty string, which hides the view from the field picker but still allows them to work. Populating the
view_label
will re-expose the view in the field picker.
How to re-enable the old Calendar dimensions
If you need the old calendar dimensions back, create a generic lkml file in the
base_refinements
folder in your Looker project, and add the following contents to the file:
include: "//base_daasity/views/drp/calendar.view.lkml"
view: +retail_calendar {
label: "Calendar"
}
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:
  1. Add 2 new joins to any custom explores to include the new calendar v2 view. After enabling Calendar v2, you should do the following joins to your custom explores:
Please Note!
If the custom explore does not already have a
retail_calendar
join, you will also need to include the
//base_daasity/views/drp/calendar.view.lkml
file and set up a join for it. The instructions below assume that
retail_calendar
is already joined in the explore.
# Add the following include statement to the top of the custom explore file
include: "//base_daasity/views/drp/calendar_v2.view.lkml"
# Add the following joins to the explore
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]
}
  1. 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 added. 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.

improved

Visualization

Adding dynamic date field to Calendar V2

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.
dynamic date
Load More
β†’