Sending the email digest

Digest is under Tangilla Data in the left-hand menu. It is the screen that sends your subscriber email.

⚠️ This screen sends real email to real people, and it cannot be undone. Read this article before using it. There is a test option — use it every time.

What the screen tells you

At the top you'll see:

  • How many confirmed subscribers there are. These are the people who will receive it.
  • The queue — which items are waiting to go out, grouped by topic.

Items reach the queue on their own. Published news articles and active job openings go in automatically; documents go in only when Notify Subscribers is ticked. Nothing is added here.

If the queue is empty, there is nothing to send and the screen will tell you so.

Always send a test first

Under Send a test, enter your own email address and send. You get exactly what subscribers would get, and nothing is marked as sent, so you can test as many times as you like.

Check the test for:

  • The right items, and nothing you didn't expect
  • Links that go where they should
  • Anything that reads oddly out of context

A test costs nothing. Sending to everyone with a mistake in it costs a great deal.

Run for real

Under Run for real, the button mails every confirmed subscriber the items matching their chosen topics, and marks those items as sent.

You'll be asked to confirm, and the confirmation tells you exactly how many people and how many items are involved — for example "This mails 412 confirmed subscriber(s) about 6 item(s) and marks them as sent. It cannot be undone."

Read those two numbers before you click Send it. They are your last chance to notice that the queue holds something you didn't intend to send.

Once it has run

  • Each item is marked as sent and will not go out again, even if you run the digest later that day.
  • Subscribers only receive items matching the topics they chose, so no two people necessarily get the same email.
  • There is no recall. An email that has gone has gone.

If something is in the queue that shouldn't be

Deal with it before you run, not after.

  • A news article that shouldn't go out — unpublish it, or set an expiry date in the past.
  • A job opening — untick Active.
  • A document — untick Notify Subscribers.

Then reload the Digest screen and confirm the queue looks right.

Who should use this

Anyone sending this should understand that it reaches every subscriber immediately. If you are not sure whether something should go out, ask before running it — the queue will still be there tomorrow.

Related

  • Subscribers
  • News
  • Documents
  • Job Openings
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.