Skip to main content
A contact is a person in your project: their address plus whatever you know about them. A segment is a group of contacts, and it’s what you pick as the audience when you send.

​
Importing contacts

The importer takes a CSV or Excel file and lets you map your columns to contact fields. That step matters more than it looks.
Map the name column. If you import bare addresses, {{first_name}} comes out empty in every email you send: the greeting reads “Hi ,”. It doesn’t fail and it doesn’t warn — it just sends. See Editor variables.
The importer deduplicates by address, so you can upload a list that overlaps with what you already have without creating duplicates. Imported contacts can go straight into a segment. For a handful of contacts you don’t need a file: create them by hand, or paste the list to the copilot and ask it to build the segment.

​
Segments

There are two kinds, and the difference is who decides membership. A static segment is a list: you build it once and it stays put. A dynamic segment is a question: every time it’s evaluated, it answers with whoever matches today. Dynamic rules are built on signals RQE already has: campaign engagement (opened, clicked, didn’t open), passage through an automation, custom events from your system, and Shopify data when your store is connected.
When in doubt, go dynamic. A static segment ages quietly: people get added, nobody removes them, and one day a send goes to an audience that no longer fits.

​
Suppressions

A suppressed contact receives no email, even when they sit inside a segment. It protects your sending reputation; it isn’t a punishment for the contact. The first three are automatic. Continuing to send to addresses that bounce or that flagged you as spam is the fastest route to the spam folder, so suppression works in your favor: see Deliverability. Suppressed contacts stay in your list, visible, with their reason attached. Someone who unsubscribed can only come back by resubscribing themselves.