Skip to main content

Start Here

This is the product documentation for Mailtarget. It covers Email Marketing, API, SMTP relay, deliverability operations, Mailtarget CDP, reporting, and integration paths.

The fastest way through these docs is to pick the Mailtarget surface you are using first.

1. What is Mailtarget​

Mailtarget is enterprise email infrastructure. You send transactional and marketing email through an HTTP API or an SMTP relay, manage sending domains and authentication, monitor deliverability, and reach contacts via Mailtarget CDP when you need behavioral targeting.

Read What is Mailtarget for the full picture, including who runs the platform and what compliance posture it ships with.

2. Which surface are you using​

Pick the surface that matches the job.

  • Email Marketing is for campaign creation, targeting, scheduling, sending, and reporting.
  • The API path gives you JSON requests, server-side templates, substitution data, attachments, metadata for tracking, and a single response object with a transmissionId you can reconcile against webhooks.
  • The SMTP path drops a relay in front of your existing mail stack with one host, one port, and one credential.
  • Mailtarget CDP is for contacts, fields, segments, audiences, journeys, and targeted sends.

Read Email Marketing, API vs SMTP, or Mailtarget CDP before you decide where to start.

3. First Email​

Pick the quickstart that matches your decision above.

  • API Quickstart sends the first transactional email with cURL and language examples.
  • SMTP Quickstart configures the relay and sends one test message.

Both quickstarts assume you already have an API key. If you do not, create one inside the Mailtarget dashboard with the permission scope that matches your path (Send via API or Send via SMTP).

Where to go next​

After your first send works, the order most teams follow is:

  1. Authentication for API keys, allowlisting, and rotation.
  2. Sending Domains for SPF, DKIM, DMARC, and tracking domain setup.
  3. Errors and Rate Limits before you write retry logic.
  4. Webhooks when you need delivery, open, click, or bounce events.
  5. The Transmission API reference once you start tuning the request body.

If you operate Mailtarget at production scale, the Operations section covers deliverability monitoring, webhook reliability, and domain verification troubleshooting.