Get started

Quickstart

Create a project, connect sending, and reach a reviewed first send.

This page gets a new project to a reviewed first send in about 20 minutes. Contacts sync immediately. Audiences, journeys, campaigns, and email drafts never go live until you say so. Customer mail leaves through your ESP, never Audryo’s servers.

What you will have at the end

A verified sending domain, at least a handful of contacts, one audience, and either a campaign you can send or a Journey you can dry-run. Sending to real customers still waits on consent and a green Review checklist.

The path

  1. Create a project (Foundation reads your site).
  2. Connect Resend or Mailgun and verify DNS.
  3. Sync or import contacts; record consent for marketing.
  4. Build an audience and preview it.
  5. Draft an email, send a test, confirm it.
  6. Send a campaign or activate a Journey after dry run.

Step by step

1. Create a project

Signup (or New project) asks for your website. That seeds Foundation: product facts and a brand kit. Confirm the facts that are true; reject invented pricing or legal claims.

Workspace → project tenancy: records never leak across projects. A workspace can hold several products.

2. Connect your email provider

Settings → Email delivery. Resend is recommended; Mailgun works. You need a domain you control — use a subdomain such as mail.yourcompany.com. Follow Connect your ESP through DNS and the provider webhook (bounces/complaints).

Until status is Verified, Journeys and campaigns refuse to activate.

3. Get people in

Data: CSV import, sample dataset, or continuous API ingest. Use stable externalIds.

Marketing mail also needs an explicit consent grant. Being a user of your product is not consent.

4. Build an audience

Audiences → New. Rules on fields, events, or tags. Preview before save. See Audiences.

5. Write the email

Emails or from a Journey/campaign. Same editor. Save draft, send test, Confirm. Confirm every language you enabled.

6. Campaign or Journey

Types of emails: one-shot vs sequence vs transactional API. Campaigns have no holdout; Journeys can, and Insights will measure lift against the goal event.

7. Optional: an agent

Settings → Agent access — scoped key. Agents propose; they do not silently send. Agent quickstart.

The one rule

Nothing customer-facing goes live on its own. Ingest is live data. Activation, campaign send, and transactional send are explicit, audited, fail-closed actions.