Granted Patent B2

US 12,639,049 · App. 18/330,244 · Granted May 26, 2026

Inventors: Alexander Colin Meyer (Chicago, IL); Gerardo Díaz De La Serna Formoso (Mexico City, MX); Gideon Daniel VanRiette (Chicago, IL); James Quinlan (Richmond, VA); Joy Taylor Kaufman (Durham, NC); Kameron Ahler (Colorado, CO); Lauren Leia Rouse (Nashville, TN); Vishak Swaminathan Visvanathan (Brooklyn, NY)

Assignee: Stodge Inc.

G06F8/34G06F9/543

Abstract

Claims (66)

1 . A system, comprising:

at least one memory; and

at least one processor coupled with the at least one memory, the at least one memory storing code comprising instructions, the instructions when executed by the at least one processor cause a message management platform to perform steps comprising:

presenting a user interface configured to receive, from an application operator, a configuration of a message flow, the message flow being a campaign that targets more than one subscriber and, furthermore, comprising recipient criteria defining a segment of subscribers to receive messages from the message flow, at least one message in the message flow associated with a trigger condition, the message flow further comprising an exclusion trigger condition;

subscribing to at least one application programming interface (API) notification channel of an application builder platform, the application builder platform being operable as a backend component of an application controlled by the application operator;

receiving a plurality of API notifications from the application builder platform, the plurality of API notifications comprising respective API payloads that include information describing events associated with a plurality of users of the application builder platform, wherein one of the API notifications includes information that specifies a first event and a user identifier;

receiving a plurality of code-snippet notifications describing events associated with a plurality of user computing devices, wherein one of the code-snippet notifications specifies a second event and is received from a user computing device of the plurality of user computing devices via a corresponding code snippet incorporated in an instance of the application operated at the user computing device, and wherein the user computing device is associated with a corresponding subscriber identifier used by the message management platform, wherein the corresponding subscriber identifier is associated with a first subscriber;

determining that the user identifier included in the API notification received from the application builder platform corresponds to the subscriber identifier specified by the code-snippet notification received from the user computing device;

determining, based on receipt of both the first event included in the API notification received from the application builder platform and the second event specified in the code-snippet notification received from the user computing device, that the first subscriber satisfies the recipient criteria and enrolling the first subscriber to the segment of subscribers who are to receive messages from the message flow;

receiving one or more new notifications that describe one or more new subscriber events associated with the first subscriber;

determining that the one or more new subscriber events meet the trigger condition in the message flow and do not meet the exclusion trigger condition; and

transmitting the at least one message in the message flow that is associated with the trigger condition to the first subscriber.

2 . The system of claim 1 , wherein:

the user computing device is a first user computing device and the corresponding subscriber identifier is a first subscriber identifier;

one of the code-snippet notifications specifies a third event and is received from a second user computing device of the plurality of user computing devices, the second user computing device being associated with a corresponding second subscriber identifier used by the message management platform, wherein the second subscriber identifier is associated with a second subscriber;

the message flow has a scheduled start; and

the instructions when executed by the at least one processor cause a message management platform to perform steps further comprising:

determining, based on the third event, that the second subscriber satisfies the recipient criteria and enrolling the second subscriber to the segment of subscribers who are to receive messages from the message flow, wherein the first and second subscribers are enrolled at the scheduled start.

3 . The system of claim 1 , wherein the exclusion trigger condition is a conversion event.

4 . The system of claim 1 , wherein the exclusion trigger condition is a cancellation event.

5 . The system of claim 1 , wherein the instructions when executed by the at least one processor cause a message management platform to perform steps further comprising:

responsive to detection of an event that is associated with the first subscriber and that satisfies the exclusion trigger condition, removing the first subscriber from the segment of subscribers who are to receive messages from the message flow.

6 . The system of claim 1 , wherein the message flow is linear.

7 . The system of claim 1 , wherein:

the message flow includes a message branching;

the trigger condition is a first trigger condition; and

the message flow includes a second trigger condition associated with the message branching.

8 . The system of claim 1 , wherein the message flow has an end condition.

9 . The system of claim 1 , wherein the at least one message in the message flow that is associated with the trigger condition to the first subscriber is an initial message of the message of the message flow.

10 . The system of claim 1 , wherein the at least one message in the message flow that is associated with the trigger condition to the first subscriber is a subsequent message to an initial message of the message of the message flow.

11 . The system of claim 1 , wherein the first event is a purchase or a browsing event.

12 . The system of claim 1 , wherein the second event is a purchase or a browsing event.

13 . A computer-implemented method for a message management platform, the method comprising:

presenting a user interface configured to receive, from an application operator, a configuration of a message flow, the message flow being a campaign that targets more than one subscriber and, furthermore, comprising recipient criteria defining a segment of subscribers to receive messages from the message flow, at least one message in the message flow associated with a trigger condition, the message flow further comprising an exclusion trigger condition;

subscribing to at least one application programming interface (API) notification channel of an application builder platform, the application builder platform being operable as a backend component of an application controlled by the application operator;

receiving a plurality of API notifications from the application builder platform, the plurality of API notifications comprising respective API payloads that include information describing events associated with a plurality of users of the application builder platform, wherein one of the API notifications includes information that specifies a first event and a user identifier;

receiving a plurality of code-snippet notifications describing events associated with a plurality of user computing devices, wherein one of the code-snippet notifications specifies a second event and is received from a user computing device of the plurality of user computing devices via a corresponding code snippet incorporated in an instance of the application operated at the user computing device, and wherein the user computing device is associated with a corresponding subscriber identifier used by the message management platform, wherein the corresponding subscriber identifier is associated with a first subscriber;

determining that the user identifier included in the API notification received from the application builder platform corresponds to the subscriber identifier specified in the code-snippet notification received from the user computing device;

determining, based on receipt of both the first event included in the API notification received from the application builder platform and the second event specified in the code-snippet notification received from the user computing device, that the first subscriber satisfies the recipient criteria and enrolling the first subscriber to the segment of subscribers who are to receive messages from the message flow;

receiving one or more new notifications that describe one or more new subscriber events associated with the first subscriber;

determining that the one or more new subscriber events meet the trigger condition in the message flow and do not meet the exclusion trigger condition; and

transmitting the at least one message in the message flow that is associated with the trigger condition to the first subscriber.

14 . The computer-implemented method of claim 13 , wherein:

the user computing device is a first user computing device and the corresponding subscriber identifier is a first subscriber identifier;

one of the code-snippet notifications specifies a third event and is received from a second user computing device of the plurality of user computing devices, the second user computing device being associated with a corresponding second subscriber identifier used by the message management platform, wherein the second subscriber identifier is associated with a second subscriber;

the message flow has a scheduled start; and

the computer-implemented method further comprising:

determining, based on the third event, that the second subscriber satisfies the recipient criteria and enrolling the second subscriber to the segment of subscribers who are to receive messages from the message flow, wherein the first and second subscribers are enrolled at the scheduled start.

15 . The computer-implemented method of claim 13 , wherein the exclusion trigger condition is a conversion event or a cancellation event.

16 . The computer-implemented method of claim 13 , further comprising:

responsive to detection of an event that is associated with the first subscriber and that satisfies the exclusion trigger condition, removing the first subscriber from the segment of subscribers who are to receive messages from the message flow.

17 . The computer-implemented method of claim 13 , wherein:

the message flow includes a message branching;

the trigger condition is a first trigger condition; and

the message flow includes a second trigger condition associated with the message branching.

18 . The computer-implemented method of claim 13 , wherein the at least one message in the message flow that is associated with the trigger condition to the first subscriber is an initial message of the message of the message flow.

19 . A computer-program product stored on tangible media, the product comprising computer instructions executable to cause a message management platform to perform steps comprising:

presenting a user interface configured to receive, from an application operator, a configuration of a message flow, the message flow being a campaign that targets more than one subscriber and, furthermore, comprising recipient criteria defining a segment of subscribers to receive messages from the message flow, at least one message in the message flow associated with a trigger condition, the message flow further comprising an exclusion trigger condition;

subscribing to at least one application programming interface (API) notification channel of an application builder platform, the application builder platform being operable as a backend component of an application controlled by the application operator;

receiving a plurality of API notifications from the application builder platform, the plurality of API notifications comprising respective API payloads that include information describing events associated with a plurality of users of the application builder platform, wherein one of the API notifications includes information that specifies a first event and a user identifier;

receiving a plurality of code-snippet notifications describing events associated with a plurality of user computing devices, wherein one of the code-snippet notifications specifies a second event and is received from a user computing device of the plurality of user computing devices via a corresponding code snippet incorporated in an instance of the application operated at the user computing device, and wherein the user computing device is associated with a corresponding subscriber identifier used by the message management platform, wherein the corresponding subscriber identifier is associated with a first subscriber;

determining that the user identifier included in the API notification received from the application builder platform corresponds to the subscriber identifier specified in the code-snippet notification received from the user computing device;

determining, based on receipt of both the first event included in the API notification received from the application builder platform and the second event specified in the code-snippet notification received from the user computing device, that the first subscriber satisfies the recipient criteria and enrolling the first subscriber to the segment of subscribers who are to receive messages from the message flow;

receiving one or more new notifications that describe one or more new subscriber events associated with the first subscriber;

determining that the one or more new subscriber events meet the trigger condition in the message flow and do not meet the exclusion trigger condition; and

transmitting the at least one message in the message flow that is associated with the trigger condition to the first subscriber.

Assignments (3)

Continuity (2)

References Cited (384)