> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/email/brevo/data-overview.md).

# Data Overview

Brevo exposes a broad range of data across contact management, CRM, and campaign channels. Below is a breakdown of what's available through each entity.

## Entity summary

| Entity                     | What it contains                                                      |
| -------------------------- | --------------------------------------------------------------------- |
| Contacts                   | Email, subscription status, creation date, custom attributes          |
| Contacts attributes        | Field names, types, and categories for contact properties             |
| Contacts folders           | Folder IDs and names                                                  |
| Contacts folders lists     | Lists nested inside folders                                           |
| Contacts lists             | List names, IDs, subscriber counts                                    |
| Contacts lists contacts    | Contacts mapped to a specific list                                    |
| Contacts segments          | Segment rules, names, and IDs                                         |
| Senders                    | Sender name, email, and verification status                           |
| Companies                  | Company name, domain, linked contacts                                 |
| Companies attributes       | Custom field definitions for companies                                |
| CRM pipeline stages        | Stage name, order, and pipeline ID                                    |
| CRM pipeline details all   | Full pipeline metadata                                                |
| CRM attributes deals       | Custom deal field definitions                                         |
| CRM deals                  | Deal name, value, stage, owner, dates                                 |
| CRM task types             | Task category labels                                                  |
| CRM tasks                  | Task title, due date, status, linked contact or deal                  |
| CRM notes                  | Note content, creation date, linked record                            |
| Domains                    | Domain name, verification and authentication status                   |
| Webhooks                   | URL, event triggers, creation date                                    |
| Accounts                   | Plan type, credits, account email                                     |
| Organization invited users | Invitee email, role, and invitation status                            |
| Email campaigns            | Campaign name, status, send date, open rate, click rate, unsubscribes |
| SMS campaigns              | Campaign name, status, send date, delivered, unsubscribes             |

#### Email campaign metrics

| Metric        | Description                                      |
| ------------- | ------------------------------------------------ |
| Unique opens  | Number of unique recipients who opened the email |
| Total opens   | Total open events including repeat opens         |
| Clicks        | Total clicks on links in the email               |
| Unique clicks | Number of unique clickers                        |
| Unsubscribes  | Recipients who unsubscribed after this campaign  |
| Bounces       | Hard and soft bounces                            |
| Spam reports  | Recipients who marked as spam                    |
| Delivered     | Emails successfully delivered                    |
| Sent          | Total emails sent                                |

#### Email campaign dimensions

| Dimension           | Description                        |
| ------------------- | ---------------------------------- |
| Campaign ID         | Unique identifier for the campaign |
| Campaign name       | Name as set in Brevo               |
| Subject line        | Email subject                      |
| Status              | Draft, queued, sent, or archived   |
| Send date           | Scheduled or actual send timestamp |
| Sender name / email | The sender identity used           |

#### SMS campaign metrics

| Metric       | Description                     |
| ------------ | ------------------------------- |
| Delivered    | Messages successfully delivered |
| Sent         | Total messages sent             |
| Unsubscribes | Recipients who opted out        |

#### Contact dimensions

| Dimension              | Description                                  |
| ---------------------- | -------------------------------------------- |
| Email                  | Contact email address                        |
| SMS                    | Contact phone number (if captured)           |
| First name / Last name | Name fields                                  |
| Created at             | Date contact was added                       |
| Modified at            | Date contact was last updated                |
| Email blacklisted      | Whether the contact is globally unsubscribed |
| SMS blacklisted        | Whether the contact has opted out of SMS     |
| Custom attributes      | Any fields you've defined in Brevo           |

#### CRM deal dimensions

| Dimension       | Description                       |
| --------------- | --------------------------------- |
| Deal name       | Name of the deal                  |
| Amount          | Deal value                        |
| Stage           | Current pipeline stage            |
| Owner           | Assigned user                     |
| Close date      | Expected or actual close date     |
| Linked contacts | Contacts associated with the deal |

## Common metric combinations

* **Email campaigns + Contacts lists** — Join on list ID to see which audience segments are driving the best open rates
* **CRM deals + CRM tasks** — Combine to get a full activity picture per deal, including pending follow-ups
* **Contacts + Email campaigns** — Use Append to merge contact attributes with campaign engagement for segmentation analysis
* **Email campaigns + SMS campaigns** — Append both entities to compare cross-channel performance in one report

## Use cases by role

{% tabs %}
{% tab title="Marketers" %}

* Pull email and SMS campaign stats into Google Sheets or Looker Studio to build a unified campaign performance dashboard
* Export contacts and segments to analyze audience growth over time
* Send campaign data to ChatGPT or Claude to generate performance summaries or subject line recommendations
* Use Append transformation to combine email and SMS campaign results in one table
  {% endtab %}

{% tab title="CRM & Sales teams" %}

* Export CRM deals and pipeline stages into a spreadsheet to track deal velocity and stage distribution
* Join CRM tasks with deals to see activity levels per opportunity
* Pull CRM notes into a data warehouse for historical activity logging
* Use Aggregate transformation to summarize deal values by owner or pipeline stage
  {% endtab %}

{% tab title="Operations" %}

* Monitor organization invited users to audit team access
* Export webhooks and domains for infrastructure documentation
* Pull account data to track plan usage and credit consumption
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* Brevo uses API key authentication — there is no OAuth flow. Keep your API key secure and rotate it if shared accidentally.
* Contact custom attributes are defined per account — export **Contacts attributes** alongside **Contacts** to understand what each field means.
* The **Contacts lists contacts** entity requires selecting a specific list — add multiple sources in one data flow to pull contacts from several lists at once.
* Campaign statistics in Brevo are updated in near real-time after a send, but some metrics like unsubscribes may have a short delay.
* SMS campaigns have fewer available metrics than email campaigns by design.


---

# 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.coupler.io/sources/category/email/brevo/data-overview.md?ask=<question>&goal=<endgoal>
```

`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.
