> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getjurni.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Conversion Step Performance

> Understand how Jurni measures the shopper journey across sessions, product-page activity, add to cart, checkout, and purchase so you can identify meaningful drop-offs.

Conversion-step reporting helps you understand where shoppers progress and where they drop off between landing on a Jurni experience and completing a purchase.

## Typical commerce journey

A common Jurni commerce journey can be read as:

`Session → Product interaction → Add to Cart → Checkout → Purchase`

Not every experience uses every step in the same way, but the progression is useful for diagnosing where performance is changing.

## Sessions

Sessions represent the traffic entering the experience and act as the denominator for many rate-based metrics.

If session counts are unexpectedly low, check the traffic destination, Smart Link or experiment routing, date range, and tracking setup before diagnosing the page itself.

## Product interaction / PDP step

Some experiences contain a dedicated product-detail step or product interaction before add to cart. Use this stage to understand whether shoppers are engaging deeply enough with the product or offer to continue.

A large drop before product interaction can point to weak message match, slow engagement, or unclear page structure.

## Add to Cart

AddToCart is a strong purchase-intent signal. When the rate is low, inspect:

* Offer clarity
* Pricing and savings
* Product/variant availability
* Buy Box usability
* CTA prominence
* Mobile experience

<Info>
  A button click is not automatically the same thing as an AddToCart event. For commerce analysis, confirm that the product action successfully adds the intended item to cart.
</Info>

## Checkout

Checkout measures shoppers who progress into the supported checkout flow.

When add-to-cart is healthy but checkout rate is low, inspect:

* Slide-out cart behavior
* Cart provider configuration
* Unexpected products or quantities
* Subscription/selling-plan state
* Discounts or gifts
* Checkout CTA behavior

## Purchase

Purchase or Order is the completed conversion used for CVR and revenue reporting.

If checkout volume is healthy but purchase completion drops, investigate checkout-specific factors such as payment methods, shipping, taxes, discount behavior, or store-level checkout changes.

## Read drop-offs as rates

Raw counts naturally get smaller at each stage. Use rates to decide whether the drop is unusual.

For example:

* **Add-to-Cart Rate** = sessions with add to cart ÷ sessions
* **Checkout Rate** = sessions reaching checkout ÷ sessions
* **CVR** = orders ÷ sessions

## Compare variants

In an experiment, compare the same conversion steps by variant. A variant can improve early engagement while hurting checkout or AOV, so look at the full path before declaring the change successful.

## Related guides

* Experience analytics
* Analytics overview
* Metrics glossary
* Cart and checkout behavior
* Buy Box overview
* Reading experiment results


## Related topics

- [Analytics Overview: Experiences & Experiments](/analytics-reporting/overview.md)
- [Experience Analytics](/analytics-reporting/experience-analytics.md)
- [Launch your first Jurni campaign](/academy/start/first-campaign.md)
- [Set Up Slack Performance Reports](/notifications/slack-reports.md)
- [Custom Events and Downstream Tracking](/analytics-reporting/custom-events.md)