# US 10,771,425 B2 · Electronic message lifecycle management

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 10,771,425 B2
- Document ID: US10771425B2
- Status: Granted
- Kind: B2
- Application number: 15/884,251
- Filed: 2018-01-30
- Published: 2018-08-02
- Granted: 2020-09-08
- Earliest claimed: 2017-01-30
- Assignees: HubSpot, Inc.
- Applicants: HubSpot Inc.
- Inventors: James Kebinger; Farid Jahanmir; Sean Patrick Hogan; Ryan Kophs; Nathaniel Dempkowski; Michael Axiak; Tom Monaghan
- Web page: https://patentgrep.com/patent/US10771425B2

## CPC

- H04L 51/234: for tracking messages
- G06N 3/08: Learning methods
- G06N 3/09: Supervised learning
- G06N 7/01: Probabilistic graphical models, e.g. probabilistic networks
- G06N 20/00: Machine learning
- G06Q 10/107: Computer-aided management of electronic mailing [e-mailing]
- G06Q 30/0248: {Avoiding fraud}
- G06Q 30/0277: {Online advertisement}
- H04L 51/08: Annexed information, e.g. attachments
- H04L 51/18: Commands or executable codes
- H04L 51/212: using filtering or selective blocking
- H04L 51/42: Mailbox-related aspects, e.g. synchronisation of mailboxes
- H04L 51/48: Message addressing, e.g. address format or anonymous messages, aliases
- H04L 61/5007: Internet protocol [IP] addresses
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

Provided herein is an electronic message management platform that enables management and execution of electronic message campaigns while appropriately managing challenges presented by spam filters, black lists, and domain blocking technologies, and that includes elements for managing an electronic message campaign based on dynamic conditions, quality measures, engagement factors, and other measures, factors and conditions.

## Claims

### Claim 1

A method of managing a lifecycle of an electronic message comprising:
preparing a message for delivery by adding at least one header value that facilitates identifying the message;
updating at least one link in the message to include metadata that facilitates identifying a recipient of the message, wherein the at least one link in the message include at least one target URL;
tracking and recording life cycle events throughout a delivery phase and an engagement phase of the lifecycle of the message; and
determining at least one of a degree of engagement and a quality of engagement of the recipient with the message based on at least a portion of the tracked and recorded life cycle events,
wherein updating the at least one link in the message comprises rewriting the at least one target URL based at least in part on a type of the message, wherein the type of the message is a plain text email or an HTML email, and
wherein updating the at least one link in the message comprises rewriting the at least one target URL into a short URL that is a link to a resolution server that redirects to a longer URL that provides access to a resource that is consistent with the at least one target URL.

### Claim 2 (depends on 1)

The method of claim 1, wherein delivery phase life cycle events include at least one of send events, drop events, processing events, delivery events, deferred delivery events, and bounced delivery events.

### Claim 3 (depends on 1)

The method of claim 1, wherein the engagement phase life cycle events include at least one of message open events, message content link engagement events, message forward events, message reply events, duration of engagement events, and status change events.

### Claim 4 (depends on 1)

The method of claim 1, wherein preparing the message for delivery includes updating attribute data of the message with at least one of recipient identification information and client sender identification information.

### Claim 5 (depends on 1)

The method of claim 1, wherein updating the at least one link in the message includes rewriting a link to include at least one of an encoding of the at least one target URL in the link and the metadata that facilitates the resource at the at least one target URL to identify the recipient of the message.

### Claim 6 (depends on 1)

The method of claim 1, wherein tracking life cycle events includes detecting when data comprising the prepared message has been transmitted from a system on which the message was prepared.

### Claim 7 (depends on 1)

The method of claim 1, wherein recording life cycle events comprises storing at least one of the at least one header value and the updated links in a message-specific lifecycle event storage facility accessible to a processor.

### Claim 8 (depends on 1)

The method of claim 1, further comprising receiving an indication that at least one of the links is selected by the recipient of the message, the indication based at least in part on the metadata.

### Claim 9

A non-transitory computer readable medium containing executable instructions that, when executed by a processor, cause the processor to manage a lifecycle of an electronic message by:
preparing a message for delivery by adding at least one header value that facilitates identifying the message;
updating at least one link in the message to include metadata that facilitates identifying a recipient of the message, wherein the at least one link in the message includes at least one target URL;
tracking and recording life cycle events throughout a delivery phase and an engagement phase of the lifecycle of the message; and
determining at least one of a degree of engagement and a quality of engagement of the recipient with the message based on at least a portion of the tracked and recorded life cycle events,
wherein updating the at least one link in the message comprises rewriting the at least one target URL based at least in part on a type of the message, wherein the type of the message is a plain text email or an HTML email, and
wherein updating the at least one link in the message comprises rewriting the at least one target URL into a short URL that is a link to a resolution server that redirects to a longer URL that provides access to a resource that is consistent with the at least one target URL.

### Claim 10 (depends on 9)

The non-transitory computer readable medium of claim 9, wherein delivery phase life cycle events include at least one of send events, drop events, processing events, delivery events, deferred delivery events, and bounced delivery events.

### Claim 11 (depends on 9)

The non-transitory computer readable medium of claim 9, wherein the engagement phase life cycle events include at least one of message open events, message content link engagement events, message forward events, message reply events, duration of engagement events, and status change events.

### Claim 12 (depends on 9)

The non-transitory computer readable medium of claim 9, wherein preparing the message for delivery includes updating attribute data of the message with at least one of recipient identification information and client sender identification information.

### Claim 13 (depends on 9)

The non-transitory computer readable medium of claim 9, wherein updating the at least one link in the message includes rewriting a link to include at least one of an encoding of the at least one target URL in the link and the metadata that facilitates the resource at the at least one target URL to identify the recipient of the message.

### Claim 14 (depends on 9)

The non-transitory computer readable medium of claim 9, wherein tracking life cycle events includes detecting when data comprising the prepared message has been transmitted from a system on which the message was prepared.

### Claim 15 (depends on 9)

The non-transitory computer readable medium of claim 9, wherein recording life cycle events comprises storing at least one of the at least one header value and the updated links in a message-specific lifecycle event storage facility accessible to the processor.

### Claim 16 (depends on 9)

The non-transitory computer readable medium of claim 9, further comprising receiving an indication that at least one of the links is selected by the recipient of the message, the indication based at least in part on the metadata.