Getting started
The few steps between a new workspace and your first campaign.
Zeebra keeps your contacts and sends your email campaigns from your own domain, through Amazon SES. Everything lives in a workspace: its contacts, lists, segments, templates, campaigns, sending domains and members. Use one workspace per product or team, and switch between them from the menu at the top left.
1. Fill in your details
Open Settings → Workspace and add:
- Postal address. Anti-spam laws require it in every marketing email, so campaigns can't be sent without it. It goes in the footer for you.
- Company name, brand colour and logo. Used in the email footer and the pages people see when they unsubscribe.
- Timezone and default country. A new workspace starts in your browser's time zone and, when we can tell, your country. The time zone is used for schedules, reports and summary emails; the default country reads phone numbers typed without a
+. With no default country, every phone number needs its country code (like+44 20 7946 0958).
2. Add your sending domain
Open Settings → Email sending, add a domain such as news.yourcompany.com, and add the DNS records it shows. See Sending domain and DNS.
3. Bring in your contacts
Import a CSV from your old email tool, add people by hand, or collect signups with a signup form. Each contact is one of two kinds:
- Opted in: they agreed to get your emails. Only they get campaigns.
- Prospect: you have their address but not their agreement. They never get campaigns.
See Importing contacts.
4. Organise them
- Tags label contacts (VIP, speaker, 2026 attendee).
- Lists are fixed groups you add people to.
- Segments are rules ("opted in, tagged VIP, opened in the last 90 days") worked out each time you use them.
5. Write and send
Write a template or a campaign in the visual editor, in Markdown or in HTML, then review it, send yourself a test, and send it. See Campaigns and sending rules.
Working with code or AI agents
Everything above can also be done through the REST API or by an AI agent over MCP. See API and MCP.