> For the complete documentation index, see [llms.txt](https://order-editing.gitbook.io/oe-help-book/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://order-editing.gitbook.io/oe-help-book/analytics/use-analytics-to-optimise-your-store.md). # Use Analytics to optimise your store Order Editing tracks every customer interaction, every edit made, and every dollar earned through post-purchase engagement. This visibility allows you to continuously optimize your setup, maximize revenue, and deliver a better customer experience. *** ### Two Analytics Dashboards #### Self-Service Edit Analytics Understand how customers interact with each editing feature. Which App Blocks drive engagement? Where do customers drop off? Which features generate value? See impressions, interactions, completions, and success rates for every feature—from Primary Upsell to Shipping Address changes to Discount Codes. Explore App Block Analytics *** #### Upsell Strategy Analytics Measure revenue performance for each upselling approach. Track conversion rates, revenue generated, product performance, and trends for every strategy. Identify which products drive the most revenue and optimize underperforming strategies. Explore Upsell Strategy Analytics *** ### Continuous Optimization Successful merchants use analytics to refine their approach through a simple cycle: **measure** current performance, **identify** what works, **test** improvements, and **refine** based on results. **Weekly:** Review engagement rates and investigate any drops—quick adjustments prevent revenue losses. **Monthly:** Analyze which upsell strategies generate the most revenue and prioritize optimization efforts. **Quarterly:** Examine long-term trends, disable underperforming features, and expand high-performing offerings. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://order-editing.gitbook.io/oe-help-book/analytics/use-analytics-to-optimise-your-store.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.