> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/install-connect-and-integrate/integrations/olo-integration-delivery-orders/filter-delivery-events-olo-integration.md). # Filter Delivery Events (Olo Integration) You can view third-party delivery app data on the Events page if you are subscribed to our [Olo integration](/docs/install-connect-and-integrate/integrations/olo-integration-delivery-orders/olo-integration-overview.md). See the following sections for a few methods you can use to search and filter your delivery events. ### Default Delivery Reports You can select a variety of default delivery reports to filter your delivery events. Select the [Reports Panel](/docs/review-events-and-save-evidence/events/events-page-user-interface-guide.md#reports-panel) (located near the top-left of the Events page), then select any of the following default delivery reports to filter your delivery data on the Events page: * **Olo - All Orders:** All orders received via Olo. * **Olo - Delivery Orders:** All delivery orders. * **Olo - UberEats Orders:** All orders made through UberEats. * **Olo - DoorDash Orders:** Orders made through DoorDash. * **Olo - GrubHub Orders:** Orders made through GrubHub. * **Olo - PostMates Orders:** Orders made through PostMates. * **Olo - Chargebacks**: Chargeback orders. Please reach out to your Solink Customer Success representative if these reports are not available. **Note**: See [Create a Report](/docs/understand-your-business/search-and-save-reports/create-a-report.md) for information on how to create custom reports. ### Search Terms You can type a few search terms in the Events search bar to find delivery events: * Type "delivered" to filter for delivery events that have occurred. * Type "delivery" to filter for delivery events in progress, if any. * Type "chargeback" to filter for chargeback events. **Note**: See [Search Bar on the Events Page](/docs/understand-your-business/search-and-save-reports/search-and-filter-events.md) for a detailed overview of how you can customize your search and use filters for all of your events. ### Histogram You can also view your delivery order data with the **histogram** at the top of the Events page: The data displayed in the histogram changes whenever you sort the data; for example, if you filter the data by date - whether it be a certain day, week, month or year - the histogram visually displays data within the selected timeframe. Hover over the individual bars in the histogram to see the number of transactions completed in a given period of time. **Note**: For more information on the histogram panel, see [Events Page: User Interface Guide](/docs/review-events-and-save-evidence/events/events-page-user-interface-guide.md#histogram-panel). ​ --- # 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.solink.com/docs/install-connect-and-integrate/integrations/olo-integration-delivery-orders/filter-delivery-events-olo-integration.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.