> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/the-admin-panel/statistics/statistics-app/network-table-export-app.md).

# Network table export (App)

## How to download the Networking table statistics 

1. Open the Admin panel
2. Go to Statistics --> App statistics
3. Click on 'Export'
4. Select 'Network table export' from the drop-down.
5. An e-mail will be sent to your e-mail address including an Excel file with all booth view statistics. 

### How to read the Networking table statistics export

When opening the Excel with the networking table statistics, multiple tabs are visible. 

The first tab is called '**Overview**' and shows an overview of all the different networking tables. It shows their: 

* Name (of the table)
* Start date (DD-MM-YYYY HH:mm:ss)
* End date (DD-MM-YYYY HH:mm:ss)
* Location
* Amount of Subscriptions 
* Maximum of Subscriptions
* Description

The other tabs are named after the individual network tables. These tabs show who joined the relevant networking tables (*Name, E-mail, Company, Function*). 


---

# 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://knowledge-base.letsgetdigital.com/the-admin-panel/statistics/statistics-app/network-table-export-app.md?ask=<question>&goal=<user_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.