Granted Patent B2

US 12,255,860 · App. 18/485,639 · Granted Mar 18, 2025

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, CA); Lauren Leia Rouse (Nashville, TN); Vishak Swaminathan Visvanathan (Brooklyn, NY)

Assignee: Stodge Inc.

H04L51/214H04L51/234H04L51/48

Abstract

Claims (86)

1. A system, comprising:

software code instructions executable by a computing device to:

provide a user interface;

receive, via the user interface, a message-flow plan of a merchant, wherein the message-flow plan specifies a message flow that is a campaign to be distributed to multiple users, wherein the message-flow plan includes a scheduled start of the campaign, wherein the message-flow plan specifies criteria defining a target segment, and wherein at least one message of the message-flow plan is associated with a trigger condition different than the criteria; and

transmit the message-flow plan; and

a message management platform comprising one or more processors and memory, the memory configured to store code instructions executable by the one or more processors to:

receive the message-flow plan;

subscribe to receive application programming interface (API) notifications from an application builder platform that provides server-side services for an e-commerce application of the merchant, wherein the e-commerce application executes client-side on user devices, and wherein the API notifications include information describing events related to the server-side services;

receive an API notification from the application builder platform, the API notification including a user ID of a user and information describing a first event that is attributable to the user ID, wherein the first event is a completed transaction event associated with an order placed by the user on the e-commerce application;

determine, based on the first event and at the scheduled start of the campaign, that the user qualifies under the criteria to be included in the target segment and enroll the user in the campaign;

receive either another API notification from the application builder platform that includes the user ID, or a code-snippet notification from an instance of the e-commerce application executing on a device of the user, wherein the code-snippet notification includes information that specifies a device ID of the device, which device ID is different from the user ID, and wherein the code-snippet notification further includes information describing a second event that is attributable to the device ID, the device ID being correlated to the user ID; and

determine, based on an event associated with said another API notification from the application builder platform or based on the second event, that the trigger condition is met and, in response, transmit the at least one message associated with the trigger condition to the enrolled user.

2. The system of claim 1 , wherein the memory is further configured to store code instructions executable by the one or more processors to:

receive, for the user enrolled in the campaign, a notification including information describing a new event attributable to the user;

determine that the new event meets an exclusion condition; and

responsive to determining that the new event meets the exclusion condition, remove the user from a group of users enrolled in the campaign.

3. The system of claim 2 , wherein the new event is one of a completed transaction event and a user opt-out event.

4. The system of claim 1 , wherein the criteria defining the target segment is further based on tags specifying user characteristics.

5. The system of claim 1 , wherein the memory is further configured to store code instructions executable by the one or more processors to:

transmit, to each user enrolled in the campaign and at the scheduled start of the campaign, an initial message to the user per the message-flow plan prior to transmitting the at least one message associated with the trigger condition.

6. The system of claim 1 , wherein the memory is further configured to store code instructions executable by the one or more processors to:

receive another code-snippet notification from the instance of the e-commerce application executing on the device of the user, the another code-snippet notification including information describing a third event that is attributable to the device ID;

wherein the instructions to determine that the user qualifies under the criteria to be included in the target segment and enroll the user in the campaign further comprises instructions to qualify at the scheduled start of the campaign based on the first event and the third event.

7. The system of claim 1 , wherein each code-snippet notification is generated by a code snippet of the message management platform, the code snippet being listed in a digital distribution platform of the application builder platform.

8. The system of claim 1 , wherein the API notifications received from the application builder platform are webhook notifications.

9. The system of claim 1 , wherein the memory is further configured to store code instructions executable by the one or more processors to:

introduce a delay of a predetermined amount of time as dictated by the message-flow plan prior to execution of the instruction to determine that the trigger condition is met.

10. The system of claim 1 , wherein the second event is a browsing event.

11. A system, comprising:

software code instructions executable by a computing device to:

provide for display a user interface;

receive, via the user interface, a message-flow plan of a merchant, wherein the message-flow plan specifies a message flow that is a campaign to be distributed to multiple users, wherein the message-flow plan includes a scheduled start of the campaign, wherein the message-flow plan specifies criteria defining a target segment, and wherein at least one message of the message-flow plan is associated with a trigger condition different than the criteria; and

transmit the message-flow plan; and

a message management platform comprising one or more processors and memory, the memory configured to store code instructions executable by the one or more processors to:

receive the message-flow plan;

subscribe to receive application programming interface (API) notifications from an application builder platform that provides server-side services for an e-commerce application of the merchant, wherein the e-commerce application executes client-side on user devices, and wherein the API notifications include information describing events related to the server-side services;

receive a code-snippet notification from an instance of the e-commerce application executing on a device of a user, wherein the code-snippet notification includes information that specifies a device ID of the device, wherein the code-snippet notification further includes information describing a first event that is attributable to the device ID;

determine, based on the first event and at the scheduled start of the campaign, that the user qualifies under the criteria to be included in the target segment and enroll the user in the campaign;

receive either another code-snippet notification that includes information that specifies the device ID, or an API notification from the application builder platform, the API notification from the application builder platform including a user ID of the user and information describing a second event that is attributable to the user ID, the user ID being correlated to the device ID, wherein the second event is a completed transaction event associated with an order placed by the user on the e-commerce application; and

determine, based on an event associated with said another code-snippet notification or based on the second event, that the trigger condition is met and, in response, transmit the at least one message associated with the trigger condition to the enrolled user.

12. The system of claim 11 , wherein the memory is further configured to store code instructions executable by the one or more processors to:

receive, for the user enrolled in the campaign, a notification including information describing a new event attributable to the user;

determine that the new event meets an exclusion condition; and

responsive to determining that the new event meets the exclusion condition, remove the user from a group of users enrolled in the campaign.

13. The system of claim 12 , wherein the new event is one of a completed transaction event and a user opt-out event.

14. The system of claim 11 , wherein the criteria defining the target segment is further based on tags specifying user characteristics.

15. The system of claim 11 , wherein the memory is further configured to store code instructions executable by the one or more processors to:

transmit, to each user enrolled in the campaign and at the scheduled start of the campaign, an initial message to the user per the message-flow plan prior to transmitting the at least one message associated with the trigger condition.

16. The system of claim 11 , wherein the memory is further configured to store code instructions executable by the one or more processors to:

receive another API notification from the application builder platform, wherein said another API notification includes the user ID of the user and information describing a third event that is attributable to the user ID, wherein the third event is a completed transaction event associated with an order placed by the user on the e-commerce application;

wherein the determination that the user qualifies under the criteria at the scheduled start of the campaign to be included in the target segment and enroll the user in the campaign is responsive to the correlation and is further based on the first event and the third event.

17. The system of claim 11 , wherein each code-snippet notification is generated by a code snippet of the message management platform, the code snippet being listed in a digital distribution platform of the application builder platform.

18. The system of claim 11 , wherein the API notifications received from the application builder platform are webhook notifications.

19. The system of claim 11 , wherein the memory is further configured to store code instructions executable by the one or more processors to:

introduce a delay of a predetermined amount of time as dictated by the message-flow plan prior to determining execution of the instructions to determine that the trigger condition is met.

20. The system of claim 11 , wherein the first event is a browsing event.

21. A computer-implemented method, comprising:

receiving, via a user interface, a message-flow plan of a merchant, wherein the message-flow plan specifies a message flow that is a campaign to be distributed to multiple users, wherein the message-flow plan includes a scheduled start of the campaign, wherein the message-flow plan specifies criteria defining a target segment, and wherein at least one message of the message-flow plan is associated with a trigger condition different than the criteria;

subscribing to receive application programming interface (API) notifications from an application builder platform that provides server-side services for an e-commerce application of the merchant, wherein the e-commerce application executes client-side on user devices, and wherein the API notifications include information describing events related to the server-side services;

receiving API notifications from the application builder platform, a first API notification including a first user ID of a first user and information describing a first event that is attributable to the first user ID, a second API notification including a second user ID of a second user and information describing a second event that is attributable to the second user ID, wherein each of the first event and the second event is a completed transaction event associated with an order placed by the first user or the second user on the e-commerce application;

determining, based on the first and second events and at the scheduled start of the campaign, that the first and second users qualify under the criteria to be included in the target segment and enroll the first and second users in the campaign;

receiving either (i) another API notification from the application builder platform that includes the first user ID, wherein said another API notification includes information describing a third event that is attributable to the first user ID, or (ii) a code-snippet notification from an instance of the e-commerce application executing on a device of the first user, wherein the code-snippet notification includes information that specifies a device ID of the device, which device ID is different from the first user ID, and wherein the code-snippet notification further includes information describing a fourth event that is attributable to the device ID, the device ID being correlated to the first user ID; and

determining, based on either the third or fourth events, depending on which one was received, that the trigger condition is met and, in response, transmit the at least one message associated with the trigger condition to the enrolled first user.

22. The computer-implemented method of claim 21 , further comprising:

receiving, for the first user enrolled in the campaign, a notification including information describing a new event attributable to the first user;

determining that the new event meets an exclusion condition; and

responsive to determining that the new event meets the exclusion condition, removing the first user from a group of users enrolled in the campaign.

23. The computer-implemented method of claim 22 , wherein the new event is one of a completed transaction event and a user opt-out event.

24. The computer-implemented method of claim 21 , wherein the criteria defining the target segment is further based on tags specifying user characteristics.

25. The computer-implemented method of claim 21 , further comprising:

transmitting, to each of the first and second users enrolled in the campaign and at the scheduled start of the campaign, an initial message to the user per the message-flow plan prior to transmitting the at least one message associated with the trigger condition.

26. A non-transitory computer-readable medium storing code instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:

receiving, via a user interface, a message-flow plan of a merchant, wherein the message-flow plan specifies a message flow that is a campaign to be distributed to multiple users, wherein the message-flow plan includes a scheduled start of the campaign, wherein the message-flow plan specifies criteria defining a target segment, and wherein at least one message of the message-flow plan is associated with a trigger condition different than the criteria;

subscribing to receive application programming interface (API) notifications from an application builder platform that provides server-side services for an e-commerce application of the merchant, wherein the e-commerce application executes client-side on user devices, and wherein the API notifications include information describing events related to the server-side services;

receiving API notifications from the application builder platform, a first API notification including a first user ID of a first user and information describing a first event that is attributable to the first user ID, a second API notification including a second user ID of a second user and information describing a second event that is attributable to the second user ID, wherein each of the first event and the second event is a completed transaction event associated with an order placed by the first user or the second user on the e-commerce application;

determining, based on the first and second events and at the scheduled start of the campaign, that the first and second users qualify under the criteria to be included in the target segment and enroll the first and second users in the campaign;

receiving either (i) another API notification from the application builder platform that includes the first user ID, wherein said another API notification includes information describing a third event that is attributable to the first user ID, or (ii) a code-snippet notification from an instance of the e-commerce application executing on a device of the first user, wherein the code-snippet notification includes information that specifies a device ID of the device, which device ID is different from the first user ID, and wherein the code-snippet notification further includes information describing a fourth event that is attributable to the device ID, the device ID being correlated to the first user ID; and

determining, based on either the third or fourth events, depending on which one was received, that the trigger condition is met and, in response, transmit the at least one message associated with the trigger condition to the enrolled first user.

27. The non-transitory computer-readable medium of claim 26 , wherein the code instructions further cause the one or more processors to perform operations comprising:

receiving, for the first user enrolled in the campaign, a notification including information describing a new event attributable to the first user;

determining that the new event meets an exclusion condition; and

responsive to determining that the new event meets the exclusion condition, removing the first user from a group of users enrolled in the campaign.

28. The non-transitory computer-readable medium of claim 27 , wherein the new event is one of a completed transaction event and a user opt-out event.

29. The non-transitory computer-readable medium of claim 26 , wherein the criteria defining the target segment is further based on tags specifying user characteristics.

30. The non-transitory computer-readable medium of claim 26 , wherein the code instructions further cause the one or more processors to perform an operation comprising:

transmitting, to each of the first and second users enrolled in the campaign and at the scheduled start of the campaign, an initial message to the user per the message-flow plan prior to transmitting the at least one message associated with the trigger condition.

Assignments (3)

Continuity (2)

References Cited (377)