Changelog

Follow up on the latest improvements and updates.

RSS

Overview
This update covers the last few weeks of work on AI Analyst and the Daasity MCP Server. Rates such as ROAS and click-through rate are now calculated from totals, so they hold up when you group by week or campaign. Large results and large views now reach your AI complete, and its errors say what to fix. Your views carry more of your Looker model, including Retailer Inventory, and one measure with an error no longer keeps the rest of its view from building.
What's new
  • Rates are calculated from totals.
    Some measures are written as a rate on each row, such as sales divided by spend, and then added up. Across a week or a campaign, that doesn't give the rate for the group. For these measures (ROAS, click-through rate and cost per click are the common ones), your views now divide the total by the total. Measures that convert a currency or a unit, such as session duration in minutes, are unchanged.
  • Fields from joins with a few repeated rows.
    When a joined table repeated a handful of rows that differed only in columns the explore doesn't use, the join was left out of the view along with its fields. Those repeats are now removed during the refresh and the join comes through, with fields such as an order line type or a ticket tag and the measures that rely on them.
  • Default filters from every layer of your model.
    When your own Looker project adds a default filter to a Daasity explore, the view now lists it alongside the filters the explore already had.
  • More explores become views.
    An explore was skipped when one of its fields repeated a setting, or when its SQL generated its own rows, such as a calendar of operating days. Looker accepts both, and your views now do too.
  • Large results arrive complete.
    On the MCP Server, a long result such as two years of daily sales is now sent in a compact format that fits your AI tool's size limit. If a result still has to be cut short, the AI is told how many rows were left out, so it can say so.
  • Large views fit, with the full detail one step away.
    A view with hundreds of fields, such as Sales Report, could overflow what an AI tool accepts in one response, and the AI would guess at field names. The list of views now fits, and the AI can pull one view's complete detail when it needs it.
  • Errors the AI can fix by itself.
    When a query names a field a view doesn't have, the error now names that field and the closest real ones. Month and quarter fields are marked as text labels, like 2026-10, so the AI filters them correctly.
  • Retailer Inventory views.
    The Retailer Inventory explores (Target, Ulta, Sephora, Macy's, Dillard's, Costco, KeHE and Walmart) now become views for the retailers you have data for. Weeks of supply uses the same sales window the retailer's inventory dashboard opens with.
  • A connection that only runs scheduled jobs stays connected.
    A connector used only by automated reports could lose its warehouse access after 30 days and fail with an unclear error. Access now renews every time the connector is used. If it does lapse, the AI says so and tells you how to reconnect.
  • Connect Your AI shows each refresh.
    The page shows a refresh as it runs and when each view was last built. A view that failed to build is listed with the reason.
What's fixed
  • One measure with an error doesn't stop its view.
    If your warehouse rejects the SQL behind one measure, that measure is left out and the rest of the view builds. Before, the whole view failed to build. Ask the AI what was left out of a view and it gives the reason.
  • Day names match their dates.
    An answer that named a day of the week beside a date could name the wrong day. Day names now come from the calendar.
  • Optional parts of Daasity's Looker model apply only where you use them.
    Some optional pieces, such as Shopify B2B, were being applied to every account's views. On an account that doesn't use them, that could change a filter or leave an order count off Sales Report. They now apply only when your Looker model includes them.
  • Measures that add up an ID are left out.
    A measure that sums a product ID or a similar identifier isn't a real total. It's now left out of the view, and the AI gives the reason if you ask for it.
  • Your own SQL for a Daasity view is what the view reads.
    If your Looker project redefines a Daasity view with its own SQL, the view now reads that SQL, so the columns you added come through.
  • A comment inside a filter no longer breaks its view.
    An explore whose filter contained a SQL comment could fail to build.
  • AI Analyst considers every matching view.
    A very large view at the top of the list could crowd out the others, so an answer could come from the wrong view.
What to expect
A rate that's now calculated from totals can differ from a Looker tile built on the same measure, because the tile still adds up the row-level rates. To check the AI's number, divide the two totals for the same period.
What to do
Run Refresh Views from the account menu in AI Analyst. No Refresh Semantic Layer is needed. If your company has several brand accounts, run it on each one. Larger results, clearer errors, the Connect Your AI page and the fix to day names work now, with or without the refresh.
Then try two things. Ask the AI what was left out of your Sales Report view, and why. And ask for ROAS by week on one of your ad platforms, then check one week against that week's sales divided by its spend.
Overview
You can now hand your AI a saved Look and have it rebuild that report from your Daasity views. The AI gets the Look's fields, filters and definitions, so it starts from a report your team already trusts and doesn't have to guess how it was built.
Who it's for
Teams using the Daasity MCP Server who keep Looks in their shared folders.
What's new
  • Start from a Look.
    Paste a Look's link or its ID into your AI and ask it to reproduce the report.
  • The same fields and filters.
    The AI matches each field in the Look to the field in your view, applies every filter the Look has, and names both the Look and the view in its answer.
  • It tells you what it couldn't match.
    If a field from the Look isn't on the view, or a filter can't be carried over exactly, such as a relative date range, the answer lists it and says what was used in its place.
What to expect
There's nothing to set up. Existing connections pick this up without reconnecting. It works with Looks saved in your shared folders.
Then try one thing. Paste the link to a Look you use every week, ask your AI to reproduce it, and compare the totals with the Look.
Overview
Starting November 17, Daasity calculates two things differently for Amazon Seller Central orders: Total Discount Amount and the fulfillment date on orders fulfilled by Amazon. Both changes come from merchant feedback and help your Amazon numbers in Daasity line up more closely with your own Seller Central reporting.
What's changed
Discounts come from the All Orders report.
Total Discount Amount now uses the promotion amounts on each order line in the All Orders report. Promotion amounts from the FBA Promotions report are no longer added to it.
Fulfillment dates use the date the order shipped.
For orders fulfilled by Amazon, the fulfillment date now comes from the shipment date in the Amazon Fulfilled Shipments report, in place of the earliest ship date on the order. If an order isn't in the shipment report yet, Daasity uses the earliest ship date until it is. Orders you fulfill yourself are unchanged.
What to expect
Amazon Total Discount Amount may be lower, and Net Sales higher by the same amount. Gross Sales doesn't change. If you report by fulfillment date, some Amazon orders near the end of a month may move to the next month.
These changes apply to your past Amazon orders as well, so historical Amazon discounts, Net Sales and fulfillment dates update along with new orders. There's nothing you need to do.
Validating Your Amazon Data in Daasity shows how to check Amazon discounts and fulfillment dates against Seller Central.
Overview
If your company has several brands in Daasity, your team can now connect the Daasity MCP Server to all of them at once. Each brand gets its own connector in your AI tool. That means one person can ask about any brand they have access to in the same chat, without disconnecting and reconnecting to switch.
Who it's for
Companies with more than one brand account in Daasity. It matters most for teams on Claude Team or Enterprise, where an admin adds connectors for the whole organization. If your company has one brand, nothing changes.
What's new
A connector for each brand.
Each brand's Connect Your AI page now gives a URL of its own. Before, every brand used the same URL, and Claude only lets an organization add a URL once, so the whole organization was limited to one Daasity connector. Now your admin can add one for each brand.
Every brand in the same chat.
Connect to each brand you work on, then ask about any of them in one conversation. Each answer comes only from the brand you asked about.
Only your brands.
A person can connect only to brands they can sign in to in Daasity, and gets a clear message if they try another. Access still follows your Daasity user access, so to keep someone to one brand, give them access to that brand only.
Each brand stands on its own.
Disconnecting a brand, or losing access to one, leaves your other brands and everyone else's connections as they were.
What to do
For your admin: in your AI tool's organization settings, add one connector for each brand. Use the URL from that brand's AI Analyst > Connect Your AI page, and name the connector after the brand so your team can tell them apart.
For each person: sign in to a brand in Daasity, then click Connect on that brand's connector in your AI tool. Repeat for each brand you work on.
If your company has one brand, no action is needed. You connect the way you do today, and existing connections keep working.
Then try one thing. Ask for last week's net sales for two of your brands in the same chat, and check each answer against that brand's dashboard.
Connect several brands walks through each step.
Overview
Your Loop Returns integration now loads the return method behind each return: how the customer is sending it back, where it's going, and where it stands. You can report on it alongside the returns and return lines you already have.
What's new
A return method for every return.
Each return now carries its return method: the provider and method type, its current state, the RMA, the QR code link and scannable ID, when it was scheduled and last updated, and the return address it's headed to.
Loaded with your returns.
The return method comes from the same Loop data Daasity already pulls for your returns, so it adds no extra calls to Loop.
One row per return.
A return with no return method still gets a row, so return counts match across tables.
What to expect
No setup is needed. Existing Loop Returns integrations pick it up on their next daily run.
Loop Returns Integration Specifications lists every field and where it lands.
Overview
There's a new Sales Sources page in Daasity. It lists every sales source Daasity finds in your account, and you set how each one is named and grouped. Every report uses what you set here.
What's new
Every source in one list.
Shopify and Amazon Seller Central show one row per store and sales channel found in your data, such as Amazon.com, Amazon.ca and Non-Amazon. Amazon Vendor Central, BigCommerce, Target Plus and Walmart Marketplace show one row per connected integration. New sources appear on their own after your data loads.
You set the grouping.
For each source, enter the sales channel name you want in your reports and, if you like, a business unit such as a brand or region. Then choose its business channel (Direct to Consumer, Wholesale, Marketplace or Retail) and store type (eCommerce, Wholesale, Amazon or Retail).
You know what's left.
A banner at the top tells you how many sources still need a name.
What to expect
Open Settings, then Commerce, then Sales Sources. Click Save when you're done, and your next data refresh picks up your changes. If a source you mapped stops showing up in your data, its row stays so you can edit or clear it.
Retail feeds aren't listed yet.
Sales Sources walks through each column.
Overview
AI Analyst and the Daasity MCP Server now carry measures that are built by adding or subtracting other totals, including Total Sales, Average Order Value and Average Unit Retail on Sales Report, and the change, lift and incremental measures on your syndicated and retail views. Order explores built on your own data models get a line-level view for product and unit questions. Year-over-year answers now say how the two periods were lined up, and the AI tells you when a field was left out of a view.
What's new
  • Total Sales, Average Order Value and Average Unit Retail are on Sales Report.
    Total Sales adds together gross sales, discounts, refunds, shipping, tax and duties, and Average Order Value and Average Unit Retail are built on it. These measures had been left out of views because they combine several totals. They now come through with the same definition as your dashboards, and a total with no rows for the period counts as zero, the same way Looker counts it.
  • Change and lift measures on syndicated and retail views.
    On your SPINS, Circana, Nielsen, Kroger and URMS views, measures that compare the latest period with the year-ago period, such as dollar sales change, unit sales change, lift, non-promo sales and incremental sales, come through for the same reason. They appear on views that carry both periods.
  • Year-over-year, lined up the way most brands do.
    A day or a week compares with the same days of the week 52 weeks earlier, so a Monday is compared with a Monday. A month, quarter, year or to-date period compares with the same calendar dates a year earlier. A question asked in your retail or fiscal calendar compares with the same retail or fiscal period last year, when your view carries that calendar. Every answer names the basis it used and gives the date range of both periods. If you want the other basis, ask for it and the AI will use it.
  • Line-level detail for orders built on your own data models.
    If your model has an orders table with its order lines joined to it, a common setup for teams that build their own models in dbt, the AI now gets a second view at the order line level, named for the explore and the order line table. Questions about products, units and line sales answer from that view, and order-level totals stay on the original view so nothing is counted twice.
  • Fields from joins that match one row per order.
    Some explores mark a join as one-to-many even when each order matches only one row in the joined table. Those joins had been left out of views along with their fields, such as an order type. Each one is now checked against your data during the refresh, and when it adds no rows, its fields come through, along with any default filter that relies on them.
  • Know when a field was left out.
    When you ask for a field that couldn't be included in a view on its latest refresh, the AI now says it isn't available on that view and gives the reason. It no longer tells you the field doesn't exist or uses a similarly named field from another view.
What's fixed
  • Views dated only by a hidden field have their date.
    When an explore's only date field is hidden from Looker's field picker, its view had no date at all, so a question about a date range added up every row. The view now includes that date, and its description notes that the field is hidden in your field picker.
What to do
Run Refresh Views from the account menu in AI Analyst. No Refresh Semantic Layer is needed. If your company has several brand accounts, run it on each one. Year-over-year answers and the note on fields left out of a view work now, with or without the refresh.
Then try two things. Ask for last month's Average Order Value and compare it with your dashboard. And ask for last week's net sales against last year; the answer should name the basis it used and give both date ranges.
Overview
When a vendor stops accepting the login Daasity holds for one of your integrations, you now hear about it from the connection check, before your data goes missing. A temporary outage on the vendor's side is no longer reported as a login problem, and when the problem is with Daasity's own access, it comes to us instead of asking you to reconnect. An integration you turned on but never added to a workflow now gets a notification too.
What's fixed
Rejected logins are caught.
Some connection checks treated an expired or revoked login as working, so nobody heard about it until data stopped arriving. That's fixed for TikTok Shop, Klaviyo, Yotpo, AppLovin, Cin7 Core, Northbeam, Skio, Algolia, Narvar, Newstore, Avalara, Reddit, Facebook, Sailthru, Criteo, Google Analytics on BigQuery, Walmart Marketplace, Salesforce Service Cloud, and your database, S3 and SFTP sources. Any integration whose vendor rejects the login is now treated as a login problem. You get a "Reconnect needed" or "Couldn't reach the source" notification with a button to fix it.
Fewer false alarms.
ShopMy, Instacart Ads, Prodco, Shopify B2B and Iterable had reported a temporary outage on the vendor's side as a login failure. They no longer do.
Errors that tell you the fix.
Saving a GA4 integration whose Google login expired now asks you to reauthorize instead of showing an error. A TikTok Ads login with no access to any advertiser account explains the ways to fix it. A BigQuery connection missing a permission tells you which one.
History loads stop on a login problem.
If a history load runs into a login problem, it now stops and tells you, instead of carrying on or sitting in the queue with no error.
What's new
Integrations left out of a workflow.
If an integration is active but isn't part of any active workflow, Daasity isn't pulling its data. You now get an "Integration not in a workflow" notification, with a Review button to add it to a workflow. New integrations get 7 days before it appears.
What to expect
If one of your integrations now asks you to reconnect, its saved login had stopped working. Click Reauthorize, or Check connection for a database, and it starts loading again.
Notification Types lists every notification and what to do about it.
Overview
Downloading a dashboard now gives you what you see on screen, saved Looks keep the filters you saved, and a few error pages are replaced with messages that tell you what to do.
What's fixed
Downloads match your filters.
PDF, PNG and CSV downloads of a dashboard now use the filters applied on screen. Before, a download used the dashboard's saved default filters, so changing a date range updated the tiles but not the file.
Saved Looks keep their filters.
Reopening a saved Look to edit it no longer brings back the filters it had before your last save.
Download errors you can act on.
When a Look, dashboard or Explore can't run, for example because a filter points to a field that no longer exists, the download window now shows the reason so you can fix and re-save it, instead of "Something went wrong."
Home page weeks match your dashboards.
The charts on your home page now label each week by its end date, the same way your dashboards do.
Old Explore links open.
An Explore link that no longer points anywhere, such as an old bookmark or a link copied from another account, now opens Explore with a message instead of an error page.
What to expect
No action is needed.
Overview
A round of fixes across your data sources over the last several weeks. Most of them stop a refresh from failing or quietly missing data. A couple need a reload of past data, noted at the end.
What's fixed
Shopify.
Cancelled orders on very large stores no longer time out, because they're now pulled in smaller time windows. Discounts with more than one page of codes no longer stop the extraction. Transactions now include the payment ID.
Amazon Seller Central.
A report stuck in Amazon's queue no longer holds your whole refresh open. After 6 hours Daasity stops waiting and notifies you that the data is missing. Single-day history loads are no longer cancelled by Amazon.
Amazon Ads.
Sponsored Display reports outside the US load again; the off-Amazon conversion columns Amazon only offers in the US stay empty there.
Facebook.
Ad-level custom reports with breakdowns now keep one row per ad or campaign, instead of collapsing to one row per date and breakdown.
Northbeam.
Exports no longer fail on Northbeam's rate limits or on a client ID saved with a stray space. On busy days, large uploads wait for a slot instead of leaving a gap. If Northbeam stops offering an attribution model on your account, such as Linear, Daasity skips it instead of failing the run.
Walmart.
Walmart Marketplace inventory loads page through reliably. Walmart Connect checks that your Advertiser ID is 6 digits and explains how to add Daasity as an API partner if access is missing.
History limits are explained.
Facebook, Amazon Ads, Bing Ads, Criteo, Cin7 Core and Impact Radius now show the earliest date their history can reach and why, instead of a date picker that quietly stops.
Everything else.
Survey responses sent by webhook that contain accents, curly quotes or emoji are no longer dropped. SFTP sources that sign in with a key no longer fail at random. A file pattern that ends in the file type without a dot, like *csv, now finds your files.
What to do
Two of these fixes apply going forward only. If you use Facebook ad-level custom reports with breakdowns, or want the payment ID on older Shopify transactions, contact Support and we'll reload the past data.
Load More
→