# US 2018/0024873 A1 · System and method for tagging and tracking events of an application platform > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2018/0024873 A1 - Document ID: US20180024873A1 - Status: Published application - Kind: A1 - Application number: 15/719,860 - Filed: 2017-09-29 - Published: 2018-01-25 - Earliest claimed: 2013-09-17 - Assignees: Twilio Inc. - Applicants: Twilio, Inc. - Inventors: Timothy S. Milliron; Adam Ballai; Robert Hagemann - Web page: https://patentgrep.com/patent/US20180024873A1 ## CPC - G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications} - G06F 9/466: {Transaction processing} - G06F 11/3065: {Monitoring arrangements determined by the means or processing involved in reporting the monitored data (error or fault reporting or logging G06F11/0766)} - G06F 11/3089: {Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents (software debugging using additional hardware using a specific debug interface G06F11/3656; performance evaluation by tracing or monitoring G06F11/3466)} - G06F 2201/86: Event-based monitoring - G06F 2201/88: Monitoring involving counting - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A system and method for providing delegated metric tools within a partially closed communication platform that includes receiving a tag identifier linked to at least a first identified platform interaction in the communication platform; associating the tag identifier with at least one logged event of an account associated with the first identified platform interaction; defining a tracking resource with at least one tag identifier; measuring platform interactions tracked by a tracking resource; and providing access to measured platform interactions through an application. ## Claims ### Claim 1 A method comprising: an event tracking system receiving, from an external multi-tenant application platform system, first usage trigger configuration for a first platform account of the platform system; the event tracking system storing the first usage trigger configuration; the event tracking system receiving at least one event publication from the multi-tenant application platform system via an interface of the event tracking system; for each event publication received via the interface: the event tracking system determining whether the event publication is associated with the first usage trigger configuration, and responsive to a determination that the event publication is associated with the first usage trigger configuration, the event tracking system incrementing a first counter associated with the first usage trigger configuration; and responsive to a determination that the first counter satisfies a first trigger condition of the first usage trigger configuration, the event tracking system sending a request to one of the platform system and an external application server system of the first platform account, in accordance with a first trigger action of the first usage trigger configuration. ### Claim 2 (depends on 1) The method of claim 1, wherein the first usage trigger configuration includes the first trigger condition, the first trigger action, and a first usage key, and wherein the event tracking system receives the first usage trigger configuration as a first request through an application programming interface (API) of the event tracking system. ### Claim 3 (depends on 2) The method of claim 2, wherein the first usage trigger configuration is received with a first token used to authenticate permission to create a usage trigger, wherein the event tracking system uses the first token of the first usage trigger configuration to authenticate permission to create a usage trigger, and wherein the event tracking system stores the first usage trigger configuration responsive to authentication of permission to create a usage trigger by using the first token. ### Claim 4 (depends on 2) The method of claim 2, wherein the first usage key specifies counting of a first event of the first platform account of the multi-tenant application platform system. ### Claim 5 (depends on 1) The method of claim 1, further comprising: the event tracking system receiving platform usage trigger configuration for a plurality of platform accounts of the external multi-tenant application platform system. ### Claim 6 (depends on 1) The method of claim 1, further comprising: the event tracking system receiving platform usage trigger configuration for a plurality of external multi-tenant application platform systems. ### Claim 7 (depends on 1) The method of claim 1, wherein the event tracking system sends the request to the platform system, in accordance with the first trigger action of the first usage trigger configuration. ### Claim 8 (depends on 1) The method of claim 1, wherein the event tracking system sends the request to the application server system of the first platform account, in accordance with the first trigger action of the first usage trigger configuration. ### Claim 9 (depends on 1) The method of claim 1, wherein the first usage trigger configuration includes the first trigger condition, the first trigger action, and a first usage key, wherein the event tracking system receives the first usage trigger configuration as a first request through an application programming interface (API) of the event tracking system, wherein the first usage trigger configuration is received with a first token used to authenticate permission to create a usage trigger, wherein the event tracking system uses the first token of the first usage trigger configuration to authenticate permission to create a usage trigger, wherein the event tracking system stores the first usage trigger configuration responsive to authentication of permission to create a usage trigger by using the first token, wherein the first usage key specifies counting of a first event of the first platform account of the multi-tenant application platform system, further comprising: the event tracking system receiving platform usage trigger configuration for a plurality of platform accounts of the external multi-tenant application platform system, and further comprising: the event tracking system receiving platform usage trigger configuration for a plurality of external multi-tenant application platform systems. ### Claim 10 (depends on 9) The method of claim 9, wherein the event tracking system sends the request to the platform system, in accordance with the first trigger action of the first usage trigger configuration. ### Claim 11 (depends on 9) The method of claim 9, wherein the event tracking system sends the request to the application server system of the first platform account, in accordance with the first trigger action of the first usage trigger configuration. ### Claim 12 An event tracking system comprising: a usage trigger database; a transaction system; and a trigger action processor, wherein the event tracking system is constructed to receive, from an external multi-tenant application platform system, first usage trigger configuration for a first platform account of the platform system, and store the first usage trigger configuration in the usage trigger database, wherein the transaction system is constructed to receive at least one event publication from the multi-tenant application platform system via an interface of the transaction system; wherein, for each event publication received via the interface, the transaction system is constructed to: determine whether the event publication is associated with the first usage trigger configuration, and responsive to a determination that the event publication is associated with the first usage trigger configuration, increment a first counter associated with the first usage trigger configuration; and wherein responsive to a determination that the first counter satisfies a first trigger condition of the first usage trigger configuration, the trigger action processor is constructed to send a request to one of the platform system and an external application server system of the first platform account, in accordance with a first trigger action of the first usage trigger configuration. ### Claim 13 (depends on 12) The system of claim 12, wherein the first usage trigger configuration includes the first trigger condition, the first trigger action, and a first usage key, and wherein the event tracking system is constructed to receive the first usage trigger configuration as a first request through an application programming interface (API) of the event tracking system. ### Claim 14 (depends on 13) The system of claim 13, wherein the first usage trigger configuration is received with a first token used to authenticate permission to create a usage trigger, wherein the event tracking system is constructed to use the first token of the first usage trigger configuration to authenticate permission to create a usage trigger, and wherein the event tracking system is constructed to store the first usage trigger configuration responsive to authentication of permission to create a usage trigger by using the first token. ### Claim 15 (depends on 13) The system of claim 13, wherein the first usage key specifies counting of a first event of the first platform account of the multi-tenant application platform system. ### Claim 16 (depends on 12) The system of claim 12, wherein the event tracking system is constructed to receive platform usage trigger configuration for a plurality of platform accounts of the external multi-tenant application platform system. ### Claim 17 (depends on 12) The system of claim 12, wherein the event tracking system is constructed to receive platform usage trigger configuration for a plurality of external multi-tenant application platform systems. ### Claim 18 (depends on 12) The system of claim 12, wherein the event tracking system is constructed to send the request to the platform system, in accordance with the first trigger action of the first usage trigger configuration. ### Claim 19 (depends on 12) The system of claim 12, wherein the event tracking system is constructed to send the request to the application server system of the first platform account, in accordance with the first trigger action of the first usage trigger configuration. ### Claim 20 (depends on 12) The system of claim 12, wherein the first usage trigger configuration includes the first trigger condition, the first trigger action, and a first usage key, wherein the event tracking system is constructed to receive the first usage trigger configuration as a first request through an application programming interface (API) of the event tracking system, wherein the first usage trigger configuration is received with a first token used to authenticate permission to create a usage trigger, wherein the event tracking system is constructed to use the first token of the first usage trigger configuration to authenticate permission to create a usage trigger, wherein the event tracking system is constructed to store the first usage trigger configuration responsive to authentication of permission to create a usage trigger by using the first token, wherein the first usage key specifies counting of a first event of the first platform account of the multi-tenant application platform system, wherein the event tracking system is constructed to receive platform usage trigger configuration for a plurality of platform accounts of the external multi-tenant application platform system, and wherein the event tracking system is constructed to receive platform usage trigger configuration for a plurality of external multi-tenant application platform systems.