Subscriber lifecycle emails

Subscriber lifecycle emails send after a reader subscribes or unsubscribes. Ask your agent to list them, create a new one, or change an existing one.

Each email has a trigger, delay, subject, body, and enabled state. Current triggers are:

• New subscriber sends when a reader subscribes.
• New subscriber follow-up sends after a reader subscribes and is useful with a delay.
• Subscriber unsubscribed sends after a reader unsubscribes.

Membership, paid-subscriber, and collectible triggers are retired and can't be used for new emails.

Create and review an email

Tell your agent the trigger, delay, subject, and body you want. New emails are always created disabled, so you can review the complete result before it can send.

Your agent can also show delivery totals that are available for each email: queued, in progress, sent, failed, and canceled. Opens and clicks appear for lifecycle emails sent after Paragraph began attributing engagement to each email. Older delivery records stay marked as unavailable instead of showing incomplete totals.

Update the default welcome email

Ask your agent to show the default welcome email before changing it. The agent identifies it by its email ID and default status, then shows the current and proposed subject or body for confirmation.

After you confirm, the agent changes only the subject and body fields you supplied. It returns the complete before and after definitions so you can inspect the saved result. Paragraph saves the prior definition with a rollback reference in the same atomic operation. The welcome email's system name, trigger, and delay don't change through this action.

Use the separate enable, disable, and test actions to change whether the welcome email sends or to send one copy to your signed-in email address.

Enable, disable, or delete

Your agent asks for confirmation before it enables, disables, or deletes an email, and before it changes an email that's already enabled.

Disabling first saves the email as disabled. New events can't schedule it, and delivery workers recheck that state before sending. Paragraph then deletes every queued Cloud Task and marks every queued or in-progress delivery canceled. If Cloud Task cancellation fails, the email remains disabled and your agent reports that cancellation must be retried.

Deleting uses the same order: disable, cancel pending deliveries, then delete the email. If cancellation fails, the disabled email remains available so deletion can be retried without losing its content. Default emails can't be deleted.

Send a test

Ask your agent to send a test, then confirm the signed-in account email it names. A test sends exactly one copy to that address. It doesn't schedule or fan out to subscribers, and it can test a disabled email.