Release Notes

Release notes for @chordcommerce/data-autonomy.

Autonomy 2.1

This release upgrades all Autonomy data models in Autonomy 2.0.

Key highlights of this release:

• Revenue definitions for both gross revenue and net revenue have been revised. Gross and net revenue exclude sales tax, include shipping revenue, and reflect adjustments more accurately.

• The "Product" dashboard line item sales now reflect the product of line item quantity and line item price.

• Visitors are no longer pre-aggregated daily.

• Cancelled orders are now removed from the order count in the dashboards.

• Customer counts are now based on unique user ID instead of order email, allowing customer traceability despite changing email addresses.

• Traffic attribution categorization rules have been improved to reflect traffic sources more precisely.

• Time to shipment has decreased due to a bug fix on the calculation.

• The number of visitors in Top Referrers in the “Marketing" dashboard has increased due to a bug fix on the visualization.

• There are new and renamed field names and field labels in explores to improve the analyst experience.

Key highlights in more detail:

Revenue definitions have been revised.

Gross Revenue: sales tax has been removed from this calculation as sales tax is typically viewed as a liability and not recorded as part of revenue. However, sales tax is still included as a field that can be added to or removed from calculations in Explore.

• Autonomy 2.0: gross revenue = payment by the customer + promotions.

  • Orders must be completed and have a net total greater than zero to be included.

  • The value of promotions did not always encompass all possible order adjustments.

• Autonomy 2.1: gross revenue = item total + shipment total - included tax total.

  • Orders must be completed to be included in the calculation.

  • The qualification that orders must have a net total greater than zero has been excluded to reflect gross revenue more accurately.

• Impact: gross revenue more accurately reflects the gross amount and no longer includes tax.

Net Revenue: includes shipping revenue in the calculation, which had previously been subtracted from net revenue. Shipping revenue has been and is still included in gross revenue and remains an individual field that can be added or removed from calculations in Explore.

• Autonomy 2.0: net revenue = gross revenue - shipping revenue - promotions - credits - refunds.

  • The sum of promotions, credits, refunds, and shipping revenue did not always encompass all possible order adjustments.

• Autonomy 2.1: net revenue = gross revenue - promotions - credits - refunds.

  • For invoicing, shipping revenue will continue to be removed from net revenue. Net revenue still does not include any Stripe processing fees.

• Impact: net revenue more accurately reflects adjustments (promotions, credits, and refunds) and includes shipping revenue.

The "Product" dashboard line item sales now reflect the product of line item quantity and line item price.

• Autonomy 2.0: the "Product" dashboard sales metrics were based only on the line item price.

• In Autonomy 2.1, line item sales now reflect the product of line item quantity and line item price, meaning line item sales will be higher in cases when line items have a quantity greater than one.

• Impact: there may be slight increases in line item sales for items with quantities greater than one in the "Product" dashboard and "Line Items" explore, impacting the following "Product" dashboard tiles: Average Price per Unit, Top Products by Sales, Top Products for First Purchases by Sales, and Bottom Products by Sales.

Visitors are no longer pre-aggregated daily.

• Autonomy 2.0: visitors were pre-aggregated daily.

• Autonomy 2.1: there is a more granular view of visitors that no longer pre-aggregates daily, which means that a single visitor coming back to the website on two different days will be counted as a single visitor if measured over multiple days. In contrast, the legacy dashboards would have counted that visitor twice (once per visited day).

• Impact: there may be slight changes to the following metrics when viewing them for a time period other than daily: Traffic (visitors) and Visitor Conversion.

Cancelled orders are now removed from the order count in the dashboards.

• Autonomy 2.0: Cancelled orders were included in the order counts that were displayed in the dashboards. They were also included in the Orders explore.

• Autonomy 2.1: The Orders explore still includes the cancelled orders, but the Sales explore excludes them. The dashboards are now pulling from the Sales explore.

Customer counts are now based on unique user ID.

• Autonomy 2.0: customer counts were based on order email, which could change over time for a given customer.

• Autonomy 2.1: customer counts are based on unique user IDs, which will remain consistent even when customers change their emails.

• Impact: there may be slight decreases in customer counts if users have changed their email, impacting the following metrics: Customer Counts, Average Sales per Customer, Average All-Time Sales per Customer, and Top Products for First Purchase by Quantity.

Traffic attribution categorization rules have been improved to reflect traffic sources more precisely.

• Autonomy 2.0: attribution categories were: SEO, Employee, Organic, Organic Social, Referral, and Paid Social.

• Autonomy 2.1: categories are Direct, Paid Search, Organic Search, Other, Paid Social, Organic Social, Affiliate, Display, and Email.

• The new categories are assigned to the sessions based on: source, medium, has_gclid, has_utm, has_referrer, which are all available in the explores. As such, the end-user of the dataset should be able to understand why a particular visitor was classified in a specific category.

Time to shipment has decreased due to a bug fix on the calculation.

• Autonomy 2.0: The "time from order to shipment" calculation was from order completion to first shipment. It also included a flawed logic that added a full day in some cases.

• Autonomy 2.1: The "time from order to shipment" calculation is from order completion to last shipment. The bug in the calculcation has been fixed.

• Impact: The average time from order to shipment has decreased.

The number of visitors in Top Referrers in the “Marketing Dashboard” has increased due to a bug fix on the visualization.

We’ve made changes to explores to allow for more flexibility and exploring.

• Order ID in the legacy explores have been renamed to order number. Order ID in the new dashboard is a Chord proprietary ID that will be unique, even across two stores. This will be useful in multi-store settings.

• In Autonomy 2.0, the "Orders" Explore contained completed orders only. In Autonomy 2.1, the "Orders" Explore now contains both “created” and “completed” orders, so there are many more rows. We added the "Sales" Explore to provide a filtered view of completed orders.

• The "Users" Explore includes any user with a User ID, whether or not they have a completed order. To get customer information (so information on users with at least one completed order), we can set the user_is_customer to yes.

• There are additional, along with renamed, field names and field labels in explores to improve the analyst experience.