> 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/bigmailer.md).

# BigMailer

Connect BigMailer to Coupler.io to pull campaign performance, contacts, lists, and suppression data into sheets or dashboards.

BigMailer is an email marketing platform built for agencies and businesses managing multiple brands. It lets you run bulk campaigns, transactional emails, and list management all from one place. Connecting BigMailer to Coupler.io lets you pull your email data into spreadsheets, dashboards, or AI tools for deeper analysis.

## Why connect BigMailer to Coupler.io?

* **Centralize your email data** — combine campaign performance, contact lists, and suppression data in one destination
* **Report across brands** — use the Append transformation to stack data from multiple brands into a single table
* **Feed AI tools** — send your campaign and contact data directly to ChatGPT, Claude, Gemini, or other AI destinations for analysis and recommendations
* **Automate reporting** — schedule automatic refreshes so your dashboards always reflect the latest data

## Prerequisites

* A BigMailer account with at least one brand set up
* An API key from your BigMailer account settings
* A destination ready — Google Sheets, Excel, BigQuery, Looker Studio, or an AI tool like ChatGPT or Claude

## Quick start

{% hint style="success" %}
If you manage multiple brands in BigMailer, start with the **Bulk campaigns** entity to get a high-level view of campaign performance, then add **Contacts** or **Lists** as additional sources in the same data flow.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Log in to Coupler.io, go to the Data flows section, and click **Add data flow**. Search for BigMailer and select it as your source.
{% endstep %}

{% step %}
**Enter your BigMailer API key.** In BigMailer, go to **Account Settings → API Keys** and generate or copy your existing API key. Paste it into the API key field in Coupler.io.
{% endstep %}

{% step %}
**Select an entity.** Choose which type of data you want to import — for example, Bulk campaigns, Contacts, or Lists. See the table below for all available entities.
{% endstep %}

{% step %}
**Choose a destination.** Select where you want your data to go — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT, Claude, Gemini, Perplexity, Cursor, or OpenClaw.
{% endstep %}

{% step %}
**Run your data flow.** Click **Run** to execute a manual run. Once it completes successfully, your BigMailer data will appear in your chosen destination.
{% endstep %}
{% endstepper %}

## Available entities

| Entity                  | What it contains                                                    |
| ----------------------- | ------------------------------------------------------------------- |
| Brands                  | Top-level brand accounts within your BigMailer workspace            |
| Contacts                | Individual subscribers with email, profile fields, and custom data  |
| Lists                   | Mailing lists and their metadata                                    |
| Fields                  | Custom contact fields used for segmentation and personalization     |
| Message types           | Definitions for transactional vs. marketing email types             |
| Segments                | Filtered contact groups based on criteria like activity or location |
| Bulk campaigns          | Mass marketing emails sent to lists or segments                     |
| Transactional campaigns | Automated one-to-one emails triggered by user actions               |
| Suppression lists       | Opt-outs and bounced addresses excluded from future sends           |
| Users                   | Team members with access to your BigMailer account                  |

## BigMailer data overview

BigMailer exposes ten entities through Coupler.io, covering everything from your brand structure and contact database to campaign performance and suppression management. Here's a breakdown of what each entity contains and how you can use the data.

## Entities summary

| Entity                  | Best used for                                                           |
| ----------------------- | ----------------------------------------------------------------------- |
| Brands                  | Understanding your account structure and brand-level organization       |
| Contacts                | Analyzing your subscriber base, segmentation, and custom attributes     |
| Lists                   | Auditing list sizes, growth, and organization                           |
| Fields                  | Mapping your contact data model and available personalization variables |
| Message types           | Distinguishing transactional from marketing sends in reporting          |
| Segments                | Reviewing dynamic audience definitions and segment criteria             |
| Bulk campaigns          | Tracking mass email campaign metadata and send history                  |
| Transactional campaigns | Monitoring trigger-based email setups and automation activity           |
| Suppression lists       | Managing deliverability by auditing opt-outs and bounces                |
| Users                   | Reviewing team access and account user management                       |

## Contacts

#### Contact fields

| Field         | Description                                         |
| ------------- | --------------------------------------------------- |
| Email         | The subscriber's email address                      |
| First name    | Contact's first name                                |
| Last name     | Contact's last name                                 |
| Status        | Subscription status (active, unsubscribed, etc.)    |
| Created at    | Date the contact was added                          |
| Updated at    | Date the contact record was last modified           |
| Custom fields | Any additional fields defined in your Fields entity |

## Lists

#### List fields

| Field         | Description                    |
| ------------- | ------------------------------ |
| List ID       | Unique identifier for the list |
| Name          | List name                      |
| Contact count | Number of contacts in the list |
| Created at    | Date the list was created      |
| Brand ID      | The brand this list belongs to |

## Bulk campaigns

#### Campaign fields

| Field        | Description                           |
| ------------ | ------------------------------------- |
| Campaign ID  | Unique identifier                     |
| Name         | Campaign name                         |
| Subject      | Email subject line                    |
| Status       | Draft, scheduled, sent, etc.          |
| Send date    | When the campaign was or will be sent |
| List/segment | The audience targeted                 |
| Brand ID     | The brand the campaign belongs to     |

## Transactional campaigns

#### Transactional campaign fields

| Field        | Description                                    |
| ------------ | ---------------------------------------------- |
| Campaign ID  | Unique identifier                              |
| Name         | Campaign name                                  |
| Message type | The message type associated with this campaign |
| Status       | Active or inactive                             |
| Brand ID     | The brand this campaign belongs to             |

## Suppression lists

#### Suppression fields

| Field      | Description                                             |
| ---------- | ------------------------------------------------------- |
| Email      | The suppressed email address                            |
| Reason     | Reason for suppression (bounce, unsubscribe, complaint) |
| Created at | Date the address was added to the suppression list      |
| Brand ID   | The brand this suppression applies to                   |

## Common data combinations

* **Contacts + Lists** — Join these two entities to see which lists each contact belongs to and analyze list composition
* **Bulk campaigns + Brands** — Join to enrich campaign data with brand-level context for cross-brand reporting
* **Contacts + Suppression lists** — Compare to identify overlap and keep your active contact counts accurate
* **Bulk campaigns + Transactional campaigns** — Append both into a single table for a unified send history view

## Use cases by role

{% tabs %}
{% tab title="Email marketers" %}

* Pull **Bulk campaigns** into Google Sheets or Looker Studio to track send history and campaign metadata across brands
* Use **Segments** data to audit your audience definitions and ensure targeting criteria are up to date
* Send **Contacts** data to ChatGPT or Claude to identify patterns in subscriber attributes and suggest segmentation strategies
  {% endtab %}

{% tab title="Agency managers" %}

* Use the **Brands** entity to get a structured overview of all client accounts in one place
* Append **Bulk campaigns** data from multiple brands into a single table to build consolidated client reports
* Join **Users** with **Brands** to audit which team members have access to which client accounts
  {% endtab %}

{% tab title="Deliverability & ops" %}

* Monitor **Suppression lists** regularly to track opt-out and bounce rates across brands
* Use **Contacts** with status filters to identify inactive subscribers and maintain list hygiene
* Pull **Fields** data to document your contact data model and ensure custom attributes are being populated correctly
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* BigMailer organizes everything under **Brands** — most other entities include a Brand ID field you can use to filter or join data
* **Custom fields** defined in the Fields entity appear as columns in the Contacts entity, so expanding your field set will add columns to contact exports
* Suppression lists are brand-specific in BigMailer — make sure you're pulling the right brand's suppression data when auditing deliverability
* Transactional campaigns are tied to **Message types** — pull both entities if you need to understand the full context of your automated sends

## BigMailer common issues

### Connection issues

<details>

<summary>My API key is not accepted</summary>

Double-check that you copied the full API key from BigMailer without any extra spaces. API keys are found under **Account Settings → API Keys** in BigMailer. If the key still doesn't work, try regenerating it in BigMailer and entering the new one in Coupler.io.

</details>

<details>

<summary>The data flow fails immediately after setup</summary>

Make sure your API key has the correct permissions in BigMailer. Some keys may be scoped to read-only or restricted to specific brands. Check your key's permission settings in BigMailer and ensure it has access to the entity you're trying to pull.

</details>

### Missing data

<details>

<summary>Contacts from a specific brand are not showing up</summary>

BigMailer scopes data by brand. If you're pulling the Contacts entity and only see data from one brand, you may need to create a separate source for each brand in your data flow and use the Append transformation to combine them.

</details>

<details>

<summary>Custom fields are missing from my Contacts export</summary>

Custom fields only appear in the Contacts entity if they've been populated for at least some contacts. Check the Fields entity first to confirm the fields exist, then verify that your contacts actually have values in those fields.

</details>

<details>

<summary>Suppression list appears empty</summary>

Suppression lists in BigMailer are brand-specific. If the list appears empty, confirm you're connected to the correct brand and that suppressions have been recorded for that brand. A brand with no bounces or opt-outs will have an empty suppression list.

</details>

### Permission errors

<details>

<summary>I get a 403 Forbidden error when running the data flow</summary>

This usually means your API key doesn't have permission to access the requested entity. Log in to BigMailer, go to **Account Settings → API Keys**, and verify the key's access scope. If you're an agency user, check whether your role has access to the brand you're querying.

</details>

### Data discrepancies

<details>

<summary>Contact counts in Coupler.io don't match BigMailer's dashboard</summary>

BigMailer may show slightly different counts if the dashboard includes pending or unconfirmed contacts that the API excludes. Check the **Status** field in your Contacts export to see if unconfirmed or suppressed contacts are being filtered out at the API level.

</details>

<details>

<summary>Campaign data looks incomplete compared to what I see in BigMailer</summary>

Draft campaigns may not be returned by the API depending on their status. Filter your Bulk campaigns data by the **Status** field and check whether drafts are expected to appear in your output.

</details>

### Rate limits

<details>

<summary>The data flow times out or returns partial data on large exports</summary>

BigMailer's API has rate limits that can affect large contact or campaign exports. If you're hitting limits, try splitting your data flow into separate sources per brand rather than pulling all data at once. You can then use the Append transformation to recombine them in your destination.

</details>

## BigMailer FAQ

<details>

<summary>Where do I find my BigMailer API key?</summary>

Log in to BigMailer and go to **Account Settings → API Keys**. You can generate a new key or copy an existing one from there. Paste the key into the API key field when setting up your BigMailer source in Coupler.io.

</details>

<details>

<summary>Can I pull data from multiple brands in one data flow?</summary>

Yes. Add a separate source for each brand within the same data flow, then use the **Append** transformation to combine the results into a single table. Each source will return data scoped to its brand, and the Brand ID field helps you distinguish them after merging.

</details>

<details>

<summary>Can I combine bulk campaigns and transactional campaigns in one report?</summary>

Yes. Add both as separate sources in your data flow and use the **Append** transformation to stack them. Make sure both entities share the same column structure in your destination, or use the Aggregate transformation to normalize fields before combining.

</details>

<details>

<summary>Why are my custom contact fields not showing up?</summary>

Custom fields only appear as columns in the Contacts export if they exist in your BigMailer account and have been assigned values. Pull the **Fields** entity first to confirm your custom fields are defined, then check whether your contacts have data in those fields.

</details>

<details>

<summary>Can I send BigMailer data to an AI tool like ChatGPT or Claude?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can send entities like Bulk campaigns, Contacts, or Segments directly to these tools for analysis — for example, asking an AI to review your audience segmentation or campaign naming patterns.

</details>

<details>

<summary>Does Coupler.io pull historical campaign data or only the current state?</summary>

Coupler.io returns the data available through the BigMailer API at the time of the run. For campaigns, this includes all campaigns regardless of their send date. For contacts and suppression lists, it reflects the current state of your account. Re-running the data flow captures any changes since the last run.

</details>

<details>

<summary>How do I monitor deliverability health using BigMailer data in Coupler.io?</summary>

Pull the **Suppression lists** entity to track opt-outs and bounces over time, and combine it with the **Contacts** entity to calculate the ratio of suppressed to active addresses. You can load this into Google Sheets or Looker Studio for a deliverability dashboard, or send it to an AI tool for a quick health summary.

</details>

<details>

<summary>Can I use BigMailer data alongside data from other sources in Coupler.io?</summary>

Yes. Coupler.io data flows support multiple sources, so you can combine BigMailer data with other platforms — for example, joining your BigMailer Contacts with CRM data from another source using the **Join** transformation to enrich your subscriber records.

</details>

{% hint style="info" %}
For a full breakdown of available fields per entity, see the [Data Overview](#bigmailer-data-overview) article. For help with connection errors or missing data, check [Common Issues](#bigmailer-common-issues).
{% endhint %}


---

# 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://docs.coupler.io/sources/category/email/bigmailer.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.
