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
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
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
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
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
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
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
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
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
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
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
Last updated
Was this helpful?
