Make Local for Global Logo

Article information

Table of content

How to Compare Ecommerce Conversion Rates by Traffic Source

Learn how to compare ecommerce conversion by traffic source using a consistent session denominator, completed orders, and a weighted blended rate.

Make Local for Global
How to Compare Ecommerce Conversion Rates by Traffic Source

Two traffic sources can bring the same number of visits and produce very different numbers of orders. A third can look impressive because its rate is high, even though it reaches fewer people. To compare them fairly, use the same reporting period, the same session definition and the same completed-order event. Then calculate expected orders for each source and divide their combined orders by combined sessions.

This guide explains how to compare ecommerce conversion by traffic source, how to read a blended rate, and what to check before changing a campaign or store page. The free Conversion Lab can organise the arithmetic into a source breakdown and a clearly labelled what-if. It does not connect to analytics or predict future sales.

Compare your three main traffic sources

Enter sessions and completed-order rates for organic search, paid campaigns, and email or returning visitors. See expected orders, a blended rate, and illustrative gross sales in £.

What does ecommerce conversion rate mean?

A conversion rate is a chosen action divided by an eligible audience or visit count, expressed as a percentage. For the examples below, the action is a completed order and the denominator is sessions attributed to a traffic source:

Order conversion rate = completed orders ÷ sessions × 100. Keep the event and denominator consistent when comparing sources. A product view, add-to-basket event, checkout start and completed order are different actions, so they should not be mixed in one rate.

Analytics products can report users, sessions, events or transactions. Those measures answer different questions. A returning person may have several sessions, and a transaction can contain several items. Decide which measure answers your question before comparing channel results. For a store-level order rate, sessions and completed orders are a practical starting point, provided your analytics and order records are configured consistently.

How the blended conversion rate works

The blended rate is not the simple average of the rates for each source. Each source contributes a different number of sessions, so calculate its expected orders first. Add those expected orders, then divide by all included sessions.

Diagram showing 1,000 organic sessions at 2%, 500 paid sessions at 1%, and 200 email or returning sessions at 5%, combining to 35 expected orders and a 2.06% blended rate.
A weighted blended rate reflects the size of each source, not just its percentage.
Traffic sourceSessionsCompleted-order rateExpected ordersIllustrative gross sales at £35 AOV
Organic search1,0002%20£700
Paid campaigns5001%5£175
Email and returning2005%10£350
Blended total1,7002.06%35£1,225

Here, organic search contributes 20 expected orders, paid contributes five, and email or returning visits contribute 10. Together that is 35 orders from 1,700 sessions, or about 2.06%. The simple average of 2%, 1% and 5% is 2.67%, which overstates the blended result because it treats the 200-session source as if it were as large as the 1,000-session source.

Expected orders can be fractional in other examples. For instance, 500 sessions at 1.5% gives 7.5 expected orders as an arithmetic average. It does not mean a store literally receives half an order. Actual orders are whole events and can vary from month to month.

Keep the comparison fair

Before drawing a conclusion, check that the figures describe comparable periods and definitions. A paid campaign that ran for only a week should not be compared casually with a full month of organic traffic. A promotion, out-of-stock product, broken tracking tag or different attribution rule can also change the numbers without the underlying customer journey changing in the same way.

Four measurement checks for comparing traffic sources: use the same period, the same session denominator, completed orders, and reviewed attribution rules.
Check the data definitions and context before interpreting a source difference.
  • Same dates: choose a period long enough to include ordinary buying patterns and note seasonal or campaign effects.
  • Same denominator: compare sessions with sessions, not sessions in one channel and users in another.
  • Completed orders: distinguish the purchase event from product views, basket additions and checkout starts.
  • Attribution: understand the rule used to assign a sale to a source. Some methods credit one source; others distribute credit.
  • Store context: record changes to price, stock, delivery, offers, site speed and checkout that could affect the period.

Google Analytics 4 provides a useful example of why the event definition matters. Its ecommerce measurement guidance distinguishes events such as view_item, add_to_cart, begin_checkout and purchase. The GA4 Checkout journey report depends on configured ecommerce events, including begin_checkout, shipping and payment steps, and purchase. A custom funnel can help inspect sequential steps, but a funnel-stage rate is not interchangeable with a completed-order rate by traffic source.

For additional context, see Google’s ecommerce measurement guide, its documentation for the Checkout journey report, and Funnel exploration. These explain measurement setup and report behaviour; they do not establish a universal conversion benchmark for every shop.

How to use a traffic-source what-if

A what-if is a way to make an assumption visible. Suppose a paid source has 500 sessions and a 1% completed-order rate. At an average order value of £35, that is five expected orders and £175 in illustrative gross sales before costs. If you model a 0.5 percentage-point increase, the assumed rate becomes 1.5%, or 7.5 expected orders. The arithmetic difference is 2.5 expected orders and £87.50 in gross sales.

A 500-session example compares a 1% baseline order rate with a 1.5% what-if rate, showing 5 versus 7.5 expected orders and a difference of 2.5 expected orders.
A half-percentage-point assumption is not the same as a 50% observed improvement.

Notice the language: the result is an assumption to investigate, not a claim that a redesign or campaign will create those orders. A percentage-point change is the direct difference between two rates. In this example, moving from 1% to 1.5% is plus 0.5 percentage points and a 50% relative increase. They describe different comparisons. Use the unit that matches your evidence.

Turn one assumption into a measured question

Use the lab to compare each source on the same basis, then choose one source and one change to investigate. The what-if keeps expected values separate from observed orders.

Read the result, then decide what to test

A high conversion rate is a useful clue, not a complete performance verdict. A smaller source may have a higher rate but provide few orders. A larger source may have a lower rate yet account for more orders. Gross sales also leave out advertising spend, product cost, fulfilment, payment fees, refunds, VAT treatment and staff time, so they are not profit or a return-on-ad-spend calculation.

Use three questions to move from comparison to action:

  • Is the difference trustworthy? Check event setup, channel grouping, attribution and sample size before interpreting a small change.
  • What could explain it? Review the landing page, audience, product availability, price, delivery offer and campaign message for the source in question.
  • What will you observe next? Write down the change, measure, period and other conditions to monitor before making the change.

Change one meaningful factor where practical. If you change the advert, product page, price and delivery promise together, the next month may be different, but it will be hard to know why. Record the before-and-after period and any context that might affect the comparison. When traffic is limited, allow for natural variation and avoid treating a short run as conclusive evidence.

Common mistakes to avoid

  • Averaging rates without weighting: calculate expected orders from each source, then divide by total sessions.
  • Comparing different actions: do not compare a product-page add-to-cart rate with another source’s completed-order rate.
  • Calling expected orders actual: fractional results are a planning calculation, not observed transactions.
  • Calling gross sales profit: order value does not deduct costs, fees, taxes, refunds or advertising.
  • Assuming attribution is exact: tracking gaps and attribution choices can shift credit between channels.
  • Assuming a change caused the difference: a before-and-after result can be affected by other conditions. Treat it as evidence to review, not proof on its own.

A practical comparison checklist

  • Choose one reporting period and write down the dates.
  • Use sessions and the same completed-order definition for every source.
  • Check how your analytics groups traffic and attributes orders.
  • Calculate expected orders per source before the blended rate.
  • Keep average order value in £ on one consistent basis.
  • Label any rate change as a what-if until observed data supports it.
  • Choose one next test, record its measure and review it after a suitable period.

Frequently asked questions

Should I use sessions or users for conversion rate?

Use the measure that matches your question and keep it consistent. Sessions are useful when comparing visits attributed to sources. Users answer a person-level question and can have multiple sessions. If a dashboard reports a different denominator, do not compare its rate directly until you understand the definition.

Why is my blended rate not the average of channel rates?

Because sources have different session volumes. Multiply each source’s sessions by its rate to estimate orders, add those values, and divide by the total sessions. This weights each rate by its share of visits.

Can one source have a higher rate but fewer orders?

Yes. A smaller source can convert a larger share of its sessions and still contribute fewer total orders. Review both the rate and the expected or observed order count, along with cost and business context.

Does a higher conversion rate mean more profit?

Not by itself. Conversion Lab estimates gross sales from expected orders and an average order value you enter. It does not deduct product, fulfilment, advertising, payment, tax or refund costs. Use separate cost data to evaluate contribution or profit.

What does a percentage-point test show?

It shows the arithmetic result if one source’s rate changed by the number of percentage points you enter and other inputs stayed fixed. For example, 1% to 1.5% is an increase of 0.5 percentage points. It is not proof that the change will happen.

Make your next comparison easier to review

Use Conversion Lab to set out the same-period source figures, record one what-if, and download a three-page review for your next planning session.

If you want a practical structure for acting on what you find, explore the Ecommerce Basics Mini Course and the guide to estimating ecommerce orders from website traffic. For help planning your store, you can also talk with MLFG.

Sources and further reading

Share Article:

PREFERRED SOURCE

Keep finding us on Google

Like what you’re reading? Add Make Local for Global as a preferred source on Google to see more of our articles when you search.

Recommanded

Ready to Start Your Online Business?

Build your online presence without having to figure out everything yourself.

Qualifying / Questionnaire Form
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5

Answer a few quick questions and I’ll point you in the right direction.