Subscriber edit

The subscriber edit page is one contact's full profile — contact details, status, per-subscriber email statistics and history, the automation runs they went through, and the actions you can take on them, including exporting their data and starting an automation by hand.

Subscriber Overview

The subscriber edit page provides a comprehensive view of an individual subscriber's profile, including their contact information, email history, and the automations they have been through. Open it by clicking a subscriber's email address in the Subscribers table.

At the top you see the subscriber's name (or email address if there is no name), their email address and Subscriber since date, and an Actions menu. Above the details, a strip of numbers shows Emails received, Link clicks, Last opened, Last active (both read Never when nothing has been recorded yet) and the Engagement score with a progress bar.

Subscriber Status

The Email consent card beside the details shows the subscriber's current state as a badge, with a one-line explanation:

New
badge
Just added and waiting for Yaplet's background check before verification starts
Not confirmed
badge
The double opt-in email has been queued or sent, but the address hasn't been confirmed yet
Subscribed
badge
Subscriber is confirmed and can receive emails
Unsubscribed
badge
Subscriber has unsubscribed from your newsletters
Removed
badge
Subscriber has been taken off the list and is no longer emailed
Bounced
badge
Mail to this address came back as permanently undeliverable — set automatically by bounce handling
Spam complaint
badge
The subscriber marked one of your emails as spam — set automatically by complaint handling

Under the badge, the card has a button: Unsubscribe for a subscribed contact, or Mark as subscribed for one that is new, not confirmed or removed. For a contact who said no, a lock message takes its place (see below).

A "no" stays a "no". An Unsubscribed, Bounced or Spam complaint contact can't be switched back to subscribed or verified by anyone in your account — not on this page, not with the Verify subscribers bulk action, not by importing it again (from a file or through the API), and not by an AI. Deleting the contact and adding it again doesn't help either: Yaplet remembers which addresses in your account said no, so the re-added contact shows up with its old status, and you can see why it isn't emailed. Only the person can subscribe again — see Confirmation Emails.

The card is followed by an Activity timeline, newest first: Added to your list, Last email sent, Last opened an email, Last clicked a link and Last active, each with its date.

Email Statistics

View comprehensive email engagement metrics for this specific subscriber, under Email history ("Every email this subscriber was sent, with opens and clicks").

Send Statistics

Sent emails

Total number and percentage of emails successfully handed off for delivery to this subscriber

Queued/Paused emails

Emails waiting to be sent or temporarily paused

On hold

Emails held back for now, for example while a campaign is spread over several days. This card only appears when some emails are on hold

Failed emails

Emails that failed to deliver

Engagement Metrics

Opened

Emails the subscriber opened

Clicked

Emails where the subscriber clicked on links

Bounces

Emails that bounced due to delivery issues

Unsubscribed

Times the subscriber clicked unsubscribe

Complaints

Spam complaints reported by the subscriber

Email History Table

Below the statistics, you'll find a detailed table showing:

  • Subject: Email subject line (clickable to open the campaign or automation it came from)
  • Type: Whether it was sent by a Campaign or an Automation
  • From: Sender information
  • State: Current delivery status (Sent, Queued, Paused, Held, Failed or Sending)
  • Sent At: When the email was sent
  • Opened: When the subscriber opened it, with ×2, ×3 and so on when it was opened more than once
  • Clicks: How many links in it the subscriber clicked

Tabs above the table narrow it down to All emails, the ones the subscriber Opened, the ones they Clicked, or the ones they Didn't open.

Filter by email state, subject, or sender to find specific emails in the history.

Automation Run Statistics

Track how this subscriber has moved through your email automations, under Automations ("Automation runs this subscriber went through"). One run is one pass of one automation for this one contact.

Run Summary

Completed

Runs that finished successfully for this subscriber

In progress

Runs waiting to be processed, or currently in progress

Failed

Runs that hit an error for this subscriber

A run counts as completed once the person has gone through every step. The email from its last step can still be waiting in the send queue for a few minutes.

Automation History Table

The Automation runs table below the cards shows every automation this contact has gone through, newest first:

  • Automation: Name of the automation (clickable to open its report)
  • State: Current run status (Completed, In progress, Failed or Canceled)
  • Created at: When the run was created

Subscriber Management

Edit Subscriber Details

Update the subscriber's basic information in the Details section ("Who this subscriber is and which groups they are in"):

Required Fields:

  • Email: Subscriber's email address
  • Name: Subscriber's full name

Optional Fields:

  • Groups: Add or remove the subscriber from group memberships. Campaigns and automations sent to a group reach this person
  • Engagement score: A number from 0 to 32,767 that ranks how engaged the subscriber is. It updates automatically: a real open adds 10 points and a link click adds 50, while every email sent first takes 10% off, so the score fades when someone stops reading. Opens within a minute of sending are mail systems loading the images by themselves and don't count. Higher-scoring subscribers are sent first within each campaign. You can also set this value manually to override it; automatic updates continue afterward.

Below it, the Custom fields section holds the extra details you store about each subscriber: one input per custom field, with the field's merge tag on the right (the tag you type in an email to insert the value). Manage fields opens the Fields view. Until you have created a field, the section says "No custom fields yet."

Changes are saved when you click Save changes in the Details section. While you have unsaved edits it shows "Unsaved changes" with a Discard button beside it, and leaving the page asks you first.

Administrative Actions

Access additional management options through the Actions dropdown:

Trigger automation

Start one of your automations for this subscriber by hand

Export JSON

Download the subscriber's complete data as a JSON file for backup or external processing

Subscribe/Unsubscribe

Unsubscribe a Subscribed subscriber, or subscribe a New, Not confirmed or Removed one (it becomes Subscribed). Unsubscribing asks you to confirm and can't be undone from the dashboard

Delete

Permanently remove the subscriber (requires confirmation)

For an Unsubscribed, Bounced or Spam complaint contact, Subscribe is disabled and shows the hint "This contact unsubscribed, bounced or complained. Only the person can subscribe again, through the subscribe link in an earlier email." You get the same message as an error when you subscribe a Removed contact whose address unsubscribed, bounced or complained before.

Triggering an Automation

Trigger automation opens a dialog that starts an automation for this one subscriber immediately, without waiting for its own trigger to fire.

Choosing the Automation

The Automation picker lists every automation in your account that is currently active. Pick one and click Start. Yaplet then:

  1. Creates a run of that automation for this subscriber
  2. Works through its nodes in order
  3. Sends emails or performs actions as configured

A toast reading "Automation started" confirms it. You can follow the run in the Automation run statistics above.

API Variables

If the automation you picked uses the API trigger, the dialog also asks for the values its emails and webhooks expect:

An API-triggered automation can contain variables (like {{ key }}) in its email content blocks and webhook body fields. Because you are starting it by hand rather than through an API call, you have to supply those values yourself.

Adding Variables:

  1. Click "Add Field" to add key-value pairs
  2. Enter the variable name (without {{ }}) in the Key field
  3. Enter the replacement value in the Value field
  4. Add as many variables as needed
Missing variable values may cause the automation to behave unexpectedly or fail.

Privacy and Compliance

All subscriber data is handled in compliance with privacy regulations. Email statistics and automation runs are tracked for legitimate business purposes including deliverability monitoring and automation effectiveness.

© 2026 Yaplet. All rights reserved.