Pages, Entry Pages and Exit Pages

The Pages card in Revenue First Analytics has three tabs. Pages lists every URL path with the visitors who viewed it, the revenue from those visitors and their average scroll depth. Entry Pages shows where sessions started, with revenue credited to the landing page of the buyer’s first visit. Exit Pages shows the last page of each session. Click any row to filter the whole dashboard by that page.

What do the three tabs show?

A pageview is one page load recorded by the tracking script, and a session is a run of pageviews by one visitor that ends after 30 minutes without activity. The three tabs look at the same data from different angles.

The attributed session is the buyer’s first known session, explained below. The exit page is updated with every pageview, so for a visitor who is still browsing it is the page they are on now.

What does each metric mean?

• Visitors: as in the table above. Each visitor counts once per row, however many times they viewed the page.
• Revenue and Orders: conversions (WooCommerce orders and EDD payments) recorded in the range, after refunds, credited to the row as described above. Orders appear in the hover tooltip and in the View details table.
• Conversion rate (CR%): Orders divided by Visitors. Revenue/visitor (Rev/vis): Revenue divided by Visitors.
• Scroll (Pages tab only): the average of the deepest point each visitor scrolled to, as a percentage of the page height, over pageviews where a scroll position was recorded. A page that fits in the viewport counts as 100%. The tooltip calls it Avg scroll depth.
• Time on page is recorded per pageview (the time the tab was visible, up to 30 minutes), but it is not shown per page in this version. It feeds the Session time tile at the top of the dashboard.

How is revenue attributed to a landing page?

Revenue First Analytics uses first touch: when an order reaches the conversion status chosen in Settings, the plugin looks up the buyer’s earliest session and saves that session with the order. The Entry Pages tab credits the revenue to the entry page of that session, so the landing page of the first visit gets the sale even when the purchase happened days later and started on a different page. The Pages and Exit Pages tabs use the same session, so revenue there means “pages seen during the buyer’s first visit”.

This depends on the plugin recognizing the buyer across visits. In Full tracking, and in Consent mode after the visitor consents, the _rfa_vid cookie makes that possible. In Privacy mode, or in Consent mode before consent, visitors are identified by a hash that changes every day, so the first session can only be found when the visit and the order happen on the same day. Orders with no tracked visit at all appear as Unattributed in the Channel tab and are not credited to any page. See How Sales Are Attributed to Traffic Sources and Choosing a Privacy Mode.

How are URLs recorded?

The tracking script sends the path of the page, and the plugin cleans it before storing it:

• Only the path is kept, for example /blog/best-sellers/. The query string and the hash are removed, so /shop/?orderby=price and /shop/ are one row, and /pricing/#faq is /pricing/. UTM parameters are stored separately and do not create extra page rows.
• Letter case and trailing slashes are kept as the browser sent them. /About and /about, or /pricing and /pricing/, are separate rows.
• Percent-encoding is kept, so a page named /café/ appears as /caf%C3%A9/. Characters that are not valid in a URL path are dropped, and paths are cut at 1024 characters.
• Navigations inside JavaScript apps that change the path with the History API are recorded as new pageviews. Changes to the hash alone are not.

How do you use these reports?

Which blog posts bring sales?

1. Open the Entry Pages tab and click the grid icon (View details).
2. Sort by Revenue or CR% by clicking the column header, and type part of the path (for example /blog/) in the search box to keep only posts.
3. To see only sales from search, first click Organic search in the Channel tab, then repeat.

Where do visitors leave?

The top rows of Exit Pages are the pages where most sessions end. The home page and product pages are normal there; a cart or checkout page near the top is worth a look. Open the Pages tab and compare the Scroll value of a long page with the rest of the site to see whether visitors read it before leaving. For a step-by-step view of checkout drop-off, build a funnel; see Building Conversion Funnels.

Which pages did buyers of one product see?

Click the product in the Products card. The Pages card now lists only pages viewed by visitors who bought that product. Filters work the same way for countries, devices and campaigns; see Filtering Reports by Channel, Page, Country or Device.

What are the limitations?

• Pages identified only by a query parameter, such as /?p=123 or /?s=shoes, are reported as /.
• Revenue is credited only to pages of the buyer’s first session. A page they viewed on a later visit before ordering gets no revenue, even though it may have helped.
• Visitors in Entry Pages count every session in the range, while Revenue uses the first session only. A returning customer whose second visit started on /sale/ counts as a visitor for /sale/, but their order is credited to the landing page of their first visit.
• In Privacy mode, first-visit attribution works within a single day.
• The card shows the top 10 rows by visitors and the View details table up to 50.

For the tiles above the cards, see Dashboard Overview: Metrics, Chart and Date Ranges. To track how far visitors scroll as a goal, see Creating Goals: Events, Page Visits and Scroll Depth.