> ## Documentation Index
> Fetch the complete documentation index at: https://docs.edgeimpulse.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Data campaigns
> Track dataset growth and model performance over time on shared dashboards, with scheduled email updates.
**Only available on the Enterprise plan**
This feature is only available on the Enterprise plan. Review our [plans and pricing](https://edgeimpulse.com/pricing) or sign up for our free [expert-led trial](https://edgeimpulse.com/expert-led-trial) today.
The "data campaigns" feature allows you to quickly track your experiments and your models' development progresses. It is an overview of your pipelines where you can easily extract useful information from your datasets and correlate those metrics with your model performances.
It has been primarily designed to follow clinical research data processes. In August 2023, we released this feature for every enterprise user as we see value in being able to track metrics between your datasets and your projects.
## How data campaigns work
A dataset or project page shows the current state. A campaign samples that state repeatedly and plots it over time, so you can see data arriving, checklists passing, and accuracy changing.
Campaigns are grouped into dashboards:
| Object | What it is |
| - | - |
| **Dashboard** | A container for campaigns, and the thing people subscribe to. It holds the email recipients, how often they are emailed, and how many days of history the graphs show. |
| **Campaign** | One tracked effort inside a dashboard. It references the organization datasets and projects it tracks, optionally the pipelines that feed it, and the queries that define its metrics. |
Graphs are recalculated periodically, so they can lag behind the live data. Metrics come from counts over the selected datasets, model performance from the selected projects, and any queries you define. Each query is an SQL `WHERE` filter over dataset metadata.
A campaign also carries a description, coordinators, and links, so a collaborator can find the protocol document or repository without asking.
## Setting up your dashboard
To get started, navigate to the **Data campaigns** tab in your organization:
Click on **+ Create new dashboard**.
Give your dashboard a name, and select one or more collaborators to receive the daily updates by email. If you don't want to be spammed, you can select when you want to receive these updates, either *Always*, *On new data, changes or on error*, or *Never*. Finally, set the last number of days shown in the graphs:
The number of days only changes what the graphs show. It doesn't delete any data. Use a short range to see recent changes, or a long range to review the whole campaign.
You can create as many dashboards as needed, simply click on **+ Create a new dashboard** from the dropdown available under your current dashboard:
If you want to delete a dashboard, Click on **Actions...** -> **Delete dashboard**
## Setting up your campaign
Once your dashboard is created, you can add your custom campaigns. It's where you will specify which metrics are important to you and your use case. Click on **Actions...** -> **Add campaign**
Fill the form to create your campaign:
**Name**: Name of your data campaign.
**Description**: Description of your data campaign.
**Campaign coordinators**: Add the collaborators that are engaged with this campaign
**Datasets**: Select the datasets you want to visualize in your campaign. You can add several datasets.
**Projects**: Select the projects you want to visualize in your campaign.
You can add several projects.
**Pipelines**: Select the pipeline that is associated with your campaign.
*Note that this is for reference only, it is not displayed in your campaign*
**Links**: Select between the link type you need. Options are Github, Spreadsheet, Text Document, Code repository, List or Folder.
Add a name and the link. This place is useful for other collaborators to have all the needed information about your project, gathered in one place under your campaign.
**Addition queries to track**:
These queries are data filters that need to be written in the SQL WHERE format. See [Querying data](/knowledge/guides/reference-designs/health-reference-design/querying-clinical-data) for more information.
For example `metadata->`age >= 18\` will return the data samples from adult patients.
Each query plots how many data items match it over time. Write one query per group you want to follow, such as a single site, device revision, or age band, so you can see when one group stops growing.
You can then save your data campaign and it will be added to your dashboard:
This dashboard shows the metrics' progress from the [Health reference design data](/knowledge/guides/reference-designs/health-reference-design)
If you want to edit or delete your campaign, click on the "**⋮**" button on the right side of your campaign:
## Working with campaigns programmatically
Dashboards and campaigns can also be created and read through the API.
| Task | Endpoint |
| - | - |
| List the dashboards in an organization | [Get data campaign dashboards](/apis/studio/organizationdatacampaigns/get-data-campaign-dashboards) |
| List the campaigns on a dashboard | [Get data campaigns](/apis/studio/organizationdatacampaigns/get-data-campaigns) |
| Create a campaign, including its datasets, projects, queries, and links | [Add a data campaign](/apis/studio/organizationdatacampaigns/add-a-data-campaign) |
| Read a campaign together with its computed graphs | [Get data campaign](/apis/studio/organizationdatacampaigns/get-data-campaign) |
## Additional resources
* [Data pipelines](/studio/organizations/data-pipelines)
* [Organization data](/studio/organizations/data)
* [Health reference design](/knowledge/guides/reference-designs/health-reference-design)
* [Querying clinical data](/knowledge/guides/reference-designs/health-reference-design/querying-clinical-data)