> For the complete documentation index, see [llms.txt](https://help.recart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.recart.com/general/session-ids-explained.md). # Session IDs Explained Explains the Session ID Recart adds to order notes and how it's used to attribute revenue accurately. How Recart uses the Session ID on your orders to attribute revenue accurately. Once you install Recart, you'll notice a **Session ID** being added to the notes section on your order pages. This is completely normal — it's how Recart tracks orders and calculates your attributed revenue accurately. #### Why is a Session ID added to orders? From the point you have Recart installed, a **Session ID** is added to each store visit and order. This doesn't mean every order is attributed to Recart — the ID simply helps our app identify which Shopify order belongs to which **Recart subscriber**, which is how **attributed revenue** is **tracked accurately**. ![RecartSessionID](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2Fek6kMmeNnE9dKmtQcAEM%2Fsession-ids-explained-1.png?alt=media) If the app can't identify a Recart subscription from the ID, the sale won't be attributed, but the Session ID will still be visible on the order page. #### Seeing a Shopper ID on an older order? Recart previously added a Shopper ID to orders alongside the Session ID. This was phased out in July 2026 and is no longer added to new orders. Orders placed before then may still show a Shopper ID — this is expected, and it's safe to ignore. It doesn't affect your Session ID, your tracking, or your revenue attribution. ![](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FbkOCyyElCFP9RMbTnuey%2Fsession-ids-explained-2.png?alt=media) If you have any questions, do not hesitate to [contact the Recart Support team.](/contact-recart-support.md) We'd be happy to help! --- # 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://help.recart.com/general/session-ids-explained.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.