IP Library Granted Patent US 8,719,356
Granted Patent B2
US 8,719,356 · App. 13/449,153 · Granted May 6, 2014

Methods, systems, and computer readable media for monitoring deliverability of electronic mail based on subscriber and seed deliverability data

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,719,356
App. No.
13/449,153
Granted
May 6, 2014
Kind
B2
Abstract

A system monitor delivery of electronic mail based on subscriber and seed deliverability data. Seed deliverability data is received that includes information indicating a number of email messages associated with an email campaign that are delivered to a folder associated with one or more intended recipients of the email campaign based on a sampling of seed accounts. The seed accounts are not associated with actual recipients of the email campaign. Subscriber deliverability data is received that includes information indicating a number of email messages associated with the email campaign that are delivered to a folder associated with the one or more intended recipients of the email campaign based on one or more subscriber accounts. The seed accounts are associated with a subset of human recipients of the email campaign. One or more deliverability metrics are determined based on the seed deliverability data and the subscriber deliverability data.

Claims (32)

1. A method for monitoring deliverability of electronic mail based on subscriber and seed deliverability data, the method comprising:

receiving at a seed deliverability storage database, seed deliverability data that includes information indicating a number of email messages associated with an email campaign that are delivered to a folder associated with one or more intended recipients of the email campaign based on a sampling of seed accounts, wherein the seed accounts are not associated with human recipients of the email campaign;

receiving at a subscriber deliverability storage database, subscriber deliverability data that includes information indicating a number of email messages associated with the email campaign that are delivered to a folder associated with the one or more intended recipients of the email campaign based on one or more subscriber accounts, wherein the subscriber accounts are associated with a subset of actual recipients of the email campaign;

determining at a processor, one or more deliverability metrics based on the seed deliverability data and the subscriber deliverability data; and

matching at the processor a subscriber campaign to a seeded campaign by determining at the processor a list of matching IDs associated with the seeded campaign and matching at the processor the matching IDs with the seeded campaign.

2. The method of claim 1 further comprising matching subscriber campaigns associated with campaign senders by parsing a matching ID included in an email header.

3. The method of claim 2 wherein the matching is performed in real-time or near real-time.

4. The method of claim 1 wherein determining one or more deliverability metrics includes using at least one of a domain, a subject line, or an IP address to combine the seed deliverability data and the subscriber deliverability data.

5. The method of claim 1 wherein the matching ID includes an x-header value.

6. The method of claim 1 further comprising displaying the deliverability metrics.

7. The method of claim 1 further comprising receiving deliverability data associated with the email campaign directly from one of an internet service provider (ISP) and an email service provider (ESP).

8. The method of claim 1 wherein the subscriber deliverability data is obtained using a plugin configured to communicate with an email program of the recipient.

9. The method of claim 1 wherein each matching ID uniquely represents a campaign.

10. The method of claim 1 further comprising automatically using one of subscriber data exclusively or seed data exclusively, for an ISP, in the event that the number of mailboxes from which folder placement data is received is greater than or less than a predetermined threshold value.

11. A non-transitory computer-readable medium that is not a signal, the medium having stored thereon computer executable instructions that when executed by the processor of a computer perform steps comprising:

receiving seed deliverability data that includes information indicating a number of email messages associated with an email campaign that are delivered to a folder associated with one or more intended recipients of the email campaign based on a sampling of seed accounts, wherein the seed accounts are not associated with human recipients of the email campaign;

receiving subscriber deliverability data that includes information indicating a number of email messages associated with the email campaign that are delivered to a folder associated with the one or more intended recipients of the email campaign based on one or more subscriber accounts, wherein the subscriber accounts are associated with a subset of actual recipients of the email campaign;

determining one or more deliverability metrics based on the seed deliverability data and the subscriber deliverability data; and

matching at the processor a subscriber campaign to a seeded campaign by determining at the processor a list of matching IDs associated with the seeded campaign and matching at the processor the matching IDs with the seeded campaign.

12. A system for monitoring deliverability of electronic mail based on subscriber and seed deliverability data, the system comprising:

a seed deliverability storage database for receiving and storing seed deliverability data that includes information indicating a number of email messages associated with an email campaign that are delivered to a folder associated with one or more intended recipients of the email campaign based on a sampling of seed accounts, wherein the seed accounts are not associated with actual recipients of the email campaign;

a subscriber deliverability storage database for receiving and storing subscriber deliverability data that includes information indicating a number of email messages associated with the email campaign that are delivered to a folder associated with the one or more intended recipients of the email campaign based on one or more subscriber accounts, wherein the subscriber accounts are associated with a subset of human recipients of the email campaign; and

a processor device configured to determine one or more deliverability metrics based on the seed deliverability data and the subscriber deliverability data, wherein the processor device is configured to match a subscriber campaign to a seeded campaign by determining a list of matching IDs associated with the seeded campaign and matching the matching IDs with the seeded campaign.

13. The system of claim 12 wherein the processor device is configured to match subscriber campaigns associated with campaign senders by parsing a matching ID included in an email header.

14. The system of claim 13 wherein the processor device is configured to perform the matching in real-time or near real-time.

15. The system of claim 12 wherein the processor device is configured to use at least one of a domain, a subject line, or an IP address to combine the seed deliverability data and the subscriber deliverability data.

16. The system of claim 12 wherein the matching ID includes an x-header value.

17. The system of claim 12 wherein the processor device is configured to display the deliverability metrics.

18. The system of claim 12 wherein the processor device is configured to receive deliverability data associated with the email campaign directly from one of an internet service provider (ISP) and an email service provider (ESP).

19. The system of claim 12 wherein the subscriber deliverability storage database is configured to receive subscriber deliverability data from a plugin configured to communicate with an email program of the recipient.

20. The system of claim 12 wherein the matching ID uniquely represents a campaign.

21. The system of claim 12 wherein the processor device is configured to determine the one or more deliverability metrics based on one of the subscriber data exclusively or the seed data exclusively, for an ISP, in the event that the number of mailboxes from which folder placement data is received is greater than or less than a predetermined threshold value.

Assignments (10)
SECOND LIEN INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Jun 24, 2025
From: VALIDITY, INC.
To: BARCLAYS BANK PLC, AS ADMINISTRATIVE AGENT
Reel/Frame 071730/0300 →
RELEASE OF SECURITY INTEREST Recorded Apr 10, 2025
From: ANTARES CAPITAL LP, AS ADMINISTRATIVE AGENT
To: VALIDITY, INC.
Reel/Frame 070805/0665 →
SECURITY INTEREST Recorded Apr 10, 2025
From: VALIDITY, INC.
To: BARCLAYS BANK PLC, AS ADMINISTRATIVE AGENT
Reel/Frame 070798/0113 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 4, 2022
From: RETURN PATH, INC.
To: VALIDITY, INC.
Reel/Frame 058889/0153 →
RELEASE OF SECURITY INTEREST Recorded Jun 7, 2019
From: PACIFIC WESTERN BANK
To: RETURN PATH, INC.
Reel/Frame 049403/0074 →
SECURITY INTEREST Recorded May 30, 2019
From: RETURN PATH, INC.
To: ANTARES CAPITAL LP, AS ADMINISTRATIVE AGENT
Reel/Frame 049315/0256 →
RELEASE OF SECURITY INTEREST Recorded Apr 11, 2019
From: SILICON VALLEY BANK
To: RETURN PATH, INC.
Reel/Frame 048857/0919 →
SECURITY INTEREST Recorded Feb 8, 2018
From: RETURN PATH, INC.
To: PACIFIC WESTERN BANK
Reel/Frame 044870/0217 →
SECURITY AGREEMENT Recorded Jun 22, 2015
From: RETURN PATH, INC.
To: SILICON VALLEY BANK
Reel/Frame 035997/0654 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 30, 2012
From: DILLINGHAM, JEREMY K.; NOCCHIERO, PETER J.; OAKE, CHRISTOPHER J.; JORDAN, SEAN E.; ISAC, SHEELA; BILBREY, GEORGE MARVIN, III
To: RETURN PATH INC.
Reel/Frame 028127/0362 →