Kit

Your assistant can pull the account's growth statistics over a date range and the email statistics for the last ninety days, then read the account record for the plan and the sending timezone those numbers are reported in. Kit returns growth in your sending timezone rather than UTC, which is the usual reason a hand-built weekly count never quite matches. Nothing here writes.

What you end up with. A written read on subscriber growth and email performance across the period, with the dates and timezone stated.

Start with it bringing you the information and you deciding.

Never without. Ask for net growth and its two halves, not one number. A month that added six hundred subscribers and lost five hundred and eighty reads as growth until somebody looks at the unsubscribes underneath it.

Built on: Get Account / Get Growth Stats / Get Email Stats

It can list your broadcasts, read a specific one, pull its statistics once it has been sent, and pull the link click data showing which links people actually clicked. Comparing the clicks to the subject line across the last dozen sends is the version worth asking for, because the click is the part that means something and the open rate has been unreliable for years.

What you end up with. A comparison of recent broadcasts by opens, clicks and unsubscribes, naming the links that got clicked in each.

Start with it bringing you the information and you deciding.

Never without. Do not rank sends on open rate alone. Mail privacy features fire opens nobody performed, so treat the open number as a rough signal and let the clicks and the unsubscribes carry the judgment.

Built on: List Broadcasts / Get Broadcast / Get Broadcast Stats / Get Broadcast Clicks

It can filter subscribers by engagement behavior, such as no opens or no clicks over a date range you set, read the individual engagement stats behind any name on that list, and trace people back to the form they joined through. That connects the two halves of the question: who has gone quiet, and whether one particular signup path produces people who never engage. Kit only holds subscriber-level event data from June 2025 onward, so an older account has a floor on how far back this looks.

What you end up with. A list of disengaged subscribers with their last activity and the form each one came in through.

Start with it bringing you the information and you deciding.

Never without. Silence is not the same as absence. Someone who never opens can still be reading in a preview pane or forwarding you to their team, so treat this as a list to look at rather than a list to act on automatically.

Built on: Filter Subscribers / List Subscribers / Get Subscriber / Get Subscriber Stats / List Forms / List Subscribers For Form

It can read your templates, creator profile and account colors, then create the broadcast itself. Leaving the send time empty saves it as a draft, which is the setting that matters: the same action with a future timestamp schedules real email to real people. Draft it, open it in Kit, and send it yourself.

What you end up with. A draft broadcast sitting in Kit with subject line and body written, ready for you to edit and send.

Start with it doing the work and checking with you.

Never without. Never let it set a send time. One field is the difference between a draft you can fix and a scheduled send to your entire list, and a broadcast that has gone out cannot be recalled.

Built on: List Email Templates / Get Creator Profile / Get Account Colors / Create Broadcast

It can read your existing tags, create the one this event needs, add or update each person by email, tag them, and add them to the relevant form. Kit treats subscriber creation as an upsert, so an existing person is updated rather than duplicated. The order matters, since the tag and form actions both require the person to exist in the account first.

What you end up with. Every attendee in Kit, tagged for this event and attached to the right form, with a list of who was new and who already existed.

Start with it doing the work and checking with you.

Never without. Check what the tag and the form are wired to before the import runs. Tags and form additions are what your sequences trigger on in Kit, so a bulk import can start a welcome sequence to two hundred people who thought they were signing up for one webinar.

Built on: List Tags / Create Tag / Create Subscriber / Tag Subscriber by Email / Add Subscriber to Form by Email

It can list the custom fields already defined, create a new one for the attribute you want to hold, and write values onto subscribers, up to a hundred and forty custom fields at a time. Renaming an existing field's label is a separate action from changing what is stored in it, which is worth keeping straight.

What you end up with. A custom field defined in Kit and populated for the subscribers you named, ready to segment on.

Start with it doing the work and checking with you.

Never without. Have it show the field-to-value mapping for a handful of people before it runs the rest. Custom field values are what your segments read, so a field filled from the wrong column quietly changes who receives what.

Built on: List Custom Fields / Create Custom Field / Update Custom Field / Update Subscriber

It can find the person and unsubscribe them, which in Kit removes them from every sequence and form and stops all email to them. Their historical data stays, and running it twice on the same person does nothing extra. Kit's own description calls this permanent, and there is no matching action to put somebody back.

What you end up with. The named person unsubscribed from everything, confirmed by reading their record back afterward.

Start with it doing the work and checking with you.

Never without. Confirm you have the right person by email, not by name, and never run this over a group described only as a rule. The connector offers no way to resubscribe anyone, so getting a paying customer back onto your list means asking them to sign up again.

Built on: List Subscribers / Get Subscriber / Delete Subscriber

It can list every tag with its creation date, count who is on each one, rename the ones worth keeping, remove a tag from specific people, and delete the ones that are dead. Two things here cannot be undone, so run it in stages: list first, rename next, and treat deletion as its own decision made against a list you have read.

What you end up with. A tag list you can actually use, with the survivors renamed consistently and a saved record of every tag removed and how many people it held.

Start with it doing the work and checking with you.

Never without. Never delete a tag or a custom field before checking what triggers on it. These are what sequences, forms and segments key off in Kit, so removing one takes the automation behind it with no way to restore the tag or recover the field values it held.

Built on: List Tags / List Tag Subscribers / Update Tag / Remove Tag From Subscriber / Delete Tag / Delete Custom Field