Domain events for a multi-platform data stream
This disclosure relates to methods, non-transitory computer readable media, and systems that relay domain-event objects within an enhanced multi-platform data stream to listen for and react to digital events indicated by the domain-event objects that occur across a wide variety of computing platforms. Specifically, the disclosed systems can receive domain-event objects within the multi-platform data stream. From among the domain-even objects transmitted through the multi-platform data stream, the disclosed systems can identify a domain-event object that is relevant to a digital-analytics platform by identifying domain-event objects that include properties satisfying domain-event-listener rules. Based on an entity identifier and an object event from the relevant domain-event object, the disclosed systems can perform a platform action within the digital-analytics platform (e.g., to react to a change in another platform as indicated by the domain-event object).
1. A computer-implemented method comprising:
generating a domain-event object schema for a domain-event object definition comprising domain-event-listener conditions used to identify domain-event objects that meet the domain-event object definition within a multi-platform data stream;
providing the domain-event object schema to a schema library for the multi-platform data stream;
identifying, within the multi-platform data stream, a domain-event object based on an entity identifier for the domain-event object satisfying the domain-event-listener conditions;
identifying an object event for the domain-event object; and
performing an action based on the object event for the domain-event object.
2. The computer-implemented method of claim 1 , further comprising determining that the entity identifier for the domain-event object satisfies the domain-event-listener conditions by determining that the entity identifier satisfies a logic condition for at least one of a type of digital entity, a digital-entity-creation time, an object-event-occurrence time, or an object-event type.
3. The computer-implemented method of claim 1 , further comprising:
in response to performing the action, generating an additional domain-event object comprising an additional entity identifier and an additional object event corresponding to the action; and
providing the additional domain-event object to the multi-platform data stream.
4. The computer-implemented method of claim 1 , wherein performing the action comprises at least one of transmitting an electronic communication, configuring a ticket, triggering a platform process, modifying a platform workflow, updating a digital reporting interface, or modifying a platform parameter within a digital-analytics platform to reflect the domain-event object.
5. The computer-implemented method of claim 1 , wherein identifying the object event comprises identifying at least one of a creation of, an assignment of, a transmission of, a modification to, an interaction with, a publication of, an update of, a sharing of, a subscription to, an unsubscription to, or a rejection of a digital entity corresponding to the entity identifier.
6. The computer-implemented method of claim 5 , wherein the digital entity comprises a contact, a form, a ticket, a response, a distribution, a survey invitation, a list member, or a segment member.
7. The computer-implemented method of claim 1 , further comprising:
determining that the domain-event object corresponds to a third-party platform; and
performing the action within a digital-analytics platform in response to a third-party platform action taken on the third-party platform as indicated by the domain-event object.
8. A non-transitory computer-readable storage medium comprising instructions that, when executed by at least one processor, cause a computing device to:
generate a domain-event object schema for a domain-event object definition comprising domain-event-listener conditions used to identify domain-event objects that meet the domain-event object definition within a multi-platform data stream;
provide the domain-event object schema to a schema library for the multi-platform data stream;
identify, within the multi-platform data stream, a domain-event object based on an entity identifier for the domain-event object satisfying the domain-event-listener conditions;
identify an object event for the domain-event object; and
perform an action based on the object event for the domain-event object.
9. The non-transitory computer-readable storage medium of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the computing device to determine that the entity identifier for the domain-event object satisfies the domain-event-listener conditions by determining that the entity identifier satisfies a logic condition for at least one of a type of digital entity, a digital-entity-creation time, an object-event-occurrence time, or an object-event type.
10. The non-transitory computer-readable storage medium of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the computing device to:
in response to performing the action, generate an additional domain-event object comprising an additional entity identifier and an additional object event corresponding to the action; and
provide the additional domain-event object to the multi-platform data stream.
11. The non-transitory computer-readable storage medium of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the computing device to perform the action by performing at least one of the following operations: transmitting an electronic communication, configuring a ticket, triggering a platform process, modifying a platform workflow, updating a digital reporting interface, or modifying a platform parameter within a digital-analytics platform to reflect the domain-event object.
12. The non-transitory computer-readable storage medium of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the computing device to identify the object event by identifying at least one of: a creation of, an assignment of, a transmission of, a modification to, an interaction with, a publication of, an update of, a sharing of, a subscription to, an unsubscription to, or a rejection of a digital entity corresponding to the entity identifier, wherein the digital entity comprises a contact, a form, a ticket, a response, a distribution, a survey invitation, a list member, or a segment member.
13. The non-transitory computer-readable storage medium of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the computing device to:
provide, for display within a graphical user interface of an administrator device, a selectable domain-event-listener condition in relation to the entity identifier for the domain-event object;
receive, from the administrator device, an indication of a selection of the selectable domain-event-listener condition; and
based on the selection of the selectable domain-event-listener condition, add the selectable domain-event-listener condition to the domain-event-listener conditions.
14. The non-transitory computer-readable storage medium of claim 13 , further comprising instructions that, when executed by the at least one processor, cause the computing device to:
provide, for display within the graphical user interface of the administrator device, a platform-action option for the action to be performed upon satisfaction of the selectable domain-event-listener condition;
receive, from the administrator device, an indication of a selection of the platform-action option; and
based on the selection of the platform-action option, associate the action with the domain-event-listener conditions such that the action is performed upon satisfying the selectable domain-event-listener condition.
15. A system comprising:
at least one processor; and
at least one non-transitory computer-readable storage medium comprising instructions that, when executed by the at least one processor, cause the system to:
generate a domain-event object schema for a domain-event object definition comprising domain-event-listener conditions used to identify domain-event objects that meet the domain-event object definition within a multi-platform data stream;
provide the domain-event object schema to a schema library for the multi-platform data stream;
identify, within the multi-platform data stream, a domain-event object based on an entity identifier for the domain-event object satisfying the domain-event-listener conditions;
identify an object event for the domain-event object; and
perform an action based on the object event for the domain-event object.
16. The system of claim 15 , wherein the at least one non-transitory computer-readable storage medium further comprises instructions that, when executed by the at least one processor, cause the system to determine that the entity identifier for the domain-event object satisfies the domain-event-listener conditions by determining that the entity identifier satisfies a logic condition for at least one of a type of digital entity, a digital-entity-creation time, an object-event-occurrence time, or an object-event type.
17. The system of claim 15 , wherein the at least one non-transitory computer-readable storage medium further comprises instructions that, when executed by the at least one processor, cause the system to perform the action by performing at least one of the following operations: transmitting an electronic communication, configuring a ticket, triggering a platform process, modifying a platform workflow, updating a digital reporting interface, or modifying a platform parameter within a digital-analytics platform to reflect the domain-event object.
18. The system of claim 15 , wherein the at least one non-transitory computer-readable storage medium further comprises instructions that, when executed by the at least one processor, cause the system to identify the object event by identifying at least one of: a creation of, an assignment of, a transmission of, a modification to, an interaction with, a publication of, an update of, a sharing of, a subscription to, an unsubscription to, or a rejection of a digital entity corresponding to the entity identifier.
19. The system of claim 15 , wherein the at least one non-transitory computer-readable storage medium further comprises instructions that, when executed by the at least one processor, cause the system to:
generate a new domain-event object schema for a new domain-event object definition comprising new domain-event-listener conditions used to identify a new domain-event object within the multi-platform data stream; and
provide the new domain-event object schema to the schema library for the multi-platform data stream.
20. The system of claim 15 , wherein the at least one non-transitory computer-readable storage medium further comprises instructions that, when executed by the at least one processor, cause the system to identify an additional action to perform based on the object event for the domain-event object.