> For the complete documentation index, see [llms.txt](https://docs.intelligems.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intelligems.io/getting-started/opportunity-audit.md). # Opportunity Audit {% hint style="info" %} **Opportunity Audit is in beta.** It's available to new Intelligems installs first. If you're an existing customer and want access, [contact support](https://portal.usepylon.com/intelligems/forms/intelligems-support-request). {% endhint %} ### Overview Opportunity Audit tells you what to test first. It reads your store's data, finds the step in your funnel where you lose the most shoppers compared with similar stores, and recommends three tests to close that gap. Every idea explains why it's worth running, and you can build any of them in one click. \[Screenshot of the full audit page, with the chat on the left and the audit on the right] *** ### Running an audit 1. Click **Opportunity Audit** in the left navigation. If you just installed Intelligems, you'll land here after onboarding. 2. The audit starts on its own and pulls in your store data. 3. Review what it found about your store and your funnel. 4. Add any context you want the recommendations to consider, or skip this step. 5. Click **Create recommendations**. The audit returns three test ideas. 6. Open an idea to see the details, then save it or build the test. *** ### What's in your audit Your audit reads top to bottom, from what we know about your store, to where your biggest opportunity is, to what to test. | Section | What it shows | | ----------------------- | --------------------------------------------------------------------------------------------------- | | **Store metrics** | Revenue, orders, and average order value (AOV) for the last three months. | | **Brand style** | Your store's colors, fonts, and overall look. Content test ideas use them so changes fit your site. | | **Summary** | A short read on those numbers and the biggest opportunity in your funnel. | | **Funnel** | How shoppers move from visit to purchase, compared with similar stores. | | **Insight** | The funnel step where you trail similar stores the most, in plain numbers. | | **Ideas worth testing** | Three recommended tests aimed at that step. | The insight drives your recommendations. Say only 52% of shoppers who add to cart go on to begin checkout, and similar stores do better. Most of your ideas will then focus on getting more shoppers from cart to checkout. *** ### Shaping the recommendations Before you click **Create recommendations**, you can tell the audit anything it should take into account. Share your goals, what you most want to test first, or something the data can't show, like a new collection launching next month. If you don't add anything, the audit works from your funnel insight alone. > ""We want to raise AOV before Black Friday, and we'd rather start with product pages than checkout."" *** ### Reviewing an idea Click an idea in the chat, or scroll down to **Ideas worth testing**, to see its details. * **What to test and where.** For example, adding a ""Buy 2, get 1 free"" line under each price in your homepage product carousel. * **A screenshot of the page today.** It's marked to show where the change would go. It's not a preview of the change itself. * **Why it's worth testing.** How the idea ties back to your funnel, plus anything you should know before you build it. \[Screenshot of an idea's detail view] *** ### Saving ideas Click **Save** on any idea you want to come back to. Saved ideas live on your **Dashboard** under **Saved ideas**, and everyone on your account can see them. From **Saved ideas**, open any idea to see its full detail, or click **Build test**. \[Screenshot of the Saved ideas table on the Dashboard] *** ### Building a test Click **Build test** on any idea, in the audit or from **Saved ideas**. Intelligems sets up a draft experience based on the idea. Review the draft, make any changes, and start it when you're ready. The audit never launches a test for you. *** ### Your audit and chat You have one audit at a time. It stays put when you leave the page, so you can come back and pick up where you left off. Keep chatting to ask for new ideas or dig into one you like. To start over, open the dropdown at the top of the audit and choose **Restart audit**. This runs a brand-new audit and replaces your current one. Your saved ideas stay on your Dashboard. {% hint style="info" %} Restarting replaces your current audit and chat. History of past audits and chats isn't available yet, so save any ideas you want to keep before you restart. {% endhint %} *** ### Things to note Opportunity Audit is in beta, and it's changing fast. * **Ideas start from best practices.** They'll get more specific to your store as the audit improves. * **Saved ideas don't update on their own.** If your store has changed since you saved an idea, check that it still fits before you build it. * **We can't see other apps in your checkout.** Intelligems can't tell what other apps run in your checkout or post-purchase flow, so check for overlap before you build those ideas. * **It can be wrong.** If an idea doesn't fit your store, skip it and [let us know](https://portal.usepylon.com/intelligems/forms/intelligems-support-request). Beta feedback shapes what the audit recommends next. *** ### Tips * **Add context first.** Even one line about your goals sharpens the ideas. * **Start with a low-friction idea.** A test you can launch today gets you results sooner than a bigger one stuck in approvals. * **Save what you're not ready for.** Your team can find saved ideas on the Dashboard anytime. * **Keep the conversation going.** Ask for ideas on a different page, or for more detail on one you like." --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.intelligems.io/getting-started/opportunity-audit.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.