Help & docs

Add a sending server under Sending, publish the DKIM and SPF records shown for your domain, and wait for verification to pass. Until a domain verifies, campaigns using it cannot be sent — that is deliberate, because sending from an unauthenticated domain is the fastest way into a spam folder.

Import a CSV under Lists, mapping each column to a field. Addresses that are malformed, duplicated, or already unsubscribed are reported rather than silently dropped, so you can see exactly what happened to every row.

Sending credits are consumed one per recipient and reset at the start of each billing cycle. A campaign is checked against your remaining credits before it starts, so a send never stops halfway through for lack of credit.

Warm up gradually with a warmup schedule, authenticate every sending domain with DKIM and SPF, use a tracking domain on your own domain, and keep your list clean by letting the bounce and feedback handlers do their job. The deliverability page in the app shows which of these are still outstanding.

Yes. Every list, campaign and subscriber is available through the REST API, and webhooks push subscription, delivery, open, click, bounce and complaint events to your own endpoint as they happen.

From Account, at any time, with no retention period and no exit interview. You get your subscribers, their custom fields and their subscription status as CSV.