Use Journeys to follow recorded visits and find points that deserve a closer look. Use Revenue to compare purchase interest with recorded outcomes and, when available, Cedros Pay revenue. Together, these reports help you choose what to investigate or improve.
For the wider dashboard and traffic-source definitions, see Understanding your site analytics.
Open Journeys or Revenue
- Open Dashboard → Insights and select View full analytics.
- Choose Last 7 days, Last 30 days, Last 90 days, Last 12 months, or All time. The initial selection is Last 30 days.
- Open Journeys to explore visits, or Revenue to review purchase activity and money.
- Wait for the report to finish updating, then check the period and any notices beside the figures before comparing them.
Start with a question you can act on: “Are visitors getting stuck on our enquiry form?” or “Did more interest in pricing lead to more recorded purchases?”
Follow a recorded visit
Journeys lists recent visits with a short description of the strongest recorded action. Select a visit to expand its page path, activity, and any warning signals. Open Event timeline for the available event detail.
Use the filters to focus your review:
- Converted includes recorded outcomes such as a successful form submission, purchase, booking attendance, or signup. It does not mean every visit in this group produced a sale.
- Needs review highlights recorded form validation errors, failed submissions, or repeated-click signals. Investigate the affected page before deciding what caused them.
- Engaged includes activity such as reading, searching, form interaction, or CTA clicks. Engagement alone does not establish purchase intent.
- Limited activity means little engagement or outcome activity was recorded. It does not prove the visitor disliked the page or immediately left.
A visit with a recorded conversion can also contain errors. Expand successful visits as well as those marked Needs review when looking for obstacles.
The path shows recorded page steps. Consecutive views of the same route can appear as one step with a repeat count; returning after another page appears as a separate step. Available time, scroll, click, and form details help explain what happened on each page.
This is a recent-visit sample, not the full history of everyone who used your site. Show earlier visits expands the list when available, up to 50 visits. Filter counts describe the loaded list. A label such as “Visit 2 of 3 in this list” refers to that list, not the visitor's lifetime history. Visitor identifiers also do not establish a person's name or link all of their devices.
The event timeline is a limited preview, not a video replay or a guaranteed complete record. Read any truncation notice before concluding that an action never happened.
Compare recorded activity
Above the recent visits, activity panels summarize recorded sessions across the selected period. These totals cover a wider scope than the recent-visit list.
Recorded visit activity, Call-to-action activity, and Search activity show independent counts. Each percentage uses the same Tracked sessions baseline, including sessions that have events but no recorded page view. The rows do not establish that the same people completed each action in order.
For example, if 20 sessions included a CTA click and 5 included a successful form submission, that alone does not show that 5 of those 20 clickers submitted the form. Look at individual journeys for examples of the path, and use the totals to identify activity worth investigating.
Keep sessions and events separate: one session can contain several clicks or searches. Repeated-click signals, zero-result searches, and failed form activity are useful starting points for checking the page; they are not a diagnosis by themselves.
Understand what attribution tells you
Attribution connects an action or payment with recorded context, such as a referring site, a page, or a product. The available context helps you find patterns, but it does not prove what persuaded someone to buy.
In a journey, the entry source describes how that recorded visit began. The page path shows activity captured during the visit. A completed purchase elsewhere in the reports may have no matching journey, and the final page in a path should not automatically receive credit for a sale.
On Revenue, Pages that drive action ranks pages by recorded CTA clicks. Use it to find pages that prompt a next step, rather than to rank sales revenue. Customer action events lists reported conversion activity from connected extensions; read the event name before treating it as a purchase.
When Cedros Pay supplies Top products or Top pages, those lists show the product or page attribution available in its payment records. A page missing from a list does not establish that it contributed nothing to sales.
If a page deserves closer inspection, use Checking the performance of a page, post, or doc to review its traffic, attention, and heatmap.
Read purchases, interest, and revenue separately
The Revenue headline tiles summarize recorded purchase outcomes:
- Gross revenue is the recorded purchase amount in the displayed currency.
- Net revenue subtracts recorded refunds from gross revenue. It is not profit or a payout balance.
- Refunds shows the refunded amount; the supporting count describes recorded refund events.
- Purchases counts recorded completed purchase outcomes, rather than distinct customers.
- Average order uses the gross amount and purchase count with complete revenue details in the displayed currency.
- Purchase intent counts recorded pricing or checkout views and purchase-interest events. Repeated activity can contribute more than once.
Read the currency beside monetary figures. Additional currencies appear under Also collected; the report does not exchange them into one combined total. Purchase and refund counts can span currencies. A recorded purchase with incomplete amount or currency information can contribute to the count without contributing to the money totals.
Purchase journey compares recorded purchase interest with completed purchases. The completion detail identifies server-verified outcomes or activity reported by extensions. Its percentage compares aggregate counts; it is not a verified percentage of unique interested visitors who later bought. Repeated events and missing tracking can make those counts difficult to compare.
Other outcomes, such as confirmed newsletter subscriptions or attended bookings, can also appear. Use their labels to distinguish them from paid purchases.
Check the Cedros Pay period
When Cedros Pay is ready and your account has access, the Revenue report includes its payment summary, daily revenue chart, and available product or page breakdowns. Subscription figures appear when subscription data and active subscribers or recurring revenue are available.
For 7-day, 30-day, 90-day, and All time selections, the Pay panel follows the matching reporting window. Last 12 months is different: the Pay panel shows year to date, with a notice explaining the difference. Check that notice before comparing it with the analytics totals above.
A long-period chart may show only the latest available days while the headline totals cover the panel's full period. Read the chart subtitle as well as the selected window. Net revenue and refund tiles in the Pay panel appear when refunds or a difference between gross and net make them relevant.
The analytics outcome summary and Pay payment summary are separate views. Differences can reflect the reporting period, currency, available payment details, or which outcomes were recorded. Match those first when investigating a discrepancy; do not add the two summaries together as extra revenue.
Resolve missing or stale results
Journeys is empty, but page views exist. Page-view totals alone cannot reconstruct visits that lack the required session detail. Check the period and whether built-in analytics is enabled in Settings → Analytics. Consent choices and blocked requests can also leave gaps.
Results failed to refresh. Use Retry analytics, or Try again in the Pay panel. If a notice says the last successful results are being shown, those figures do not confirm that the latest refresh succeeded.
The Pay panel asks for setup or access. Follow its setup notice, or ask the site owner to check Pay access. Access to site analytics does not automatically grant access to payment reports. See feature access.
A total looks unexpectedly low or high. Check the selected period, currency, whether you are counting visits or events, and whether the list is only a recent sample. Compare similar periods and allow time for new activity after a change. Use the reports to form a specific question, then inspect the relevant page, form, or payment record before drawing a conclusion.