Build and save a report

Open Acquisition quality from the report library, or choose Acquisition when creating a report. It starts with orders, total sales, attributed orders, unattributed orders and attribution coverage, grouped by campaign source, medium and campaign. The default model is Last touch.

First touch and Last touch use the acquisition details recorded with each order. If only one qualifying touch is known, both models use it. A campaign or referral signal counts as attribution; a session or landing page alone does not. Changing the model changes the allocation between sources, not the total sales included.

Source, medium and campaign show the recorded UTM values. An unavailable value does not mean direct traffic: another recorded signal may still make the order attributed. Orders without a signal remain in the unattributed counts and sales. Attribution coverage is attributed orders divided by all qualifying orders. No orders means coverage is unavailable, not zero. These results do not measure advertising spend or prove that a campaign caused a sale.

Acquisition reports can also compare the previous period or previous year, using the same attribution model for both periods. Coverage for a missing earlier group stays unavailable. CSV exports record the selected attribution model. Saved reports and scheduled exports retain that choice.

Open Order operations, Payment outcomes, Refund outcomes or Fulfilment outcomes from the report library in Store Admin or the mobile app. They start with the last 30 days and all sales channels. Adjust the dates and breakdowns, then run, save, export or schedule the report.

Order operations includes all non-test orders created in the period, including unpaid, cancelled and archived orders. It shows current cancellations and full or partial refunds. A later cancellation or refund can change an earlier period. These order counts differ from Sales, which includes only qualifying sales.

Payment outcomes uses when the payment record was created, even for an older order. Split payments and retries count separately. Orders with payments counts each order once within a row, but the same order can appear in several rows. Failed payment share is not a checkout failure rate.

Refund outcomes uses when the refund was requested and shows its current outcome. Partial refunds count separately; cancelled orders remain included. A refund is completed only after its settlement and order changes are confirmed. Unconfirmed older refunds appear as unknown.

Known completed refund amount includes confirmed amounts in your base currency, including refunded charges. Check Refund amount coverage alongside it: missing amounts are unknown, not zero. A recorded zero is known. Formatting follows Settings > General. This request-date total can differ from the refunds shown against the original sale date in Sales.

Fulfilment outcomes uses when each fulfilment record was created. Partial fulfilments count separately, so one order can appear more than once. It shows pending, in-transit, delivered, returning, returned, failed or damaged, and cancelled outcomes. Tracking number coverage shows the share of fulfilment records with a tracking number.

Fulfilment outcomes does not show delivery speed. Manual status changes do not contain the carrier's original event time, so combining them with carrier updates would produce misleading durations.

Operational reports can compare with the previous period or previous year. Both periods show current outcomes of records created in their respective dates; they do not recreate the status at the end of each period. Later status changes can revise either period.

Product economics shows units, net sales, cost of goods, covered margin and cost coverage for each product, starting with the highest net sales. Cost coverage is the share of remaining units with a recorded cost. A recorded zero cost counts as known; missing costs stay unavailable. Covered margin includes only those costed units. It does not subtract payment fees, fulfilment expenses, advertising or other operating costs, so it is not your final profit.

Choose Repeat purchases and replenishment to compare repeat buying by product. Identified customers counts customers linked to an account; guest orders are excluded. Repeat customers placed at least two qualifying orders for that product inside your selected dates. Repeat purchase rate is repeat customers divided by identified customers.

Average and median days between purchases use consecutive qualifying product purchases inside the selected dates. They do not use purchases before the start date. Variants are combined under their product. Products with fewer than five identified buyers are hidden, so a missing product does not prove zero purchases. This aggregate report does not create or reveal a customer audience.

Choose Ordered journeys, or open Product view to purchase from the report library. Add 2–8 steps and use the arrows to reorder them. Purchase can only be the last step. Set Completion window in whole minutes from 1 to 1440; the starting report uses 30 minutes.

Each session enters once at its first selected event inside your report dates. Every next step must occur later, within the completion window measured from entry and before the report period ends. A later repeated entry does not restart the window. Sessions near the end of the period can still be incomplete. Steps with the same recorded time do not establish an order.

Sessions counts the sessions reaching each step. From previous step is the share continuing from the preceding step; From entry is the share of entering sessions reaching that step. A zero denominator is shown as unavailable. The first step is 100% when at least one session enters. Purchase counts when a sale is recorded, even if it is cancelled or refunded later; this is a journey report, not a current sales total.

Journeys use sessions with analytics consent. They do not join devices, storefronts or sales channels. Recorded events counts each occurrence, including events that cannot be linked to a session. Linked events and Linkage coverage show how much activity can be linked with consent; they are not unique visitor counts. Low coverage can limit what the journey tells you. Test and identified automated traffic are excluded.

Browsing steps, such as page views and product views, support the most recent 30 days. Commerce-only steps can use older retained history; How journeys are counted shows the limit for your selected steps. Custom date ranges still cannot exceed 366 days. An expired date range shows an error instead of a misleading zero. Journeys use the fixed Step breakdown, with a table or a bar chart for one measure, and do not support comparison periods.

Save and export journey reports like other reports. Exports include the step order and completion window. If the source events expire before an export runs, the export fails without a partial file. A schedule with expired dates is paused; save a recent or rolling date range before enabling it again.

Measures are the numbers to calculate, such as net sales, orders or units. Breakdowns split them into rows, such as days, products or countries. You can select up to 10 measures and 3 breakdowns. Traffic reports use one breakdown.

Choose a date range and, if needed, a sales channel. Custom ranges can cover up to 366 calendar days. Days follow the store timezone. A relative range such as the last 30 days moves forward when you reopen the report; custom dates stay fixed.

Choose Frequently bought together to find product pairs purchased in the same order. The table shows both products and Orders together. A pair appears only when it occurs in at least 5 qualifying orders within your chosen dates and sales channel. A missing pair may have fewer than 5 orders; it does not necessarily mean zero.

Paid and cash-on-delivery orders qualify, including imports. Test, cancelled and fully refunded orders do not qualify. Each product must have at least one unit remaining after completed refunds. Gift-card products and custom items are excluded. Different variants and multiple units of the same product count as one product per order.

Each pair counts once per order, in either selection order. The same customer can contribute several orders. The two product columns are fixed, and this report uses a table without comparison periods. You can save, export and schedule it like other reports. These counts describe products ordered together; they do not measure whether recommending a product caused a purchase.

Sales and product reports can compare the selected dates with the previous period or previous year. Traffic reports do not support comparisons. Previous period moves both date boundaries back by the number of store-local calendar dates in your selection. Previous year uses the corresponding calendar dates one year earlier; February 29 compares with February 28 when the earlier year has no leap day.

The table keeps the current period's rows, sorting and pages. A row that exists only in the earlier period is not added. If the current row had no earlier orders or units, additive measures compare with zero. Unavailable averages, costs, margins and cost coverage stay blank instead of becoming zero.

Change is the current value minus the earlier value. A change rate is blank when the earlier value is zero or either value is unavailable. Negative money and changes keep their sign.

Choose Run report after changing its measures, breakdowns or filters. Review the results before saving. On mobile, switch between Data and Report results to edit the choices or inspect the table.

Sort by a column and use pagination to see all matching rows. A page can show up to 250 rows. Charts show the current results page; they do not imply that later pages have no data. A chart needs one measure and one breakdown. A line chart needs a day, week or month breakdown.

Financial measures use the store base currency, even when you break down sales by order currency. Detailed amounts stay fully visible. Missing product costs appear as unavailable, not zero. Covered margin includes only items with a known cost.

Run the report, then choose Export CSV from Actions in Store Admin, or Export CSV in the mobile app. The export includes every matching row, not just the page on screen. You can continue working and return to Exports to check progress or download the file.

Each export can contain up to 100,000 rows and 64 MB. If either limit is exceeded, no partial file is offered. Choose a shorter date range or fewer breakdowns and try again. Only one report export can be queued or prepared at a time for a store.

The file records the evaluated date range, store timezone, currency and generation time. For a compared report, it also records the comparison choice and earlier date range, and includes the earlier value, change and change rate for each measure. Both periods are read from the same export snapshot. Amounts use a decimal point, no grouping separators and the currency's full decimal precision. These spreadsheet values do not use your display preferences in General.

Exports are private to the staff member who requested them, even when the saved report is shared with the store team. Downloads are available for 24 hours after completion. After that, create a new export; the export history remains visible.

Save the report first, then choose Schedule report from Actions in Store Admin, or Schedule report in the mobile app. Select Daily or Weekly, a time and a timezone. The schedule uses the saved report and sends notifications only to the staff member who created it.

Choose Every scheduled export to receive the ordinary completion notification. Choose Only when a threshold is met to turn the schedule into a report alert. Threshold alerts require a report without breakdowns or a comparison period, because the condition evaluates one exact total. Choose one of the report's number, amount or percentage measures, a condition and a threshold. Enter percentages from 0 to 100.

The export is prepared on every scheduled occurrence, even when the threshold is not met. The owner is notified only when the value meets the condition. An unavailable value never triggers the alert. Export failures remain visible as failures rather than satisfying the condition. Changing the saved report to an incompatible query prevents the alert from being enabled until the schedule is corrected.

Each staff member can create one schedule for a saved report. A store can have up to 25 enabled schedules. Pause or remove schedules you no longer need.

For rolling date ranges, each export resolves its dates for the scheduled occurrence in the store timezone. It does not shift the range to a later time when preparation is delayed. In the chosen schedule timezone, a skipped local time moves to the next valid minute and a repeated local time runs once. If several occurrences are missed, only the most recent is prepared.

Pausing or removing a schedule does not cancel an export that is already queued. Access is checked again before the export and its notification are prepared, and again when you download. Completed files remain private to the creator and expire after 24 hours.

In Store Admin, an opened saved report has its own address. Bookmark that address to reopen the same report. Sharing its address does not grant access: private reports remain visible only to their owner, and store-team reports still require report permission.

Give the report a name of up to 80 characters. Only me keeps it private to you. Store team makes it visible to staff who can view reports; staff who can edit reports can also change its definition. Only the owner can change visibility. You cannot give two of your reports the same name.

Favourites are personal. Saving preserves your report choices, not a frozen copy of its numbers. The next run reads the latest available data, so later refunds or other changes may alter an earlier period.

If someone else changes a shared report while you edit it, your changes are kept on screen. Reload the saved report to see their version before applying your changes again. Reloading or leaving with unsaved changes asks you to discard them first.

A store can keep up to 100 saved reports, including private reports. Delete reports you no longer need to make room. Deleting a report removes its saved choices and favourites; it does not delete orders, products, customers or recorded activity.