Concepts
Use this section when you want to understand how PING8 thinks about email operations before you configure a screen.
PING8 combines product email, marketing email, contacts, domains, mailboxes, and sending infrastructure in one control plane. The concepts below explain how those pieces fit together.
Core model
| Concept | What it means in PING8 |
|---|---|
| Workspace / tenant | An isolated operating space for one brand, team, or customer. |
| Domain | A sending identity such as yourdomain.com, with DNS authentication records. |
| Sender | A From address on a verified domain, such as hello@yourdomain.com. |
| Contact group | A list of subscribers that can receive campaigns. |
| Tags | Internal labels used to target more specific segments inside a group. |
| Template | Reusable email content for campaigns or API sends. |
| Delivery engine | The path that injects and transports mail: Local Postfix, Tenant default, KumoMTA, or external SMTP. |
| Lifecycle event | A delivery state such as queued, delivered, deferred, bounced, opened, or clicked. |
How to use this section
- Read Sending Lifecycle before interpreting campaign progress.
- Read Delivery Engines before choosing Local Postfix, Tenant default, or KumoMTA.
- Read DNS and Authentication before adding production domains.
- Read Tracking and Suppression before sending marketing campaigns.
Operating principle
Always prove the identity chain before you send real volume:
- Verify domain DNS.
- Confirm the delivery engine is healthy.
- Send one test email to an owned recipient.
- Confirm lifecycle telemetry arrives in PING8.
- Start with a small audience before increasing volume.