OppenMailer

HomePricingDocsPrivacy
Sign inCreate workspace
Browse documentation

Audiences

Import, inspect, and maintain lists in Lists.

Use this guide for audience creation, imports, preserved headers, resyncs, rollbacks, exports, and list-level review before sending.

Goal
Maintain clean recipient data with enough context for personalization and safe campaign targeting.
Best for
Operators preparing recipients, imports, segmentation, and personalization fields.
Outcome
Reliable lists with preserved source columns and fewer surprises at compose time.

Section 1

Create and name audiences

Audience names should reflect the real operational group they represent.

Surfaces

Lists

How to use it

  1. 01Create a new audience when the recipient group has its own sending purpose, cadence, or data source.
  2. 02Use names that will still make sense in Overview, Compose, and Campaigns later.
  3. 03Keep list intent obvious so operators do not accidentally send from the wrong audience.

Operator notes

  • Audience naming matters because the audience label appears across the workflow, especially when multiple sends are active.

Section 2

Import CSV, XLSX, or Google Sheets

Lists supports multiple source types, but every import should still be reviewed before launch.

Surfaces

Lists > Import

How to use it

  1. 01Upload CSV or XLSX when you need a fixed snapshot, or connect a public Google Sheet when you expect repeat resyncs.
  2. 02Review the imported headers and sample rows, especially when personalization depends on names, titles, or custom identifiers.
  3. 03If a source is sheet-backed, use resync when the source changes instead of creating duplicate audiences.

Operator notes

  • OppenMailer preserves imported headers so Compose and Templates can use the original column intent instead of flattening everything into a generic contact model.

Section 3

Inspect list detail and exported data

Use the list detail view to validate what the app actually imported.

Surfaces

Lists > Audience detail

How to use it

  1. 01Open the list detail page after import and scan the rows to confirm the columns and values are usable.
  2. 02Use export when you need to audit the current state or hand the processed list back to another team.
  3. 03Use rollback only when an import created bad records and you want to remove the effects of that specific import.

Operator notes

  • Rollback is meant to reverse a particular import’s impact, not as a substitute for routine list hygiene.

Section 4

Keep data clean for personalization

Better list hygiene reduces compose errors, ugly merge output, and failed follow-up logic.

Surfaces

Lists · Compose preview

How to use it

  1. 01Normalize email addresses and obvious duplicates before a major import whenever possible.
  2. 02Keep the columns you actually need for merge tags, sender variables, and ticket or receipt fields.
  3. 03Run a quick compose preview against the audience before launch so you catch broken names or missing values early.

Operator notes

  • If the imported sheet is the source of truth, resync from that sheet rather than hand-editing around it elsewhere.