Revenue by Landing Page

Revenue by Landing Page shows how much revenue each entry page brought in, and what each visit that started there was worth.

How It’s Calculated

Each row is one entry page: the address of the first page view in a session inside the date range. The table lists every address, with the highest Revenue first. The columns are:

• Entry Page: the full address, including anything after a ?, such as UTM tags.
• Sessions: visits that started on that page.
• Orders: the number of those sessions that ended in a purchase.
• Conversion Rate: Orders divided by Sessions.
• Revenue: the value of those purchases. It is the total of the Shopify order each purchase links to: items minus discounts, plus shipping, plus tax that isn’t already in the prices, minus refunds. Where das Pixel couldn’t match an order, it uses the value it saw at checkout.
• Revenue per Session: Revenue divided by all of the page’s sessions, including those that didn’t buy.

The address includes the part after the ?, so the same page reached through 2 links with different tags is 2 rows. Sessions with no address recorded show as (unknown). das Pixel records the address only for visitors who allowed marketing, while Track Marketing is on.

Select a row to open Sessions Explorer with that entry page and date range.

Summary Cards

The cards above the table are Revenue, Revenue per Session, Orders and Order Match Rate. They cover every row. With Compare on, the first three show their change.

Order Match Rate is the share of purchases valued from their Shopify order instead of the checkout value.

When you have entered unit costs, 3 more columns appear: Gross Profit, Profit per Session and Cost Coverage.

• Gross Profit: Revenue minus the unit cost of the items sold. It counts only orders that matched a Shopify order and where every item has a cost.
• Profit per Session: Gross Profit divided by all of the page’s sessions.
• Cost Coverage: the share of the items sold that have a unit cost.

See How to Enter Your Costs.

What Counts

• Visitors who declined analytics cookies, or who opted out of the sale or sharing of their data while Require Sale-of-Data Consent is on, aren’t recorded. Known bots are left out.
• Only events inside the date range count, in your store’s time zone.
• Turn on Live to refresh the report every 30 seconds. Without it, a figure can be up to 10 minutes old.

A warning shows above the report when das Pixel saw less than 70% of your online-store orders in the last 30 days. This report has no Segment, Sales Channel or Filters control. Pinned to a dashboard, it can show a bar chart of the 10 entry pages with the highest Revenue per Session.

What Good Looks Like

There’s no target. Revenue per Session puts pages of different sizes on one scale. A page with few sessions can have a very high or very low figure from a handful of visits.

What to Do About It

• A page with a high Revenue per Session: send more traffic to it, and link to it from your main pages.
• A page with many sessions and a low Revenue per Session: check what the page asks visitors to do next, and compare it with Entry Pages for its bounce rate.
• The same page in several rows: add the rows together before you compare pages.

Get AI Insight at the top of the report asks Copilot for a short read of it.

Where to Find It

• Revenue by Landing Page: open Reports and look under Web Analytics.