Email marketing automation: campaign beta review

This page covers the one-to-many marketing job: decide who should receive a campaign, review the content and inspect what happened. Repli Email is not open for public campaign sending.

Repli Email is an admin-only private beta. Creating an account or upgrading a plan does not unlock email sending. No public email allowance, price or launch date is offered here.

Define the campaign audience before the message

The inspected workspace includes email contacts, audiences, saved templates and campaign recipient records. A selected audience is the starting set, not proof that every address is eligible. Permission and workspace suppression need to be checked before sending.

Describe why the group should receive this particular message. An imported email address, an order or an Instagram conversation is not automatically newsletter consent. Keep permission records available and exclude contacts who unsubscribed or should not receive promotions.

A scheduled campaign is not a lifecycle sequence

A campaign targets a selected group with one reviewed message. A per-contact sequence starts from an entry event and advances through delays and conditions. Use the drip guide for the second task rather than describing every scheduled broadcast as an automated customer journey.

Saved templates reduce repeated editing, but personalization still depends on the supplied fields. Preview missing names and links as well as complete records. No open-based targeting, automatic revenue attribution or duplicate-free delivery guarantee is made by this review.

Read the result at the right level

Enrollment, queued, sent and delivered describe different stages. The inspected provider-event path records supported delivery, bounce and complaint events and can suppress addresses on qualifying failures. Not every connected mailbox supplies equivalent campaign reporting.

Do not describe delivery events as opens, clicks or purchases. Current provider setup and live campaign delivery remain unverified. Sender/domain checks and capacity controls in code are safeguards to inspect, not public email allowances or proof of operational readiness.

Illustrative planning example

Purpose

A newsletter for readers who requested updates about a specific subject.

Review

Check the selected audience, permission, suppressed addresses and the final template.

Reporting

Separate queued and sent counts from confirmed delivery; do not report them as sales.

Review checklist

Confirm beta access

No public signup or upgrade enables this email workspace.

Review audience and content

Check eligible contacts, sender, supplied fields and actual campaign configuration.

Establish operation

Verify a received email and supported reporting through an authorized test before broader use.

Frequently asked questions

Is campaign sending included in a Repli plan?

Repli Email is an admin-only private beta. Creating an account or upgrading a plan does not unlock email sending. No public email allowance, price or launch date is offered here.

Does Repli guarantee an email sends only once?

No universal delivery guarantee is made. Event deduplication and recipient records do not by themselves prove exactly-once delivery across every provider failure.

Are delivery counts the same as opens?

No. Delivery, open activity, clicks and purchases are different signals; only report the events actually recorded by the configured path.

Related guides

Email automation: Repli private beta

How to evaluate email automation software

Drip email campaign software: plan the sequence

Re-engagement email automation: define inactivity first

Sending guidance

AWS email sending best practices