Getting Started

Your old platform’s analytics will not match the new dashboard

Record definitions and baseline figures before moving, so changing metrics does not look like changing demand.

The store.fan teamNovember 15, 20266 min read
Your old platform’s analytics will not match the new dashboard

You move your products to a new storefront, wait for the first week of sales, and notice that the numbers do not resemble the old dashboard. Visits look lower. Conversion rate has changed. Revenue appears to sit in a different date range. It is tempting to conclude that demand has fallen. Often, you are comparing different definitions rather than different customer behaviour.

Why two dashboards disagree

Analytics tools rarely measure the same thing by default. One platform might call a page load a visit, while another groups several page loads into a session. One might show gross order value; another might subtract refunds or exclude taxes and fees. A sale can also be assigned to the day of payment, the day an order was created or the day a payment cleared.

The disagreement becomes more noticeable during a move because the tracking environment changes at the same time as the storefront. Your old product URL may redirect. A link in your bio may send people to a new page. Some visitors may have already seen the old page, then return through the new one. If the systems use different rules for attribution, the same person can appear as a new visitor, a returning visitor or an unattributed sale.

Record the old baseline before switching

Choose a fixed period before the move. A calendar month is easy to explain, but any complete period works if you use the same dates throughout. Export the available data where possible, then save a plain-language note beside it. The note matters because a figure without its definition cannot be reproduced.

  1. 1Record the date range, currency and timezone used by the old dashboard.
  2. 2List each product and its number of orders, units sold, refunds and revenue as the platform defines them.
  3. 3Save visits, sessions, product-page views, checkout starts and purchases if those measures exist.
  4. 4Write down how the old platform treats taxes, payment fees, discounts, refunds, cancelled orders and test transactions.
  5. 5Record traffic sources using the labels shown by the old system, rather than translating them into your own categories.
  6. 6Note the number of active subscribers, members, leads or coaching bookings if those are part of your business.

Take a screenshot as a visual record, but do not rely on it alone. A screenshot preserves the result, not the filter settings behind it. Include the filters, export files and a short data dictionary in one folder. If a figure is unavailable, mark it as unavailable instead of filling the gap with an estimate.

Build a small measurement dictionary

A measurement dictionary is a list of terms and their meanings. It gives you something to check when the new dashboard uses familiar words differently. You can create it in a spreadsheet with one row per metric.

MetricDefinition to recordQuestion for the new dashboard
VisitorA person, browser or device counted by the old systemIs this a person, a device, a visit or a session?
Conversion rateThe numerator and denominator usedDoes it divide purchases by visitors, sessions, page views or checkout starts?
RevenueGross, discounted, refunded or net amountAre taxes, refunds, fees and cancelled orders included?
OrderWhether pending, failed or refunded orders countWhen is an order created and when is it removed or adjusted?
SourceThe rule used to assign a visit or saleIs attribution based on the first click, last click, referral or an unknown source?

When your new storefront is ready, inspect its definitions before interpreting the first results. Store.fan provides an analytics area, but the useful comparison is still your responsibility: identify what each displayed number represents, then match it to the closest old measure. Do not rename two unlike metrics simply because both are labelled “conversion”.

Compare a controlled period after the move

Give the new dashboard a clean comparison window. If you recorded the last 30 complete days on the old platform, compare that with the first 30 complete days after the move, while noting anything that makes the periods unlike. A launch email, a seasonal sale, a broken link or a product price change can affect demand independently of the dashboard.

  • Compare the same product or product group, not the whole catalogue if the catalogue changed.
  • Use the same revenue basis, such as gross sales before refunds or refunded-adjusted sales.
  • Separate ordinary sales from launch offers, discount codes, bundles and one-off payments.
  • Check payment status before counting orders. A failed or pending payment should not be treated as a completed sale without a clear reason.
  • Compare traffic sources only when the links and naming conventions are consistent.
  • Write an explanation beside every material difference before deciding that demand changed.

Separate demand from the move itself

A migration can change the path a customer takes. Your bio link may now open a storefront instead of a link list. A product page may have a different layout. Checkout may ask for different information. These changes can affect behaviour, even if the audience and offer stay the same.

Keep a migration log with dates for every meaningful change: redirect enabled, product published, price changed, email sent, discount started and checkout issue resolved. Then you can explain a movement in sales using events you actually observed rather than guessing from a single graph. If payments are recorded differently, inspect the payment records and status rules in the new setup; store.fan sends money directly to your own Stripe account, while Stripe's own processing fee still applies.

Use the new dashboard for decisions, not nostalgia

Once you have a baseline, stop trying to make every old label appear in the new system. Choose a small set of measures you can define and act on: completed purchases, revenue on a stated basis, product-page visits, email clicks or bookings. Review them on a regular schedule and keep the definitions unchanged unless you document the change.

For example, a lower visitor count alongside the same number of completed purchases may indicate that the new system counts visits more narrowly. A lower checkout-to-purchase rate alongside more failed payments may point to payment status rather than weaker intent. These are hypotheses to investigate, not conclusions supplied by the graph.

No. Copy the underlying figures and definitions instead. Recalculate the rate only when the new numerator and denominator match the old ones closely enough to compare.

Save dated screenshots with every visible filter, download invoices or order reports if available, and write down the figures and definitions manually. Mark missing fields as unavailable rather than presenting them as exact.

Use a complete comparison period that fits your sales rhythm. A short period can be distorted by a launch, payday, seasonality or a single customer. The important rule is to compare equivalent periods and record unusual events.

Set up your storefront on store.fan and begin the move with a written measurement baseline.

Start your trial
#analytics#migration#getting-started#digital-selling

Turn your knowledge into income

Launch your Store.Fan in minutes — sell digital products, courses, and calls straight from your bio. Free to start.