# Sites

A Site is where all your data lives in Bento. Each Site is a distinct workspace with its own subscribers, campaigns, automations, and settings. 

## What is a Site?

A Site represents a single project, brand, or application within your Team. When you send events to Bento, import subscribers, or create emails, that data belongs to a specific Site.

Each Site has its own:

- **People**: Your subscribers and contacts
- **Events**: Tracked behaviors and actions
- **Tags and Fields**: Organization and custom data
- **Emails**: Broadcasts, sequences, and transactional messages
- **Flows**: Automations and workflows
- **Forms**: Signup forms and data collection
- **Settings**: DNS configuration, authors, and preferences

## Why Multiple Sites?

Having separate Sites lets you keep data isolated between different projects. Common reasons to use multiple Sites:

**Multiple brands or products**
If you run different businesses or products, each can have its own Site with separate subscriber lists and campaigns.

**Production and testing**
Many teams create a production Site for live campaigns and a separate testing Site for development and QA. This keeps test data from polluting your real subscriber list.

**Client work**
Agencies often create separate Sites for each client to keep data completely separate.


> Many users have two sites: one for production and one for testing. This is a common and recommended pattern.


## Site Isolation

Data in one Site is completely separate from other Sites. Subscribers in Site A don't exist in Site B. Emails sent in one Site don't affect another.

This isolation means:

- API calls target a specific Site
- Events are tracked per Site
- Segments and tags are Site-specific
- Billing is calculated across all Sites in your Team

## Switching Between Sites

If you have multiple Sites, you can switch between them from the Bento dashboard. Each Site has its own unique identifier used for API calls and integrations.

## Site Settings

Each Site has its own configuration:

- **DNS and sending domains**: Set up email authentication per Site
- **Authors**: Configure who emails appear to come from
- **Integrations**: Connect platforms like Shopify or Stripe per Site
- **API keys**: Your Site's unique identifiers for API access

## How Sites Connect to Other Concepts

Sites are the container for everything else:

- **Teams** contain Sites
- **People** belong to a Site
- **Events**, **Tags**, **Fields** are all Site-specific
- **Emails**, **Flows**, **Forms** are created within a Site

When working with the API or integrations, you're always working within the context of a specific Site.