Every time you send a press release, OmniCon records a distribution — a snapshot of what went out, to whom, and whether it arrived. The history page is where you come back to audit what you did, spot deliverability problems, and plan the next send.
Where to find it
From the channel's dashboard: Press → History. You'll see every distribution from this channel, most recent first, with the article title, the send date, and a recipient count.
What a distribution record contains
- Article — which article was sent (linked to the article's dashboard page).
- Subject — the subject line as sent, not the current article title. Useful when you've since edited the article.
- Custom message — the pitch note you typed at send time, if any.
- Sent by — the user who clicked Send.
- Sent at — the timestamp.
- Recipients — every contact that was on the selected lists at send time, with their status.
Recipient status values
- Pending — queued, not yet attempted.
- Sent — the mail server accepted the message for delivery.
- Failed — delivery attempt failed. The most common cause is a bad or outdated email address.
Status updates happen asynchronously as the mail queue drains — reload the distribution page after a few minutes to see the final state.
What to do with the data
- Investigate Failed recipients. Open the press contact, check whether the email is still valid, update it, and re-send if needed.
- Prune stale contacts. A contact that Fails on multiple consecutive distributions is probably a dead address.
- Audit what went out. When someone asks "did we send the Q2 announcement to that outlet?", this is the source of truth.
- Compare send patterns. Are your weekday sends delivering better than your Friday sends? Is the EMEA list smaller than it should be? The history page is the starting point for those questions.
What the history does not tell you
- Opens and clicks. OmniCon tracks delivery, not engagement. Open/click tracking would need email-pixel instrumentation that's not in v1.
- Replies. If a journalist replies to the release, it goes to the sender's inbox — OmniCon doesn't capture it. Look in your mail client.
- Coverage. Whether a release led to an article is human work — search, Google Alerts, a simple spreadsheet.
Re-sending
Distribution history is read-only — you can't "re-send" a distribution as a one-click action. If you need to send the same article again (to a different list, with a corrected subject, or after fixing a bounced address), go back to Send and run the flow again. This creates a new distribution record so the history stays a clean log of actual events.
Deleting
Distribution records don't have a delete action in v1, and that's intentional — the history is an audit trail. If you need one removed (for example, a test send that shouldn't be in the record), open a support request.