> For the complete documentation index, see [llms.txt](https://docs.foxmetrics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.foxmetrics.com/getting-started/setting-up-an-account/applications.md).
# Applications
Applications are databases or storage units that can hold data from one or more sources. They provide a simplified way to break down your [**account** ](/getting-started/setting-up-an-account/accounts.md)into separate units.
People use applications to represent multiple products, websites, apps, marketing campaigns, and other aspects of their businesses.
For example, let’s say ABC Group sells clothes, shoes, handbags, perfumes, and accessories in each of its stores. The company can use applications to divide [**each account**](/getting-started/setting-up-an-account/accounts.md) to represent each store section.
They just have to create 5 different applications in each account to represent each of those store sections. This way, they can track the number of shoes or handbags sold separately on each application.
Similarly, a marketer can use applications to represent different campaigns or websites. So, you can dump data from your campaigns, web app, mobile apps, and social media campaigns into individual applications.
{% hint style="warning" %}
But you don't necessarily need more than one application. The downside of having multiple applications is that you can’t report across applications. Each application has its unique database so data from multiple applications can’t interface.
{% endhint %}
If you want to get a unified report; consider using one application for all of your data and instead [**create multiple dashboards**](/features/dashboards/creating-dashboards.md) to track various campaigns, products, website data, and others.
## Application Columns
There are four columns on the application list section.
* [**Details**](/getting-started/setting-up-an-account/applications.md#details)
* [**Last published**](/getting-started/setting-up-an-account/applications.md#last-published)
* [**Usage (month)**](/getting-started/setting-up-an-account/applications.md#application-usage-percentage)
* [**Modified**](/getting-started/setting-up-an-account/applications.md#modified)
## **Details**
This column is where you find the name of the application and the associated URL. You can [update ](/getting-started/setting-up-an-account/managing-applications.md#how-to-create-a-new-application)the details (name and website of your applications).
## Last Published
This column indicates the date and time the application was published and modified and who created it.
## **Application Usage Percentage**
The **Usage (Month)** column is the most important of them all. It shows the percentage of the allocated volume of events you’ve used so far and what’s left.
Consider upgrading your plan if your application usage percentage is high. If you are on the **Core plan**, upgrade to the [Growth Plan](https://my.foxmetrics.com/register?plan=solo) or [Speak to Us](https://www.foxmetrics.com/contact-us/) about a **Customized Enterprise account.**
## **Modified**
When was the application last modified? The column shows the date and time it was modified.
---
# 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://docs.foxmetrics.com/getting-started/setting-up-an-account/applications.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.