Systems and methods for generating performance profiles of nodes

The present application is a continuation of P.C.T. Patent Application No. PCT/US2019/034030, filed on May 24, 2019, which claims the benefit of and priority to U.S. Provisional Patent Application 62/747,452, filed Oct. 18, 2018, U.S. Provisional Patent Application 62/725,999, filed Aug. 31, 2018, U.S. Provisional Patent Application 62/676,187, filed May 24, 2018, U.S. patent application Ser. No. 16/213,754, filed Dec. 7, 2018, U.S. patent application Ser. No. 16/237,579, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,580, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,582, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,585, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/371,048, filed Mar. 31, 2019, U.S. patent application Ser. No. 16/420,059, filed May 22, 2019, U.S. patent application Ser. No. 16/421,280, filed May 23, 2019, U.S. patent application Ser. No. 16/421,288, filed May 23, 2019, U.S. patent application Ser. No. 16/421,298, filed May 23, 2019, U.S. patent application Ser. No. 16/421,151, filed May 23, 2019, U.S. patent application Ser. No. 16/421,309, filed May 23, 2019, and U.S. patent application Ser. No. 16/421,328, filed May 23, 2019, each of which are incorporated herein by reference for all purposes.

The present application is a continuation of P.C.T. Patent Application No. PCT/US2019/034046, filed on May 24, 2019, which claims the benefit of and priority to U.S. Provisional Patent Application 62/747,452, filed Oct. 18, 2018, U.S. Provisional Patent Application 62/725,999, filed Aug. 31, 2018, U.S. Provisional Patent Application 62/676,187, filed May 24, 2018, U.S. patent application Ser. No. 16/213,754, filed Dec. 7, 2018, U.S. patent application Ser. No. 16/237,579, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,580, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,582, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,585, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/371,048, filed Mar. 31, 2019, U.S. patent application Ser. No. 16/420,059, filed May 22, 2019, U.S. patent application Ser. No. 16/421,280, filed May 23, 2019, U.S. patent application Ser. No. 16/421,288, filed May 23, 2019, U.S. patent application Ser. No. 16/421,298, filed May 23, 2019, U.S. patent application Ser. No. 16/421,151, filed May 23, 2019, U.S. patent application Ser. No. 16/421,309, filed May 23, 2019, and U.S. patent application Ser. No. 16/421,328, filed May 23, 2019, each of which are incorporated herein by reference for all purposes.

The present application is a continuation of P.C.T. Patent Application No. PCT/US2019/034050, filed on May 24, 2019, which claims the benefit of and priority to U.S. Provisional Patent Application 62/747,452, filed Oct. 18, 2018, U.S. Provisional Patent Application 62/725,999, filed Aug. 31, 2018, U.S. Provisional Patent Application 62/676,187, filed May 24, 2018, U.S. patent application Ser. No. 16/213,754, filed Dec. 7, 2018, U.S. patent application Ser. No. 16/237,579, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,580, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,582, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,585, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/371,048, filed Mar. 31, 2019, U.S. patent application Ser. No. 16/371,037, filed Mar. 31, 2019, U.S. patent application Ser. No. 16/371,041, filed Mar. 31, 2019, U.S. patent application Ser. No. 16/398,220, filed Apr. 29, 2019, U.S. patent application Ser. No. 16/399,706, filed Apr. 30, 2019, and U.S. patent application Ser. No. 16/418,629, filed May 21, 2019, each of which are incorporated herein by reference for all purposes.

The present application is a continuation of P.C.T. Patent Application No. PCT/US2019/034052, filed on May 24, 2019, which claims the benefit of and priority to U.S. Provisional Patent Application 62/747,452, filed Oct. 18, 2018, U.S. Provisional Patent Application 62/725,999, filed Aug. 31, 2018, U.S. Provisional Patent Application 62/676,187, filed May 24, 2018, U.S. patent application Ser. No. 16/213,754, filed Dec. 7, 2018, U.S. patent application Ser. No. 16/237,579, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,580, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,582, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,585, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/360,884, filed Mar. 21, 2019, U.S. patent application Ser. No. 16/360,884, filed Mar. 21, 2019, U.S. patent application Ser. No. 16/360,997, filed Mar. 21, 2019, U.S. patent application Ser. No. 16/361,009, filed Mar. 21, 2019, U.S. patent application Ser. No. 16/361,025, filed Mar. 21, 2019, U.S. patent application Ser. No. 16/371,035, filed Mar. 31, 2019, U.S. patent application Ser. No. 16/399,690, filed Apr. 30, 2019, U.S. patent application Ser. No. 16/418,539, filed May 21, 2019, and U.S. patent application Ser. No. 16/418,725, filed May 21, 2019, each of which are incorporated herein by reference for all purposes.

The present application is a continuation of P.C.T. Patent Application No. PCT/US2019/034042, filed on May 24, 2019, which claims the benefit of and priority to U.S. Provisional Patent Application 62/747,452, filed Oct. 18, 2018, U.S. Provisional Patent Application 62/725,999, filed Aug. 31, 2018, U.S. Provisional Patent Application 62/676,187, filed May 24, 2018, U.S. patent application Ser. No. 16/213,754, filed Dec. 7, 2018, U.S. patent application Ser. No. 16/237,579, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,580, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,582, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,585, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/360,866, filed Mar. 21, 2019, U.S. patent application Ser. No. 16/360,933, filed Mar. 21, 2019, U.S. patent application Ser. No. 16/360,953, filed Mar. 21, 2019, U.S. patent application Ser. No. 16/398,153, filed Apr. 29, 2019, U.S. patent application Ser. No. 16/418,769, filed May 21, 2019, and U.S. patent application Ser. No. 16/418,891, filed May 21, 2019, each of which are incorporated herein by reference for all purposes.

The present application is a continuation of P.C.T. Patent Application No. PCT/US2019/034045, filed on May 24, 2019, which claims the benefit of and priority to U.S. Provisional Patent Application 62/747,452, filed Oct. 18, 2018, U.S. Provisional Patent Application 62/725,999, filed Aug. 31, 2018, U.S. Provisional Patent Application 62/676,187, filed May 24, 2018, U.S. patent application Ser. No. 16/213,754, filed Dec. 7, 2018, U.S. patent application Ser. No. 16/237,579, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,580, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,582, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,585, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/371,042, filed Mar. 31, 2019, U.S. patent application Ser. No. 16/371,050, filed Mar. 31, 2019, U.S. patent application Ser. No. 16/398,157, filed Apr. 29, 2019, U.S. patent application Ser. No. 16/399,768, filed Apr. 30, 2019, U.S. patent application Ser. No. 16/418,747, filed May 21, 2019, U.S. patent application Ser. No. 16/418,851, filed May 21, 2019, U.S. patent application Ser. No. 16/418,867, filed May 22, 2019, and U.S. patent application Ser. No. 16/420,052, filed May 22, 2019, each of which are incorporated herein by reference for all purposes.

The present application is a continuation of P.C.T. Patent Application No. PCT/US2019/034070, filed on May 24, 2019, which claims the benefit of and priority to U.S. Provisional Patent Application 62/747,452, filed Oct. 18, 2018, U.S. Provisional Patent Application 62/725,999, filed Aug. 31, 2018, U.S. Provisional Patent Application 62/676,187, filed May 24, 2018, U.S. patent application Ser. No. 16/213,754, filed Dec. 7, 2018, U.S. patent application Ser. No. 16/237,579, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,580, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,582, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,585, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/398,260, filed Apr. 29, 2019, U.S. patent application Ser. No. 16/421,324, filed May 23, 2019, and U.S. patent application Ser. No. 16/421,370, filed May 23, 2019, each of which are incorporated herein by reference for all purposes.

The present application is a continuation of P.C.T. Patent Application No. PCT/US2019/034033, filed on May 24, 2019, which claims the benefit of and priority to U.S. Provisional Patent Application 62/747,452, filed Oct. 18, 2018, U.S. Provisional Patent Application 62/725,999, filed Aug. 31, 2018, U.S. Provisional Patent Application 62/676,187, filed May 24, 2018, U.S. patent application Ser. No. 16/213,754, filed Dec. 7, 2018, U.S. patent application Ser. No. 16/237,579, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,580, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,582, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,585, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/399,679, filed Apr. 30, 2019, U.S. patent application Ser. No. 16/418,807, filed May 21, 2019, U.S. patent application Ser. No. 16/418,846, filed May 21, 2019, U.S. patent application Ser. No. 16/419,583, filed May 22, 2019, and U.S. patent application Ser. No. 16/420,039, filed May 22, 2019, each of which are incorporated herein by reference for all purposes.

The present application is a continuation of P.C.T. Patent Application No. PCT/US2019/034068, filed on May 24, 2019, which claims the benefit of and priority to U.S. Provisional Patent Application 62/747,452, filed Oct. 18, 2018, U.S. Provisional Patent Application 62/725,999, filed Aug. 31, 2018, U.S. Provisional Patent Application 62/676,187, filed May 24, 2018, U.S. patent application Ser. No. 16/213,754, filed Dec. 7, 2018, U.S. patent application Ser. No. 16/237,579, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,580, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,582, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,585, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/360,892, filed Mar. 21, 2019, U.S. patent application Ser. No. 16/371,039, filed Mar. 31, 2019, U.S. patent application Ser. No. 16/371,049, filed Mar. 31, 2019, U.S. patent application Ser. No. 16/399,787, filed Apr. 30, 2019, U.S. patent application Ser. No. 16/400,000, filed Apr. 30, 2019, and U.S. patent application Ser. No. 16/418,826, filed May 21, 2019, each of which are incorporated herein by reference for all purposes.

The present application is a continuation of P.C.T. Patent Application No. PCT/US2019/034062, filed on May 24, 2019, which claims the benefit of and priority to U.S. Provisional Patent Application 62/747,452, filed Oct. 18, 2018, U.S. Provisional Patent Application 62/725,999, filed Aug. 31, 2018, U.S. Provisional Patent Application 62/676,187, filed May 24, 2018, U.S. patent application Ser. No. 16/213,754, filed Dec. 7, 2018, U.S. patent application Ser. No. 16/237,579, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,580, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,582, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/237,585, filed Dec. 31, 2018, U.S. patent application Ser. No. 16/398,150, filed Apr. 29, 2019, U.S. patent application Ser. No. 16/418,836, filed May 21, 2019, U.S. patent application Ser. No. 16/418,892, filed May 21, 2019, and U.S. patent application Ser. No. 16/421,256, filed May 21, 2019, each of which are incorporated herein by reference for all purposes.

An organization may attempt to manage or maintain a system of record associated with electronic communications at the organization. The system of record can include information such as contact information, logs, and other data associated with the electronic activities. Data regarding the electronic communications can be transmitted between computing devices associated with one or more organizations using one or more transmission protocols, channels, or formats, and can contain various types of information. For example, the electronic communication can include information about a sender of the electronic communication, a recipient of the electronic communication, and content of the electronic communication. The information regarding the electronic communication can be input into a record being managed or maintained by the organization. However, due to the large volume of heterogeneous electronic communications transmitted between devices and the challenges of manually entering data, inputting the information regarding each electronic communication into a system of record can be challenging, time consuming, and error prone.

The present disclosure relates to systems and methods for constructing a node graph based on electronic activity. The node graph can include a plurality of nodes and a plurality of edges between the nodes indicating activity or relationships that are derived from a plurality of data sources that can include one or more types of electronic activities. The plurality of data sources can further include systems of record, such as customer relationship management systems, enterprise resource planning systems, document management systems, applicant tracking systems or other sources of data that may maintain electronic activities, activities or records.

The present disclosure further relates to systems and methods for using the node graph to manage, maintain, improve, or otherwise modify one or more systems of record by linking and or synchronizing electronic activities to one or more record objects of the systems of record. In particular, the systems described herein can be configured to automatically synchronize real-time or near real-time electronic activity to one or more objects of systems of record. The systems can further extract business process information from the systems of record and in combination with the node graph, use the extracted business process information to improve business processes and to provide data driven solutions to improve such business processes.

At least one aspect of the present disclosure is directed to systems and methods for maintaining an electronic activity derived member node network. For example, a node profile for a member node in a node graph can include information such as first name, last name, company, and job title. However, it may be challenging to accurately and efficiently populate fields in a node profile due to large number of member nodes. Furthermore, permitting self-population of node profiles by member nodes can result in erroneous data values, improper data values, or otherwise undesired data values due in part to human bias. Having erroneous data values in a node profile can cause downstream components or functions that perform processing using the node profiles to malfunction or generate faulty outputs.

Thus, systems and methods of the present technical solution can generate an electronic activity derived member node network that includes node profiles for a member node that is generated based on electronic activity. By generating the member node profile for the member node using electronic activity and a statistical analysis, the system can generate the profile with data fields and values that pass a verification process or statistical analysis using electronic activities.

According to at least one aspect of the disclosure a method can include accessing, by one or more processors, a plurality of electronic activities that are transmitted or received via electronic accounts of one or more data source providers. The method can include accessing, by the one or more processors, a plurality of record objects of one or more systems of record. Each of the record object of the plurality of record objects can correspond to a record object type. Each of the record objects can include one or more object fields having one or more object field values. The system or record can correspond to the one or more data source providers. The method can include identifying, by the one or more processors, an electronic activity of the plurality of electronic activities to match to one or more record objects. The electronic activity of the plurality of electronic activities can identify participants that can include a sender of the electronic activity and one or more recipients of the electronic activity. The method can include determining, by the one or more processors, a data source provider associated with providing the one or more processors access to the electronic activity. The method can include identifying, by the one or more processors, a system of record corresponding to the determined data source provider. The system of record can include a plurality of candidate record objects to which to match the electronic activity. The method can include determining, by the one or more processors and responsive to applying a first policy including one or more filtering rules, that the electronic activity is to be matched to at least one record object of the identified system of record. The method can include identifying, by the one or more processors and responsive to applying a second policy including one or more rules for identifying candidate record objects based on one or more participants of the electronic activity, one or more candidate record objects to which to match the electronic activity. The method can include selecting, by the one or more processors, at least one candidate record object based on the second policy. The method can include storing, by the one or more processors, in a data structure an association between the selected at least one candidate record object and the electronic activity.

In some implementations, identifying the system of record corresponding to the determined data source provider can include identifying, by the one or more processors, the system of record based on a domain associated with an email address of the sender of the electronic activity. Determining that the electronic activity is to be matched to at least one record object of the identified system of record can include determining that the electronic activity does not satisfy one or more filtering rules configured to cause the one or more processors to restrict the electronic activity from being matched to the at least one record object. The filtering rules can include at least one of i) a keyword rule configured to restrict electronic activities including a predetermined keyword; ii) a regex pattern rule configured to restrict electronic activities including one or more character strings that match a predetermined regex pattern; iii) a logic-based rule configured to restrict electronic activities based on the participants of the electronic activities satisfying a predetermined group of participants.

The filtering rules can be defined by the data source provider of the electronic activity and the system of record to which to match the electronic activity. Determining that the electronic activity is to be matched to at least one record object of the identified system of record can include determining that the electronic activity does not include one or more predetermined words included in a list of restricted words. Determining to match the electronic activity can include determining that the electronic activity does not include any character strings that have a regular expression (regex) pattern that matches a predefined regex pattern included in a list of restricted regex patterns. Determining to match the electronic activity can include determining that the sender and at least one of the one or more recipients match a list of restricted sender-recipient pairs.

The method can include selecting candidate record objects based on a first policy and a second policy. The second policy can include a first set of rules and a second set of rules. The candidate record objects can be identified by applying the second policy including the first set of rules for identifying candidate record objects based on one or more recipients of the electronic activity. The first set of rules can identify a first set of candidate record objects to which to match the electronic activity. Each of the candidate record objects of the first set can be identified based on the one or more recipients of the electronic activity. The method can include identifying, by the one or more processors, responsive to applying the second policy including the second set of rules for identifying candidate record objects based on the sender of the electronic activity, a second set of candidate record objects to which to match the electronic activity. Each of the candidate record object of the second set can be identified based on the sender of the electronic activity. The method can include selected at least one candidate record object included in both the first set of candidate record objects and the second set of candidate record objects. The selected candidate record object can be match to the electronic activity based on the first set of rules and the second set of rules of the second policy.

The method can include identifying, responsive to applying the second policy, the first set of candidate record objects by applying a first matching rule of the first set of rules to identify one or more first record objects corresponding to a first record object type and applying a second matching rule of the first set of rules to identify one or more second record objects corresponding to a second record object type. The second policy can assign a first priority level to the first matching rule and a second priority level to the second matching rule. The first priority level can be greater than the second priority level. The method can include receiving, from the data source provider, at least one instruction to select a subset of the first set of rules or the second set of rules and assign a first priority to a first matching rule of the subset and assign a second priority level to a second matching rule of the subset.

In some implementations, the method can include determining, by the one or more processors, that a first electronic activity previously matched to a first record object of the data source provider is matched to a second record object of the data source provider. The method can include determining, by the one or more processors, one or more matching policies of the data source provider that apply to the first electronic activity. The method can include updating, by the one or more processors, responsive to determining that the first electronic activity previously matched to the first record object is matched to the second record object, the one or more matching policies for the data source provider such that the one or more processors can match a second electronic activity including the participants of the first electronic activity to the second record object. The method can include identifying one or more candidate record objects of a first record object type based on the recipients of the electronic activity.

In some implementations, the first set of rules can include a rule to identify one or more record objects of a first record object type based on an object field value of the record object that identifies one or more nodes. Identifying, responsive to applying the second policy, the first set of candidate record objects can include identifying one or more candidate record objects of the first record object type responsive to determining that the one or more of the participants are identified by the object field value.

The object field value can be a value of a first object field corresponding to an object owner that identifies an owner of the record object or a second object field corresponding to a team that identifies a group of people linked with the record object in the system of record. Identifying, responsive to applying the second policy, the first set of candidate record objects can include identifying a particular record object of the data source provider responsive to determining that the electronic activity includes a predetermined character string that satisfies a rule to match electronic activities including the character string to a particular record object. The second set of rules can include a rule to identify one or more record objects of a first record object type that are linked with the sender of the electronic activity. Identifying, responsive to applying the second policy, the second set of candidate record objects can include identifying one or more record objects that identify the sender as an object field value to an object field of the record object.

The second set of rules can include a rule to identify one or more record objects of a first record object type based on an object field value of the record object that identifies one or more nodes. Identifying, responsive to applying the second policy, the second set of candidate record objects can include identifying one or more candidate record objects of the first record object type responsive to determining that the one or more of the participants are identified by the object field value.

The method can include retrieving, from one or more second servers, a first plurality of record objects corresponding to a first system of record of a first data source provider and second plurality of record objects corresponding to a second system of record of a second data source provider. The method can include assigning, by the one or more processors, one or more tags to the electronic activity based on a first character string included in a body of the electronic activity; ii) a second character string included in a metadata of the electronic activity; or iii) other electronic activity.

The method can include identifying, by the one or more processors, at least one candidate record object of the one or more record objects based on one or more tags assigned to the electronic activity. The method can include determining, by the one or more processors, for at least one of the participants of the electronic activity, a respective unique identifier used by the system of record corresponding to the data source provider to represent the participant.

According to at least one aspect of the disclosure a method can include maintaining, by one or more processors, a plurality of node profiles. The node profiles can correspond to a plurality of unique entities. Each of the node profiles can include a plurality of fields. Each field of the plurality of fields can include one or more value data structures. Each value data structure of the one or more value data structures can include a node field value and one or more entries corresponding to respective one or more data points that support the node field value of the value data structure. The method can include accessing, by the one or more processors, a plurality of electronic activities transmitted or received via electronic accounts that can be associated with one or more data source providers. The one or more processors can be configured to update the plurality of node profiles using the plurality of electronic activities. The method can include maintaining, by the one or more processors, a plurality of record objects of one or more systems of record. Each record object of the plurality of record objects can include one or more object fields having one or more object field values. The method can include extracting, by the one or more processors, data included in an electronic activity of the plurality of electronic activities. The method can include matching, by the one or more processors, the electronic activity to at least one node profile of the plurality of node profiles based on determining that the extracted data of the electronic activity and the one or more values of the fields of the at least one node profile satisfy a node profile matching policy. The method can include matching, by the one or more processors, the electronic activity to at least one record object of the plurality of record objects based on the extracted data of the electronic activity and object values of the at least one record object. The method can include storing, by the one or more processors, in a data structure, an association between the electronic activity and the at least one record object.

In some implementations, the method can include retrieving, from one or more second processors, a first plurality of record objects corresponding to a first system of record of a first data source provider and second plurality of record objects corresponding to a second system of record of a second data source provider. The method can include identifying, by the one or more processors, a sender of the electronic activity of the plurality of electronic activities. The method can include selecting, by the one or more processors, a first node profile of the plurality of node profiles associated with the sender of the electronic activity. The method can include identifying, by the one or more processors, a first set of record objects of the plurality of record objects of the one or more systems of record based on the first node profile.

In some implementations, the method can include identifying, by the one or more processors, a recipient of the electronic activity of the plurality of electronic activities. The method can include selecting, by the one or more processors, a second node profile of the plurality of node profiles associated with the recipient of the electronic activity. The method can include identifying, by the one or more processors, a second set of record objects of the plurality of record objects of the one or more systems of record based on the second node profile. The method can include matching the electronic activity to the at least one record object of the plurality of record objects based on an intersection of the first set of record objects and the second set of record objects.

In some implementations, the method can include determining, by the one or more processors, a plurality of candidate record objects based on the intersection of the first set of record objects and the second set of record objects. The method can include identifying, by the one or more processors, each of the plurality of candidate record objects as belonging to one of a plurality of record object types. The method can include matching the electronic activity to two or more of the plurality of candidate record objects. Each of the two or more of the plurality of candidate record objects can include a different record object type.

In some implementations, matching the electronic activity to at least one record object can include matching the electronic activity to the at least one record object based on a matching policy. The matching policy can include a first set of rules for identifying candidate record objects based on one or more recipients of the electronic activity and a second set of rules for identifying candidate record objects based on the sender of the electronic activity. Matching the electronic activity to the at least one record object can include identifying, by the one or more processors, responsive to applying the policy including the first set of rules for identifying candidate record objects based on one or more recipients of the electronic activity, a first set of candidate record objects to which to match the electronic activity. Each of the candidate record objects of the first set can be identified based on the one or more recipients of the electronic activity. The method can include identifying, by the one or more processors, responsive to applying the second policy including the second set of rules for identifying candidate record objects based on the sender of the electronic activity, a second set of candidate record objects to which to match the electronic activity. Each of the candidate record object of the second set can be identified based on the sender of the electronic activity. The method can include selecting by the one or more processors, at least one candidate record object included in both the first set of candidate record objects and the second set of candidate record objects to match to the electronic activity based on the first set of rules and the second set of rules of the matching policy.

In some implementations, the method can include selecting, by the one or more processors, based on natural language processing, a string in a body of the electronic activity. The method can include selecting, by the one or more processors, a plurality of candidate record objects based on the string in the body of the electronic activity. Matching the electronic activity to at least one record object of the plurality of record objects can include matching the electronic activity to at least one of the plurality of candidate record objects. In some implementations, the method can include matching the electronic activity to two or more node profiles of the plurality of node profiles based on determining that the extracted data of the electronic activity and the one or more values of the fields of the two or more node profiles satisfy the node profile matching policy. The method can include determining, by the one or more processors, a relationship between two or more node profiles based on the one or more values of the fields of the two or more node profiles. The method can include assigning, by the one or more processors, one or more tags to the electronic activity based on the relationship between the two or more node profiles.

In some implementations, the method can include assigning, by the one or more processors, one or more tags to the electronic activity. The tags can be assigned based on i) one or more node profiles associated with a sender or one or more recipients of the electronic activity; ii) relationship between the one or more node profiles associated with the sender and the one or more recipients of the electronic activity; iii) a first string included in a body of the electronic activity; iv) a second string included in a metadata of the electronic activity; or v) other electronic activity.

In some implementations, the method can include identifying, by the one or more processors, a first subset of record objects of the plurality of record objects of the one or more systems of record based on one or more tags assigned to the electronic activity. Matching the electronic activity to at least one record object of the plurality of record objects can include matching the electronic activity to at least one of the first subset of record objects of the plurality of record objects based on the one or more tags assigned to the electronic activity.

In some implementations, the method can include identifying, by the one or more processors, a sender and one or more recipients of the electronic activity of the plurality of electronic activities. Matching the electronic activity to at least one node profile of the plurality of node profiles can include matching the electronic activity to a node profile of the sender and a node profile of each of the one or more recipients.

In some implementations, the method can include selecting, by the one or more processors, a first set of record objects of the plurality of record objects of the one or more systems of record based on a node field value of the node profile of the sender. The method can include selecting, by the one or more processors, a second set of record objects of the plurality of record objects of the one or more systems of record based on a node field value of the node profiles of each of the one or more recipients.

The method can include identifying, by the one or more processors, a subset of the plurality of electronic activities matched to a first record object of the plurality of record objects. The method can include identifying, by the one or more processors, for each electronic activity of the subset of the plurality of electronic activities matched to the first record object, one or more node profiles that are matched with the electronic activity. The method can include determining, by the one or more processors, a stage of the first record object based on the identified one or more node profiles of each of the subset of electronic activities. The method can include identifying, by the one or more processors, a subset of the plurality of electronic activities matched to a first record object of the plurality of record objects. The method can include determining, by the one or more processors, a stage of the first record object based on tags assigned to one or more electronic activities of the subset of electronic activities.

The method can include identifying, by the one or more processors, for a record object, a corresponding record object maintained by a second processor. The method can include determining, by the one or more processors, a plurality of processor assigned stages associated with the corresponding record object. Each stage of the plurality of processor assigned stages can indicate a proximity to completion of an event. The method can include mapping, by the one or more processors, each processor assigned stage of the corresponding record object to a stage of a plurality of system assigned stages of the record object. The method can include determining, by the one or more processors, for at least one data point of the one or more data points of a value of a field of the node profile, a contribution score of the data point based on a time corresponding to when the data point was generated or updated. The method can include generating, by the one or more processors, a confidence score of the value of the field of the node profile based on the contribution score of the data point.

The method can include matching, by the one or more processors, the electronic activity to the at least one node profile of the plurality of node profiles based on the confidence score of the value of the field of the at least one node profile. Determining the contribution score can include determining, for the at least one data point, a contribution score of the data point based on a trust score assigned to a source of the data point, the trust score determined based on a type of source of the data point.

According to at least one aspect of the disclosure a method can accessing, by one or more processors, a plurality of electronic activities transmitted or received via electronic accounts associated with a plurality of data source providers, the one or more processors maintaining a plurality of node profiles and configured to update the plurality of node profiles using the plurality of electronic activities. The method can include identifying, by the one or more processors, from data included in an electronic activity of the plurality of electronic activities to link to one or more node profiles, a plurality of strings. The method can include generating, by the one or more processors, a plurality of activity field-value pairs from the plurality of strings using an electronic activity parsing policy. The method can include comparing, by the one or more processors, the plurality of activity field-value pairs to respective node field value pairs of one or more node profiles maintained by the one or more processors to identify a subset of activity field value pairs that match respective node field-value pairs of the one or more node profiles. The method can include generating, by the one or more processors, for each node profile of a plurality of node profiles, a match score of the node profile indicating a likelihood that the electronic activity is transmitted or received by an account corresponding to the node profile based on comparing the plurality of activity field-value pairs to respective node field-value pairs of the node profile. The method can include determining, by the one or more processors, a subset of the plurality of node profiles with which to link the electronic activity responsive to determining that the match score of each node profile of the subset satisfies a threshold. The method can include updating, by the one or more processors, a data structure to include an association between the electronic activity and each node profile of the subset of the plurality of node profiles.

In some implementations, the method includes selecting, by the one or more processors, a first node profile of the subset of the plurality of node profiles with which to match the electronic activity based on the match score of the first node profile. The method can include linking, by the one or more processors, the electronic activity with the first node profile. In some implementations, the method includes determining, by the one or more processors, that a first value of a first activity field-value pair matches a first value of a first node field-value pair. The method can include adding, by the one or more processors, to a first value data structure of the first node field-value pair, a first entry identifying the electronic activity. In some implementations, the method includes determining, by the one or more processors, a contribution score of the first entry based on a trust score of a source of the electronic activity, the contribution score used to determine a confidence score of the first value of the first field of the first node profile. In some implementations, the method includes determining the confidence score of the first value of the first field of the first node profile based on the contribution score of the first entry and respective contribution scores of one or more additional entries included in the first value data structure of the first value.

In some implementations, the method includes determining, by the one or more processors, that a second value of a second activity field-value pair matches a second value of a second node field-value pair. The method can include adding, by the one or more profiles, to a second value data structure of the second node field-value pair, a second entry identifying the electronic activity. In some implementations, the method includes determining, by the one or more processors, that a second value of a second activity field-value pair does not match a second value of a second node field-value pair. The method can include generating, by the one or more processors, a second value data structure of the node profile using the second value, the second value data structure including a second entry that identifies the electronic activity. In some implementations, the method includes identifying a first string of the plurality of strings from a portion of the electronic activity. The method can include determining a confidence score that the first string is a first name based on comparing the first string to a plurality of values of the node field-value pairs and the portion of the electronic activity from which the first string was identified. The method can include generating the match score of the electronic activity based on matching characters of the first string to one or more values node field-value pairs.

In some implementations, the method includes each node profile includes a plurality of fields, each field of the plurality of fields including one or more value data structures, each value data structure of the one or more value data structures including a value and one or more entries corresponding to respective one or more data points that support the value of the value data structure. The method can include generating the match score of the electronic activity to the first node profile includes matching the plurality of strings identified from the electronic activity to respective node field-value pairs of the first node profile.

In some implementations, the plurality of fields includes a first name field, a last name field, a phone number field, an email address field and a company name field. In some implementations, the method includes determining the subset of node profiles to correspond to a sender of the electronic activity, the subset being a first subset, the electronic activity being a first electronic activity, identifying a second electronic activity, determining the second electronic activity to be at least one of a reply to or a forward of the first electronic activity, determining a second subset of node profiles that match the second electronic activity, and updating the first subset of node profiles using the second subset of node profiles. In some implementations, the method includes increasing the match score of at least one node profile of the subset of node profiles responsive to determining that the second electronic activity is at least one of a forward or a reply to the first electronic activity. In some implementations, the method includes determining the match score based on determining that the electronic activity is at least one of a forward or a reply.

According to at least one aspect of the disclosure a method can include accessing, by one or more processors, a plurality of electronic activities transmitted or received via electronic accounts associated with a plurality of data source providers, the one or more processors maintaining a plurality of node profiles and configured to update the plurality of node profiles using the plurality of electronic activities. The method can include identifying, by the one or more processors, from data included in an electronic activity of the plurality of electronic activities to link to one or more node profiles, a plurality of strings, each string of the plurality of strings corresponding to a respective field of one or more node profiles maintained by the one or more processors. The method can include identifying, by the one or more processors, a plurality of candidate node profiles to which to link the electronic activity by comparing one or more strings of the plurality of strings to values of fields of respective candidate node profiles. The method can include generating, by the one or more processors, for each candidate node profile, a match score indicating a likelihood that the electronic activity is transmitted or received by an account corresponding to the candidate node profile based on comparing the plurality of strings included in the electronic activity to values of fields included in the candidate node profile. The method can include determining, by the one or more processors, a subset of the plurality of candidate node profiles based on the match score of each candidate node profile of the subset satisfying a threshold. The method can include linking, by the one or more processors, the electronic activity to each candidate node profile of the subset of the plurality of candidate node profiles.

In some implementations, the method includes selecting, by the one or more processors, a first node profile of the subset of the plurality of candidate node profiles with which to match the electronic activity based on the match score of the first node profile. The method can include matching, by the one or more processors, the electronic activity with the first node profile. In some implementations, the method includes determining, by the one or more processors, a first string of the plurality of strings is a first string type that corresponds to a first field of the plurality of node profiles. The method can include determining, by the one or more processors, that the first string matches a first value of the first field of the first node profile. The method can include adding, by the one or more processors, to a first value data structure of the first value of the first field of the first node profile, a first entry identifying the electronic activity. In some implementations, the method includes determining, by the one or more processors, a contribution score of the first entry based on a trust score of a source of the electronic activity, the contribution score used to determine a confidence score of the first value of the first field of the first node profile.

In some implementations, the method includes determining the confidence score of the first value of the first field of the first node profile based on the contribution score of the first entry and respective contribution scores of one or more additional entries included in the first value data structure of the first value. In some implementations, the method includes determining, by the one or more processors, a second string of the plurality of strings is a second string type that corresponds to a second field of the plurality of node profiles. In some implementations, the method includes determining, by the one or more processors, that the second string matches a second value of the second field of the first node profile. The method can include adding, by the one or more profiles, to a second value data structure of the second value of the second field of the first node profile, a second entry identifying the electronic activity. In some implementations, the method includes determining, by the one or more processors, a second string of the plurality of strings is a second string type that corresponds to a second field of the plurality of node profiles. The method can include determining, by the one or more processors, that the second field of the first node profile does not include a value that matches the second string. The method can include generating, by the one or more processors, a second value data structure of the value that matches the second string, the second value data structure including a second entry that identifies the electronic activity.

In some implementations, the method includes identifying a first string of the plurality of strings from a portion of the electronic activity. The method can include determining a confidence score that the first string is a first name based on comparing the first string to a plurality of values of a first name field of the plurality of node profiles and the portion of the electronic activity from which the first string was identified. The method can include generating the match score of the electronic activity to the first node profile includes generating the match score based on matching the first string of characters to one or more values of the first name field of the first of node profile.

In some implementations, each node profile includes a plurality of fields, each field of the plurality of fields including one or more value data structures, each value data structure of the one or more value data structures including a value and one or more entries corresponding to respective one or more data points that support the value of the value data structure. In some implementations, the method includes generating the match score of the electronic activity to the first node profile includes matching the plurality of strings identified from the electronic activity to respective fields of the first node profile. In some implementations, the plurality of fields include a first name field, a last name field, a phone number field, an email address field and a company name field.

According to at least one aspect of the disclosure a method can include accessing, by one or more processors, a plurality of record objects of one or more systems of record, each record object of the plurality of record objects corresponding to a record object type and each comprising one or more object field-value pairs associating an object field value to a corresponding field of the record object, the systems of record corresponding to the one or more data source providers. The method can include maintaining, by the one or more processors, a plurality of node profiles corresponding to a plurality of unique entities, each node profile including one or more node field-value pairs associating a node field value to a corresponding field of the node profile. The method can include identifying, by the one or more processors, a record object to match to at least one node profile of the plurality of node profiles, each record object including a plurality of object field-value pairs associating an object field value to a corresponding field. The method can include comparing, by the one or more processors, the object field values of the one or more object field-value pairs of the record object to the corresponding node field values of the corresponding fields of the node profile. The method can include generating, by the one or more processors based on the comparison, a match score of the node profile indicating a likelihood that the record object corresponds to the node profile. The method can include determining, by the one or more processors, a subset of the plurality of node profiles with which to link the record object responsive to determining that the match score of each node profile of the subset satisfies a threshold. The method can include updating, by the one or more processors, a first value data structure of the first node field value by adding an entry identifying the record object. The method can include updating, by the one or more processors, a confidence score of the first node field value based on the entry identifying the record object.

In some implementations, the record object is a first record object and the subset is a first subset. The method can include matching, by the one or more processors, a second record object to a second subset of the plurality of node profiles. The method can include identifying, by the one or more processors, a link between the first record object and the second record object. The method can include at least one of (i) adding the second subset to the first subset or (ii) increasing a match score of comparisons of the node field-value pairs of node profiles of the second subset to the object field-value pairs of the first record object.

In some implementations, the method includes matching the record object to the first node profile by matching the record object to the first node profile based on a second object field value matching a second node field value of the first node profile, wherein the entry is a first entry, the confidence score is a first confidence score. The method can include updating, by the one or more processors, a second value data structure of the first node field value by adding a second entry identifying the record object. The method can include updating, by the one or more processors, a second confidence score of the second node field value based on the second entry identifying the record object. In some implementations, the method includes generating a contribution score of the entry identifying the record object based on a trust score assigned to the system of record associated with the record object, the contribution score contributing to the confidence score of the first node field value. In some implementations, the method includes generating the trust score of the system of record based on comparing the values of object fields of record objects of the system of record to values of node profiles having a confidence score above a predetermined threshold.

In some implementations, the contribution score is based on a time at which the record object was last updated or modified. In some implementations, matching the record object to the first node profile includes matching the record object to the first node profile based on a matching policy, the matching policy including a first rule having a first weight and a second rule having a second weight. In some implementations, the method includes maintaining, by the one or more processors, a shadow record object corresponding to the record object. The method can include adding, by the one or more processors, to the shadow record object, one or more values to one or more shadow object fields of the shadow record object determined from the first node profile to which the record object is matched. In some implementations, the method includes providing a notification to a device to update a value of the object field of the record object based on the one or more values added to the one or more shadow object fields of the shadow record object. In some implementations, the method includes determining, by the one or more processors, that a second object field value of a second object field of the record object is different from a second node field value of a corresponding field of the first node profile. The method can include determining, by the one or more processors, that the second node field value of the corresponding field has a confidence score above a predetermined threshold. The method can include generating, by the one or more processors, a request to update the second object field value to match the second node field value in the second object field of the record object responsive to determining that the second node field value of the corresponding field has a confidence score above a predetermined threshold.

According to at least one aspect of the disclosure a method can include accessing, by one or more processors, a plurality of record objects of one or more systems of record, each record object of the plurality of record objects corresponding to a record object type and comprising one or more object fields having one or more object field values, the systems of record corresponding to the one or more data source providers. The method can include maintaining, by the one or more processors, a plurality of node profiles corresponding to a plurality of unique entities, each node profile including a plurality of node profile fields, each node profile field of the plurality of node profile fields including one or more value data structures, each value data structure of the one or more value data structures including a node field value and one or more entries corresponding to respective one or more data points that support the node field value of the value data structure. The method can include identifying, by the one or more processors, a record object to match to at least one node profile of the plurality of node profiles. The method can include matching, by the one or more processors, the record object to a first node profile based on a first object field value matching a first node field value of the first node profile. The method can include updating, by the one or more processors, a first value data structure of the first node field value by adding an entry identifying the record object. The method can include updating, by the one or more processors, a confidence score of the first node field value based on the entry identifying the record object.

In some implementations, the record object is a first record object and the subset is a first subset. The method can include matching, by the one or more processors, a second record object to a second subset of the plurality of node profiles. The method can include identifying, by the one or more processors, a link between the first record object and the second record object. The method can include at least one of (i) adding the second subset to the first subset or (ii) increasing a match score of comparisons of the node field-value pairs of node profiles of the second subset to the object field-value pairs of the first record object.

In some implementations, the method includes matching the record object to the first node profile by matching the record object to the first node profile based on a second object field value matching a second node field value of the first node profile, wherein the entry is a first entry, the confidence score is a first confidence score. The method can include updating, by the one or more processors, a second value data structure of the first node field value by adding a second entry identifying the record object. The method can include updating, by the one or more processors, a second confidence score of the second node field value based on the second entry identifying the record object.

In some implementations, the method includes generating a contribution score of the entry identifying the record object based on a trust score assigned to the system of record associated with the record object, the contribution score contributing to the confidence score of the first node field value. In some implementations, the method includes generating the trust score of the system of record based on comparing the values of object fields of record objects of the system of record to values of node profiles having a confidence score above a predetermined threshold. In some implementations, the contribution score is based on a time at which the record object was last updated or modified. In some implementations, matching the record object to the first node profile includes matching the record object to the first node profile based on a matching policy, the matching policy including a first rule having a first weight and a second rule having a second weight. In some implementations, the method includes maintaining, by the one or more processors, a shadow record object corresponding to the record object. The method can include adding, by the one or more processors, to the shadow record object, one or more values to one or more shadow object fields of the shadow record object determined from the first node profile to which the record object is matched. In some implementations, the method includes providing a notification to a device to update a value of the object field of the record object based on the one or more values added to the one or more shadow object fields of the shadow record object.

In some implementations, the method includes determining, by the one or more processors, that a second object field value of a second object field of the record object is different from a second node field value of a corresponding field of the first node profile. The method can include determining, by the one or more processors, that the second node field value of the corresponding field has a confidence score above a predetermined threshold. The method can include generating, by the one or more processors, a request to update the second object field value to match the second node field value in the second object field of the record object responsive to determining that the second node field value of the corresponding field has a confidence score above a predetermined threshold. In some implementations, the method includes determining, by the one or more processors, the match score as a weighted average based on a uniqueness score of each object field value.

According to at least one aspect of the disclosure a method can include accessing, by one or more processors, at least one of i) a plurality of electronic activities transmitted or received via electronic accounts associated with one or more data source providers or ii) a plurality of record objects of one or more systems of record associated with the one or more data source providers, the one or more processors maintaining a plurality of node profiles and configured to update the plurality of node profiles using at least one of the plurality of electronic activities or the plurality of record objects. The method can include identifying, by the one or more processors, a node profile of the plurality of node profiles including a plurality of fields, each field of the plurality of fields including one or more value data structures, each value data structure of the one or more value data structures corresponding to a value and further including one or more entries, each entry of the one or more entries corresponding to respective one or more data points that include a string that matches the value of the value data structure, each data point of the one or more data points identifying a respective electronic activity of the plurality of electronic activities or a respective record object of the plurality of record objects. The method can include determining, for at least one data point of the one or more data points included in a respective value data structure of a value of a field of the plurality of fields of the node profile, a contribution score of the data point based on a time corresponding to when the data point was generated or updated. The method can include generating, by the one or more processors, a confidence score of the value of the field of the node profile based on the contribution score of the at least one data point.

In some implementations, the data point identifies an electronic activity of the plurality of electronic activities or a record object of a system of record accessible by the one or more processors. Determining the contribution score of the data point can include determining, for at least one data point of the one or more data points that includes the value of the field of the node profile, the contribution score of the at least one data point comprises determining, for each data point of the one or more data points that support the value of the field of the node profile, a respective contribution score of the data point based on a respective time corresponding to when the data point was generated or updated. Generating a confidence score of the value can include generating, by the one or more processors, the confidence score of the value of the field of the node profile based on the contribution score of the at least one data point includes generating, by the one or more processors, the confidence score of the value of the field of the node profile based on the respective contribution score of each of the one or more data points that support the value of the field of the node profile.

Determining the contribution score of the data point can include determining, for the at least one data point of the one or more data points, the contribution score of the data point includes determining, for the at least one data point, a contribution score of the data point based on a trust score assigned to a source of the data point, the trust score determined based on a type of source of the data point. The data point can be a record object. The trust score assigned to the data point can be based on a health of the system of record from which the record object was accessed. The health of the system of record from which the record object was accessed can be determined based on comparing field values of object fields included in record objects of the system of record to node profile field values of fields of one or more node profiles having respective confidence scores above a predetermined threshold.

In some implementations, the method can include receiving, by the one or more processors, a second electronic activity. The method can include determining, by the one or more processors, that the second electronic activity includes the value of the field of the node profile. The method can include generating, by the one or more processors, a second contribution score of the second electronic activity for the value of the field of the node profile. The method can include updating, by the one or more processors, the confidence score of the value based on the contribution score of the second electronic activity. In some implementations, the method can include identifying, by the one or more processors, a record object of a system of record previously not matched to the value of the field of the node profile. The method can include determining, by the one or more processors, that the record object includes the value of the field of the node profile. The method can include generating, by the one or more processors, a contribution score of the record object. The method can include updating, by the one or more processors, the confidence score of the value of the field of the node profile based on the contribution score of the record object.

In some implementations, the data point identifies an electronic activity is an automatically generated bounce back electronic activity. In some implementations, the method includes maintaining, for the value of the field of the node profile, an occurrence metric indicating a number of data points used to support the value. In some implementations, the node profile includes a first field having a first value data structure identifying a first value and the first value is assigned to the first field by linking a first electronic activity to the node profile.

In some implementations, the first value data structure includes a first entry identifying the first electronic activity and the first electronic activity is linked to the first node profile by identifying, by the one or more processors, from data included in the first electronic activity, a plurality of strings. The method can include identifying, by the one or more processors, a plurality of candidate node profiles to which to link the electronic activity by comparing one or more strings of the plurality of strings to values of fields of respective candidate node profiles. The method can include generating, by the one or more processors, for each candidate node profile, a match score indicating a likelihood that the electronic activity is transmitted or received by an account corresponding to the candidate node profile based on comparing the plurality of strings included in the electronic activity to values of fields included in the candidate node profile. The method can include linking, by the one or more processors, the first electronic activity to the first node profile based on the match score of the first node profile.

In some implementations, the value of the field of the node profile includes a first value of a first field of the node profile and the contribution score of the data point is a first contribution score of a first data point and the confidence score is a first confidence score of a first value. The method can include identifying a second value data structure of a second field of the node profile, the second value data structure corresponding to a second value of the second field and further including one or more second entries corresponding to respective one or more second data points that support the second value of the second value data structure. The method can include determining, for at least one second data point of the one or more second data points of the second value of the second field of the node profile, a second contribution score of the second data point based on a time corresponding to when the second data point was generated or updated. The method can include generating, by the one or more processors, a second confidence score of the second value of the second field of the node profile based on the second contribution score of the at least one second data point.

In some implementations, the field of the plurality of fields of the node profile comprises a second value and a corresponding second value data structure including at least one second entry identifying a second electronic activity or at least one second record object that includes a second string that matches the second value. In some implementations, the field of the plurality of fields is a first field and a second field of the plurality of fields of the node profile comprises a second value and a corresponding second value data structure including at least one second entry identifying the first electronic activity or the first record object that also includes a second string that matches the second value.

The method can include receiving, by the one or more processors, a subsequent electronic activity. The method can include linking, by the one or more processors, the electronic activity to the node profile by including one or more entries identifying the electronic activity to one or more value data structures corresponding to one or more values of one or more fields. The method can include generating, by the one or more processors, for each entry identifying the electronic activity, a contribution score of the electronic activity, the entry corresponding to a respective value data structure of a respective value of a respective field. The method can include generating, by the one or more processors, respective confidence scores for the values based on the respective contribution scores of the electronic activity. In some implementations, the electronic activity includes a signature block in the electronic activity, and linking the electronic activity to the node profile comprises extracting, by the one or more processors, from the signature block of the electronic activity, a plurality of strings. The method can include determining, by the one or more processors, using the plurality of strings extracted from the signature block, that the node profile of the plurality of node profiles includes one or more values that match respective strings of the plurality of strings.

Another aspect of the disclosure describes a system including one or more processors configured to access at least one of i) a plurality of electronic activities transmitted or received via electronic accounts associated with one or more data source providers or ii) a plurality of record objects of one or more systems of record associated with the one or more data source providers. The one or more processors can maintain a plurality of node profiles and be configured to update the plurality of node profiles using at least one of the plurality of electronic activities or the plurality of record objects. The one or more processors can identify a node profile of the plurality of node profiles including a plurality of fields. Each field of the plurality of fields includes one or more value data structures, each value data structure of the one or more value data structures corresponding to a value and further including one or more entries, each entry of the one or more entries corresponding to respective one or more data points that include a string that matches the value of the value data structure. Each data point of the one or more data points identifies a respective electronic activity of the plurality of electronic activities or a respective record object of the plurality of record objects. The system determines, for at least one data point of the one or more data points included in a respective value data structure of a value of a field of the plurality of fields of the node profile, a contribution score of the data point based on a time corresponding to when the data point was generated or updated. The system can generate a confidence score of the value of the field of the node profile based on the contribution score of the at least one data point.

In some implementations, the data point identifies an electronic activity of the plurality of electronic activities or a record object of a system of record accessible by the one or more processors. Determining the contribution score of the data point can include determining, for at least one data point of the one or more data points that includes the value of the field of the node profile, the contribution score of the at least one data point comprises determining, for each data point of the one or more data points that support the value of the field of the node profile, a respective contribution score of the data point based on a respective time corresponding to when the data point was generated or updated. Generating a confidence score of the value can include generating, by the one or more processors, the confidence score of the value of the field of the node profile based on the contribution score of the at least one data point includes generating, by the one or more processors, the confidence score of the value of the field of the node profile based on the respective contribution score of each of the one or more data points that support the value of the field of the node profile.

Determining the contribution score of the data point can include determining, for the at least one data point of the one or more data points, the contribution score of the data point includes determining, for the at least one data point, a contribution score of the data point based on a trust score assigned to a source of the data point, the trust score determined based on a type of source of the data point. The data point can be a record object. The trust score assigned to the data point can be based on a health of the system of record from which the record object was accessed. The health of the system of record from which the record object was accessed can be determined based on comparing field values of object fields included in record objects of the system of record to node profile field values of fields of one or more node profiles having respective confidence scores above a predetermined threshold.

In some implementations, the system can receive a second electronic activity. The system can determine that the second electronic activity includes the value of the field of the node profile. The system can generate a second contribution score of the second electronic activity for the value of the field of the node profile. The system can update the confidence score of the value based on the contribution score of the second electronic activity. In some implementations, the system can identify a record object of a system of record previously not matched to the value of the field of the node profile. The system can determine that the record object includes the value of the field of the node profile. The method can include generating, by the one or more processors, a contribution score of the record object. The method can include updating, by the one or more processors, the confidence score of the value of the field of the node profile based on the contribution score of the record object.

In some implementations, the data point identifies an electronic activity is an automatically generated bounce back electronic activity. In some implementations, the system can maintain, for the value of the field of the node profile, an occurrence metric indicating a number of data points used to support the value. In some implementations, the node profile includes a first field having a first value data structure identifying a first value and the first value is assigned to the first field by linking a first electronic activity to the node profile.

In some implementations, the first value data structure includes a first entry identifying the first electronic activity and the first electronic activity is linked to the first node profile by identifying, by the one or more processors, from data included in the first electronic activity, a plurality of strings. The method can include identifying, by the one or more processors, a plurality of candidate node profiles to which to link the electronic activity by comparing one or more strings of the plurality of strings to values of fields of respective candidate node profiles. The method can include generating, by the one or more processors, for each candidate node profile, a match score indicating a likelihood that the electronic activity is transmitted or received by an account corresponding to the candidate node profile based on comparing the plurality of strings included in the electronic activity to values of fields included in the candidate node profile. The method can include linking, by the one or more processors, the first electronic activity to the first node profile based on the match score of the first node profile.

In some implementations, the value of the field of the node profile includes a first value of a first field of the node profile and the contribution score of the data point is a first contribution score of a first data point and the confidence score is a first confidence score of a first value. The system can identify a second value data structure of a second field of the node profile, the second value data structure corresponding to a second value of the second field and further including one or more second entries corresponding to respective one or more second data points that support the second value of the second value data structure. The system can determine, for at least one second data point of the one or more second data points of the second value of the second field of the node profile, a second contribution score of the second data point based on a time corresponding to when the second data point was generated or updated. The system can generate a second confidence score of the second value of the second field of the node profile based on the second contribution score of the at least one second data point.

In some implementations, the field of the plurality of fields of the node profile comprises a second value and a corresponding second value data structure including at least one second entry identifying a second electronic activity or at least one second record object that includes a second string that matches the second value. In some implementations, the field of the plurality of fields is a first field and a second field of the plurality of fields of the node profile comprises a second value and a corresponding second value data structure including at least one second entry identifying the first electronic activity or the first record object that also includes a second string that matches the second value.

The system can be configured to a subsequent electronic activity. The system can be configured to link the electronic activity to the node profile by including one or more entries identifying the electronic activity to one or more value data structures corresponding to one or more values of one or more fields. The system can generate, for each entry identifying the electronic activity, a contribution score of the electronic activity, the entry corresponding to a respective value data structure of a respective value of a respective field. The system can generate respective confidence scores for the values based on the respective contribution scores of the electronic activity. In some implementations, the electronic activity includes a signature block in the electronic activity, and linking the electronic activity to the node profile comprises extracting, by the one or more processors, from the signature block of the electronic activity, a plurality of strings. The system can determine, using the plurality of strings extracted from the signature block, that the node profile of the plurality of node profiles includes one or more values that match respective strings of the plurality of strings.

One aspect of the present disclosure relates to a method for measuring goals based on matching electronic activities to record objects. The method may include accessing a plurality of electronic activities transmitted or received via electronic accounts of one or more data source providers, and accessing a plurality of record objects of one or more systems of record, each record object of the plurality of record objects including one or more object fields having one or more object field values, the systems of record corresponding to the one or more data source providers. The method may further include identifying, for a first entity identified by at least one field-value pair of a first set of record objects of the plurality of record objects, an event generated based on data included in the first set of record objects, the event configured to change from a first status to a second status based on an event policy specifying i) a qualifying entity type or ii) a number of electronic activities that satisfy one or more conditions of the event policy. The method may further include identifying, from the plurality of electronic activities, a set of electronic activities to be linked to a record object of the first set of record objects; and determining, for each electronic activity of the set of electronic activities, a plurality of activity field-value pairs identifying participants of the electronic activity. The method may further include determining, using the set of electronic activities, by applying the event policy, that the event is to be changed from the first status to the second status responsive to determining that: i) at least one electronic activity of the set is used to generate an activity field-value pair that identifies an entity of the qualifying entity type specified in the event policy, based on an identified participant of the at least one electronic activity, or ii) the set of electronic activities includes the number of electronic activities of the set of electronic activities that satisfy the one or more conditions. The method may further include updating the status of the event from the first status to the second status responsive to applying the event policy.

In some implementations of the method, the one or more conditions of the event policy include being a specified type of electronic activity, and the method may include determining that an electronic activity of the set of electronic activities satisfies the one or more conditions by: determining, for the electronic activity, a type of the electronic activity; and matching the type of the electronic activity to the specified type of electronic activity.

In some implementations of the method, it may include determining that the at least one electronic activity of the set is used to generate the activity field-value pair that identifies the entity by: parsing the at least one electronic activity to identify a participant of the at least one electronic activity; and determining that the identified participant is an entity of the qualifying entity type.

In some implementations of the method, it may include determining that the identified participant is the entity of the qualifying entity type by: matching the identified participant to a node profile; identifying a field-value pair of the node profile specified by the event policy as having a field corresponding to the qualifying entity type; and matching a value of the field-value pair to a qualifying value specified by the event policy.

In some implementations of the method, the field of the field-value pair of the node profile of the participant is one of a plurality of predetermined fields.

In some implementations of the method, it includes parsing the at least one electronic activity to identify a participant of the at least one electronic activity by: determining a value of a header field for the at least one electronic activity, the header field corresponding to at least one of a contact identifier or a name.

In some implementations of the method, it includes determining that the set of electronic activities includes the number of electronic activities of the set of electronic activities that satisfy the one or more conditions by: for one or more electronic activities of the set of electronic activities, determining whether the electronic activity satisfies the one or more conditions by applying the event policy, and if the electronic activity satisfies the one or more conditions, incrementing a counter; and comparing the counter to a reference threshold that is based on the number specified by the event policy; and updating the status of the event responsive to applying the event policy includes updating the status of the event responsive to determining that the counter meets or exceeds the reference threshold.

In some implementations of the method, the one or more conditions include the electronic activity being time-stamped within a predetermined period of time specified by the event policy.

In some implementations of the method, the one or more conditions include the electronic activity being classified by a classifier trained via a machine learning process as falling within a class specified by the event policy.

In some implementations of the method, it includes storing, in one or more data structures, an association between the event, the event status and an identifier of the node profile of the entity.

Another aspect of the present disclosure relates to a system configured for measuring goals based on matching electronic activities to record objects. The system may include one or more hardware processors configured by machine-readable instructions to measure goals based on matching electronic activities to record objects. The processor(s) may be configured to access a plurality of electronic activities transmitted or received via electronic accounts of one or more data source providers, and access a plurality of record objects of one or more systems of record, each record object of the plurality of record objects including one or more object fields having one or more object field values, the systems of record corresponding to the one or more data source providers. The processor(s) may be configured to identify, for a first entity identified by at least one field-value pair of a first set of record objects of the plurality of record objects, an event generated based on data included in the first set of record objects, the event configured to change from a first status to a second status based on an event policy specifying i) a qualifying entity type or ii) a number of electronic activities that satisfy one or more conditions of the event policy. The processor(s) may be configured to identify, from the plurality of electronic activities, a set of electronic activities to be linked to a record object of the first set of record objects; and determine, for each electronic activity of the set of electronic activities, a plurality of activity field-value pairs identifying participants of the electronic activity. The processor(s) may be configured to determine, using the set of electronic activities, by applying the event policy, that the event is to be changed from the first status to the second status responsive to determining that: i) at least one electronic activity of the set is used to generate an activity field-value pair that identifies an entity of the qualifying entity type specified in the event policy, based on an identified participant of the at least one electronic activity, or ii) the set of electronic activities includes the number of electronic activities of the set of electronic activities that satisfy the one or more conditions. The processor(s) may be configured to update the status of the event from the first status to the second status responsive to applying the event policy.

Yet another aspect of the present disclosure relates to a non-transitory computer-readable storage medium having instructions embodied thereon, the instructions being executable by one or more processors to perform a method for measuring goals based on matching electronic activities to record objects. The method may include accessing a plurality of electronic activities transmitted or received via electronic accounts of one or more data source providers, and accessing a plurality of record objects of one or more systems of record, each record object of the plurality of record objects including one or more object fields having one or more object field values, the systems of record corresponding to the one or more data source providers. The method may further include identifying, for a first entity identified by at least one field-value pair of a first set of record objects of the plurality of record objects, an event generated based on data included in the first set of record objects, the event configured to change from a first status to a second status based on an event policy specifying i) a qualifying entity type or ii) a number of electronic activities that satisfy one or more conditions of the event policy. The method may further include identifying, from the plurality of electronic activities, a set of electronic activities to be linked to a record object of the first set of record objects; and determining, for each electronic activity of the set of electronic activities, a plurality of activity field-value pairs identifying participants of the electronic activity. The method may further include determining, using the set of electronic activities, by applying the event policy, that the event is to be changed from the first status to the second status responsive to determining that: i) at least one electronic activity of the set is used to generate an activity field-value pair that identifies an entity of the qualifying entity type specified in the event policy, based on an identified participant of the at least one electronic activity, or ii) the set of electronic activities includes the number of electronic activities of the set of electronic activities that satisfy the one or more conditions. The method may further include updating the status of the event from the first status to the second status responsive to applying the event policy.

In some implementations of the computer-readable storage medium, the one or more conditions of the event policy include being a specified type of electronic activity, and the method includes determining that an electronic activity of the set of electronic activities satisfies the one or more conditions by: determining, for the electronic activity, a type of the electronic activity; and matching the type of the electronic activity to the specified type of electronic activity.

In some implementations of the computer-readable storage medium, the method includes determining that the at least one electronic activity of the set is used to generate the activity field-value pair that identifies the entity by: parsing the at least one electronic activity to identify a participant of the at least one electronic activity; and determining that the identified participant is an entity of the qualifying entity type.

In some implementations of the computer-readable storage medium, the method includes determining that the identified participant is the entity of the qualifying entity type by: matching the identified participant to a node profile; identifying a field-value pair of the node profile specified by the event policy as having a field corresponding to the qualifying entity type; and matching a value of the field-value pair to a qualifying value specified by the event policy.

In some implementations of the computer-readable storage medium, the field of the field-value pair of the node profile of the participant is one of a plurality of predetermined fields.

In some implementations of the computer-readable storage medium, the method includes parsing the at least one electronic activity to identify a participant of the at least one electronic activity by: determining a value of a header field for the at least one electronic activity, the header field corresponding to at least one of a contact identifier or a name.

In some of the computer-readable storage medium, the method includes determining that the set of electronic activities includes the number of electronic activities of the set of electronic activities that satisfy the one or more conditions by: for one or more electronic activities of the set of electronic activities, determining whether the electronic activity satisfies the one or more conditions by applying the event policy, and if the electronic activity satisfies the one or more conditions, incrementing a counter; and comparing the counter to a reference threshold that is based on the number specified by the event policy; and updating the status of the event responsive to applying the event policy includes updating the status of the event responsive to determining that the counter meets or exceeds the reference threshold.

In some implementations of the computer-readable storage medium, the one or more conditions include the electronic activity being time-stamped within a predetermined period of time specified by the event policy.

In some implementations of the computer-readable storage medium, the one or more conditions include the electronic activity being classified by a classifier trained via a machine learning process as falling within a class specified by the event policy.

In some implementations of the computer-readable storage medium, the method includes storing, in one or more data structures, an association between the event, the event status and an identifier of the node profile of the entity.

The present disclosure relates to systems and methods for managing electronic activity related targets. Management of the systems of record described above can include maintaining a node profile that includes data structures relates to generating, assigning, managing, tracking, and measuring an electronic activity driven target and progress of the electronic activity driven target. It can be challenging to assign electronic activity driven targets to node profiles, which may involve parsing a plurality of electronic activities to generate a plurality of electronic activity driven targets, and identifying which electronic activity driven targets, of the plurality of electronic activity driven targets, pertain to and should be assigned to the specific node profiles. Disclosed herein are systems and method for improved management, measurement, and tracking of electronic activity driven targets. The systems and methods disclosed herein can assign sets of electronic activity driven targets to specific node profiles by matching the specific node profiles to other node profiles used to generate the sets of electronic activity driven targets.

One aspect of the present disclosure relates to a method for managing electronic activity driven targets. The method may include maintaining a plurality of node profiles respectively corresponding to a plurality of unique entities, each node profile including a plurality of field-value pairs; accessing a first plurality of electronic activities transmitted or received via electronic accounts associated with one or more data source providers and updating the plurality of node profiles using the first plurality of electronic activities; selecting for a first node profile of the plurality of node profiles, using one or more field-value pairs of the first node profile, an endpoint profile generated using electronic activities of second node profiles including one or more field-value pairs that match the one or more field-value pairs of the first node profile, the endpoint profile specifying electronic activity driven targets that can be tracked by parsing electronic activities corresponding to the first node profile; storing, in one or more data structures, an association between the first node profile and the endpoint profile specifying the electronic activity driven targets; parsing a second plurality of electronic activities corresponding to the first node profile; and updating a metric relating to the electronic activity driven targets responsive to parsing the second plurality of electronic activities.

In some implementations of the method, it further comprises generating the endpoint profile, wherein generating the endpoint profile comprises: selecting the plurality of second node profiles based on matching a first set of field-value pairs of the second node profiles to the one or more field-value pairs of the first node profile; determining, for each second node profile of the selected second node profiles, a respective electronic activity pattern based on a third plurality of electronic activities transmitted or received via electronic accounts of the second node profile; and setting, by the one or more processors, one or more target values for the endpoint profile based on each respective electronic activity pattern.

In some implementations of the method, generating the respective electronic activity pattern for the second node profile comprises: parsing each electronic activity of the third plurality of electronic activities; generating, for the electronic activity, one or more activity field-value pairs corresponding to respective node field-value pairs of node profiles of participants of the electronic activity; and using the one or more activity field-value pairs to generate the respective electronic activity pattern.

In some implementations of the method, using the one or more activity-field value pairs to generate the respective electronic activity pattern comprises using a volume of electronic activities that identify participants corresponding to node profiles including node field value pairs that specify a predetermined value of a predetermined field.

In some implementations of the method, updating the metric comprises generating an updated metric, and the method further comprises determining that the updated metric is below a threshold value; and transmitting, responsive to determining that the updated metric is below the threshold value, a notification to a contact identifier specified by the first node profile, the notification referencing at least one of the electronic activity driven targets.

In some implementations of the method, updating the metric comprises generating an updated metric, and the method further comprises determining that the updated metric is below a threshold value; and transmitting, responsive to determining that the updated metric is below the threshold value, a notification to a contact identifier corresponding to a third node profile having one or more field-value pairs that match corresponding field-value pairs of the first node profile, the notification referencing the at least one of the electronic activity driven targets.

In some implementations of the method, the metric is a count of a number of record objects associated with the first node profile and having a stage status indicating that a last stage of an ordered set of stages has been completed, and one of the electronic activity driven targets requires meeting at least a threshold value for the metric.

In some implementations of the method, each second node profile of the second node profiles is associated with at least a threshold number of record objects having a stage status indicating that a specified stage of an ordered set of stages has been completed.

In some implementations of the method, the electronic activities corresponding to one of the second node profiles used to generate the endpoint profile correspond to a predetermined time period from a trigger time of the second node profile, and a current time is within the predetermined time period of a trigger time of the first node profile.

Another aspect of the present disclosure relates to a system configured for managing electronic activity driven targets. The system may include one or more hardware processors configured by machine-readable instructions to manage the electronic activity driven targets. The processor(s) may be configured to maintain a plurality of node profiles respectively corresponding to a plurality of unique entities, each node profile including a plurality of field-value pairs; access a first plurality of electronic activities transmitted or received via electronic accounts associated with one or more data source providers, the one or more processors configured to update the plurality of node profiles using the first plurality of electronic activities; select, for a first node profile of the plurality of node profiles, using one or more field-value pairs of the first node profile, an endpoint profile generated using electronic activities of second node profiles including one or more field-value pairs that match the one or more field-value pairs of the first node profile, the endpoint profile specifying electronic activity driven targets that can be tracked by parsing electronic activities corresponding to the first node profile; store in one or more data structures, an association between the first node profile and the endpoint profile specifying the electronic activity driven targets; parse a second plurality of electronic activities corresponding to the first node profile; and update a metric relating to the electronic activity driven targets responsive to parsing the second plurality of electronic activities.

In some implementations of the system, the one or more hardware processors are further configured by machine-readable instructions to generate the endpoint profile, and generating the endpoint profile comprises: selecting the plurality of second node profiles based on matching a first set of field-value pairs of the second node profiles to the one or more field-value pairs of the first node profile; determining for each second node profile of the selected second node profiles, a respective electronic activity pattern based on a third plurality of electronic activities transmitted or received via electronic accounts of the second node profile; and setting one or more target values for the endpoint profile based on each respective electronic activity pattern.

In some implementations of the system, generating the respective electronic activity pattern for the second node profile comprises: parsing each electronic activity of the third plurality of electronic activities; generating for the electronic activity, one or more activity field-value pairs corresponding to respective node field-value pairs of node profiles of participants of the electronic activity; and using the one or more activity field-value pairs to generate the respective electronic activity pattern.

In some implementations of the system, using the one or more activity-field value pairs to generate the respective electronic activity pattern comprises using a volume of electronic activities that identify participants corresponding to node profiles including node field value pairs that specify a predetermined value of a predetermined field.

In some implementations of the system, updating the metric comprises generating an updated metric, and the one or more hardware processors are further configured by machine-readable instructions to: determine that the updated metric is below a threshold value; and transmit, responsive to determining that the updated metric is below the threshold value, a notification to a contact identifier specified by the first node profile, the notification referencing at least one of the electronic activity driven targets.

In some implementations of the system, updating the metric comprises generating an updated metric and the one or more hardware processors are further configured by machine-readable instructions to: determine that the updated metric is below a threshold value; and transmit, responsive to determining that the updated metric is below the threshold value, a notification to a contact identifier corresponding to a third node profile having one or more field-value pairs that match corresponding field-value pairs of the first node profile, the notification referencing the at least one of the electronic activity driven targets.

In some implementations of the system, the metric is a count of a number of record objects associated with the first node profile and having a stage status indicating that a last stage of an ordered set of stages has been completed, and one of the electronic activity driven targets requires meeting at least a threshold value for the metric.

In some implementations of the system, each second node profile of the second node profiles is associated with at least a threshold number of record objects having a stage status indicating that a specified stage of an ordered set of stages has been completed.

In some implementations of the system, the electronic activities corresponding to one of the second node profiles used to generate the endpoint profile correspond to a predetermined time period from a trigger time of the second node profile, and a current time is within the predetermined time period of a trigger time of the first node profile.

Yet another aspect of the present disclosure relates to a non-transitory computer-readable storage medium having instructions embodied thereon, the instructions being executable by one or more processors to perform a method for managing electronic activity driven targets. The method may include maintaining a plurality of node profiles respectively corresponding to a plurality of unique entities, each node profile including a plurality of field-value pairs; accessing a first plurality of electronic activities transmitted or received via electronic accounts associated with one or more data source providers and updating the plurality of node profiles using the first plurality of electronic activities; selecting for a first node profile of the plurality of node profiles, using one or more field-value pairs of the first node profile, an endpoint profile generated using electronic activities of second node profiles including one or more field-value pairs that match the one or more field-value pairs of the first node profile, the endpoint profile specifying electronic activity driven targets that can be tracked by parsing electronic activities corresponding to the first node profile; storing, in one or more data structures, an association between the first node profile and the endpoint profile specifying the electronic activity driven targets; parsing a second plurality of electronic activities corresponding to the first node profile; and updating a metric relating to the electronic activity driven targets responsive to parsing the second plurality of electronic activities.

In some implementations of the computer-readable storage medium, the method further comprises generating the endpoint profile, and generating the endpoint profile comprises: selecting the plurality of second node profiles based on matching a first set of field-value pairs of the second node profiles to the one or more field-value pairs of the first node profile; determining, for each second node profile of the selected second node profiles, a respective electronic activity pattern based on a third plurality of electronic activities transmitted or received via electronic accounts of the second node profile; and setting one or more target values for the endpoint profile based on each respective electronic activity pattern.

One aspect of the present disclosure relates to a method. The method includes maintaining, by one or more processors, a plurality of member node profiles. Each member node profile of the plurality of member node profiles may include one or more field-value pairs. Each member node profile may be linked to electronic activities transmitted or received via electronic accounts of the plurality of member node profiles. The method includes maintaining, by the one or more processors, a plurality of group node profiles. Each member node profile may be linked to a corresponding group node profile. The method includes identifying, by the one or more processors, for a first member node profile corresponding to a first group node profile, a first plurality of electronic activities linked to the first member node profile. The method includes determining, by the one or more processors, a first performance profile corresponding to the member node profile based on the first plurality of electronic activities linked to the first member node profile and one or more predetermined field-value pairs of the first member node profile. The method includes identifying, by the one or more processors, a plurality of second performance profiles using node field-value pairs of member node profiles linked to the respective second performance profiles. The method includes generating, by the one or more processors, a performance score of the first performance profile based on a comparison of the first performance profile to the plurality of second performance profiles. The method includes storing, by the one or more processors, in one or more data structures, an association between the first member node profile and the performance score of the first performance profile.

Another aspect of the present disclosure relates to a system. The system includes one or more hardware processors configured by machine-readable instructions to maintain a plurality of member node profiles. Each member node profile of the plurality of member node profiles includes one or more field-value pairs. The processors are further configured to maintain a plurality of group node profiles. Each member node profile may be linked to a corresponding group node profile. The processors are further configured to identify, for a first member node profile corresponding to a first group node profile, a first plurality of electronic activities linked to the first member node profile. The processors are further configured to determine a first performance profile corresponding to the member node profile based on the first plurality of electronic activities linked to the first member node profile and one or more predetermined field-value pairs of the first member node profile. The processors are further configured to identify a plurality of second performance profiles using node field-value pairs of member node profiles linked to the respective second performance profiles. The processors are further configured to generate a performance score of the first performance profile based on a comparison of the first performance profile to the plurality of second performance profiles. The processors are further configured to store, in one or more data structures, an association between the first member node profile and the performance score of the first performance profile.

Yet another aspect of the present disclosure relates to a non-transitory computer-readable storage medium having instructions embodied thereon, the instructions being executable by one or more processors to perform a method. The method includes maintaining, by one or more processors, a plurality of member node profiles. Each member node profile of the plurality of member node profiles may include one or more field-value pairs. The method includes maintaining, by the one or more processors, a plurality of group node profiles. Each member node profile may be linked to a corresponding group node profile. The method includes identifying, by the one or more processors, for a first member node profile corresponding to a first group node profile, a first plurality of electronic activities linked to the first member node profile. The method includes determining, by the one or more processors, a first performance profile corresponding to the first member node profile based on the first plurality of electronic activities linked to the first member node profile and one or more predetermined field-value pairs of the first member node profile. The method includes identifying a plurality of second performance profiles using node field-value pairs of member node profiles linked to the respective second performance profiles. The method includes generating a performance score of the first performance profile based on a comparison of the first performance profile to the plurality of second performance profiles. The method includes storing, in one or more data structures, an association between the first member node profile and the performance score of the first performance profile.

According to at least one aspect of the disclosure, a method for generating performance profiles of member nodes may include accessing, by one or more processors, a plurality of electronic activities transmitted or received via electronic accounts associated with a plurality of data source providers, the plurality of electronic activities used to maintain a plurality of node profiles, each node profile of the plurality node profile including one or more field-value pairs including respective values generated from at least one of the plurality of electronic activities. The method may include identifying, by the one or more processors, for a first node profile of the plurality of node profiles, a subset of electronic activities from the plurality of electronic activities identifying an entity corresponding to the first node profile as a sender or a recipient and parsing, by the one or more processors, each electronic activity of the subset of electronic activities to identify one or more participants with which the entity corresponding to the first node profile is communicating. The method may include accessing, by the one or more processors, for each participant of the one or more participants, a second node profile corresponding to the participant from the plurality of node profiles. The method may include identifying, by the one or more processors, from each second node profile corresponding to a respective participant of the one or more participants, from a plurality of participant types, a participant type for the participant based on the one or more field-value pairs of the second node profile. The method may include determining, by the one or more processors, a distribution of the subset of electronic activities across the plurality of participant types for the one or more participants; and generating, by the one or more processors, a performance profile for the first node profile based on the distribution of the subset of electronic activities across the plurality of participant types for the one or more participants.

In some embodiments, the method may include identifying, by the one or more processors, for each electronic activity of the subset of electronic activities for the first node profile, an electronic activity type of the electronic activity. Generating the performance profile further comprises generating the performance profile for the first node profile based on the electronic activity types identified for the subset of electronic activities.

The method may include determining, by the one or more processors, a second distribution of the subset of electronic activities across the electronic activity types. Generating the performance profile may further include generating the performance profile based on the second distribution.

In some embodiments, accessing the second node profile may further comprise accessing the second node profile including one or more field-value pairs generated from a signature embedded in at least one of the plurality of electronic activities.

In some embodiments, parsing each electronic activity may further comprise parsing each electronic activity of the subset of electronic activities to identify one or more keywords embedded in the electronic activity. Generating the performance profile further comprises generating the performance profile for the first node profile based on the one or more keywords identified from the subset of electronic activities.

In some embodiments, the method may include determining, by the one or more processors, for each electronic activity of the subset of electronic activities for the first node profile, a metric corresponding to the electronic activity. Generating the performance profile may further comprise generating the performance profile for the first node profile based on the metrics corresponding to the electronic activities of the subset of electronic activities.

In some embodiments, identifying the subset of electronic activities may further comprise identifying the subset of electronic activities from the plurality of electronic activities based on one or more tags assigned to the plurality of electronic activities.

In some embodiments, the method may include accessing, by the one or more processors, the plurality of record objects of a system of record corresponding to the plurality of data source providers, each record object of the plurality of record objects having one or more object field-value pairs; and identifying, by the one or more processors, at least one record object corresponding to the first node profile of the plurality of node profiles. Generating the performance profile further comprises generating the performance profile for the first node profile based on the one or more object field-value pairs of the at least one record object identified as corresponding to the first node profile.

In some embodiments, the method may include generating, by the one or more processors, a performance score for the first node profile based on the performance profile of the first node profile.

In some embodiments, the performance profile for the first node profile is a first performance profile. The method may include identifying, by the one or more processors, respective second performance profiles of respective third node profiles that satisfy a similarity threshold based on one or more node field-value pairs of the first node profile and the respective third node profiles and comparing, by the one or more processors, the first performance profile for the first node profile and the respective second performance profiles of the third node profiles. Generating the performance score for the first node profile may further comprise generating the first performance profile for the first node profile responsive to comparing the first performance profile and the respective second performance profiles.

In some embodiments, generating the performance profile may further comprise generating the performance profile for the first node profile based on one or more of an average response time to respond to electronic activities or average response rate.

In some embodiments, the method may include identifying, by the one or more processors, for each record object identifying the entity, a plurality of stages; determining, by the one or more processors, for each stage of the plurality of stages, a subset of electronic activities corresponding to the stage; determining, by the one or more processors, the participants of the electronic activities in the subset in each stage; and generating, by the or more processors, for each stage of the plurality of stages in the record object, a distribution of electronic activities across participant types. Generating the performance profile may further include generating the performance profile based on the plurality of distributions of electronic activities across participant types at each stage of the plurality of stages

In some embodiments, the method may include accessing, by the one or more processors, subsequent to generating the performance profile, a second plurality of electronic activities transmitted or received via the electronic accounts associated with the plurality of data source providers; and updating, by the one or more processors, the performance profile for the first node profile based on a distribution of a second subset of electronic activities from the second plurality of electronic activities across the plurality of participant types for the one or more participants.

In some embodiments, the participant type of the participant comprises a first value corresponding to a seniority and a second value corresponding to a department.

Another aspect of the present disclosure relates to a system for generating performance profiles of member nodes. The system may include one or more hardware processors configured by machine-readable instructions. The one or more processors may be configured to access a plurality of electronic activities transmitted or received via electronic accounts associated with a plurality of data source providers, the plurality of electronic activities used to maintain a plurality of node profiles, each node profile of the plurality node profile including one or more field-value pairs including respective values generated from at least one of the plurality of electronic activities. The one or more processors may further be configured to identify, for a first node profile of the plurality of node profiles, a subset of electronic activities from the plurality of electronic activities identifying an entity corresponding to the first node profile as a sender or a recipient The one or more processors may further be configured to parse each electronic activity of the subset of electronic activities to identify one or more participants with which the entity corresponding to the first node profile is communicating. The one or more processors may further be configured to access, for each participant of the one or more participants, a second node profile corresponding to the participant from the plurality of node and identify, from each second node profile corresponding to a respective participant of the one or more participants, from a plurality of participant types, a participant type for the participant based on the one or more field-value pairs of the second node profile. The one or more processors may further be configured to determine a distribution of the subset of electronic activities across the plurality of participant types for the one or more participants and generate a performance profile for the first node profile based on the distribution of the subset of electronic activities across the plurality of participant types for the one or more participants.

In some embodiments, the one or more processors may be further configured to identify, for each electronic activity of the subset of electronic activities for the first node profile, an electronic activity type of the electronic activity. The one or more processors may be configured to generate the performance profile by generating the performance profile for the first node profile based on the electronic activity types identified for the subset of electronic activities.

In some embodiments, the one or more processors may be further configured to determine a second distribution of the subset of electronic activities across the electronic activity types. The one or more processors are configured to generate the performance profile by generating the performance profile based on the second distribution.

In some embodiments, the one or more processors may be configured to access the second node profile by accessing the second node profile including one or more field-value pairs generated from a signature embedded in at least one of the plurality of electronic activities.

In some embodiments, the one or more processors may be configured to parse each electronic activity by parsing each electronic activity of the subset of electronic activities to identify one or more keywords embedded in the electronic activity. The one or more processors may be configured to generate the performance profile by generating the performance profile for the first node profile based on the one or more keywords identified from the subset of electronic activities.

Yet another aspect of the present disclosure relates to a non-transitory computer-readable storage medium having instructions embodied thereon, the instructions being executable by one or more processors to perform a method for generating performance profiles of member nodes. The method may include accessing a plurality of electronic activities transmitted or received via electronic accounts associated with a plurality of data source providers, the plurality of electronic activities used to maintain a plurality of node profiles, each node profile of the plurality node profile including one or more field-value pairs including respective values generated from at least one of the plurality of electronic activities. The method may further include identifying, for a first node profile of the plurality of node profiles, a subset of electronic activities from the plurality of electronic activities identifying an entity corresponding to the first node profile as a sender or a recipient and parsing each electronic activity of the subset of electronic activities to identify one or more participants with which the entity corresponding to the first node profile is communicating. The method may further include accessing, for each participant of the one or more participants, a second node profile corresponding to the participant from the plurality of node profiles. The method may further include identifying, from each second node profile corresponding to a respective participant of the one or more participants, from a plurality of participant types, a participant type for the participant based on the one or more field-value pairs of the second node profile. The method may further include determining a distribution of the subset of electronic activities across the plurality of participant types for the one or more participants and generating a performance profile for the first node profile based on the distribution of the subset of electronic activities across the plurality of participant types for the one or more participants.

At least one aspect of this disclosure is directed to a method for generating a performance profile of a node profile using electronic activities linked to the node profile. The method can include accessing, by one or more processors, a plurality of first electronic activities linked to a first node profile maintained by the one or more processors and having an associated timestamp within a time period. For each first electronic activity of the plurality of first electronic activities, the method can include determining, by the one or more processors, a type of the first electronic activity. The method can include selecting, by the one or more processors, a feature extraction policy to generate a first feature array for the first electronic activity based on the type of the first electronic activity. The method can include generating, by the one or more processors, the first feature array for the first electronic activity based on the type of the first electronic activity. The method can include generating, by the one or more processors, a first performance profile of the first node profile for the time period by providing the generated first feature array for each first electronic activity to one or more models trained using second feature arrays corresponding to second electronic activities of second node profiles. Each second node profile can be assigned a respective second performance profile. The method can include storing, by the one or more processors, an association between the first node profile and the first performance profile.

In some embodiments, the method can include, for each first electronic activity of the plurality of first electronic activities, categorizing, by the one or more processors, the first electronic activity into one of at least a first type or a second type, based on a data format of the first electronic activity. In some embodiments, the method can include determining, by the one or processors, a first number of the plurality of first electronic activities categorized as the first type. In some embodiments, the method can include determining, by the one or processors, a second number of the plurality of first electronic activities categorized as the second type. In some embodiments, the method can include generating, by the one or more processors, the first performance profile based on the first number and the second number.

In some embodiments, for at least one electronic activity of the first plurality of electronic activities, the method can include generating the first feature array by parsing, by the one or more processors, the content of the at least one electronic activity. In some embodiments, the method can include generating, by the one or more processors, using a language complexity determination engine, a language complexity score indicating a level of language complexity of the at least one electronic activity. In some embodiments, the method can include determining, by the one or more processors, a character count or word count of the at least one electronic activity. In some embodiments, the method can include determining, by the one or more processors, an estimated amount of time to generate the at least one electronic activity using the language complexity score and the character count or the word count. In some embodiments, the method can include generating, by the one or more processors, the first feature array for the at least one electronic activity based on the estimated amount of time to generate the at least one electronic activity.

In some embodiments, for at least one of the first electronic activities, the method can include generating the first feature array by extracting, by the one or more processors, for the at least one electronic activity, one or more activity field-values from the at least one electronic activity to match the at least one electronic activity to a third node profile of at least one participant of the at least one electronic activity. In some embodiments, the method can include determining, by the one or more processors, from the third node profile to which the at least one electronic activity is matched, an importance metric of the at least one participant of the at least one electronic activity based on at least one field-value pair of the third node profile satisfying an importance determination policy. In some embodiments, the method can include generating, by the one or more processors, the feature array for the at least one electronic activity based on the importance metric of the at least one participant.

In some embodiments, for at least one of the plurality of first electronic activities, the method can include generating the first feature array by comparing, by the one or more processors, the at least one electronic activity with at least a second electronic activity of the plurality of electronic activities to determine a difference in the content between the at least one electronic activity and the second electronic activity. In some embodiments, the method can include determining, by the one or more processors, that the difference in content is below a threshold. In some embodiments, the method can include generating, by the one or more processors, the feature array for the at least one electronic activity based on determining that the difference in content is below the threshold.

In some embodiments, for at least one of the first electronic activities, the method can include generating the first feature array by identifying, by the one or more processors, a recipient of the at least one electronic activity. In some embodiments, the method can include determining, by the one or more processors, that none of the plurality of first electronic activities were sent from the identified recipient. In some embodiments, the method can include generating, by the one or more processors, the feature array for the at least one electronic activity based on the determination that none of the remaining electronic activities of the plurality of first electronic activities were sent from the identified recipient.

In some embodiments, the method can include identifying, by the one or more processors, for at least one electronic activity of the plurality of electronic activities, a third node profile corresponding to a recipient of the first electronic activity. In some embodiments, the method can include determining, by the one or more processors, a connection type of a connection between the first node profile and third node profile. In some embodiments, the method can include discarding, from the plurality of first electronic activities, the at least one electronic activity prior to generating the first performance profile, based on the connection type of the connection between the first node profile and the third node profile.

In some embodiments, the method can include determining the type of at least one electronic activity of the plurality of first electronic activities by determining, by the one or more processors, that the at least one electronic activity is one of an electronic mail activity, an electronic calendar activity or a phone activity.

In some embodiments, the method can include determining, by the one or more processors, from the plurality of first electronic activities, a vacation period for the first node profile using a vacation detection policy. In some embodiments, the method can include determining, by the one or more processors, that the time period overlaps with at least a portion of the vacation period. In some embodiments, the method can include adjusting, by the one or more processors, the first performance profile responsive to determining that the time period overlaps with at least the portion of the vacation period.

In some embodiments, the method can include selecting, by the one or more processors, at least one of the second node profiles based on a field-value pair of the second node profile matching a corresponding field-value pair of the first node profile.

Another aspect of this disclosure is directed to a system for generating a performance profile of a node profile. The system can include one or more hardware processors configured by machine-readable instructions. The processor(s) may be configured to access a plurality of first electronic activities linked to a first node profile maintained by the one or more processors and having an associated timestamp within a time period. For each first electronic activity of the plurality of first electronic activities, the processor(s) may be configured to determine a type of the first electronic activity. The processor(s) may be configured to select a feature extraction policy to generate a first feature array for the first electronic activity based on the type of the first electronic activity. The processor(s) may be configured to generate the first feature array for the first electronic activity based on the type of the first electronic activity. The processor(s) may be configured to generate a first performance profile of the first node profile for the time period by providing the generated first feature array for each first electronic activity to one or more models trained using second feature arrays corresponding to second electronic activities of second node profiles. each second node profile can be assigned a respective second performance profile. The processor(s) may be configured to store an association between the first node profile and the first performance profile.

In some embodiments, the one or more hardware processors may be further configured by the machine-readable instructions to, for each first electronic activity of the plurality of first electronic activities, categorize the first electronic activity into one of at least a first type or a second type, based on a data format of the first electronic activity. In some embodiments, the processor(s) may be configured to determine a first number of the plurality of first electronic activities categorized as the first type. In some embodiments, the processor(s) may be configured to determine a second number of the plurality of first electronic activities categorized as the second type. In some embodiments, the processor(s) may be configured to generate the first performance profile based on the first number and the second number.

In some embodiments, the processor(s) may be configured to, for at least one electronic activity of the first plurality of electronic activities, generate the first feature array by parsing the content of the at least one electronic activity. In some embodiments, the processor(s) may be configured to generate, using a language complexity determination engine, a language complexity score indicating a level of language complexity of the at least one electronic activity. In some embodiments, the processor(s) may be configured to determine a character count or word count of the at least one electronic activity. In some embodiments, the processor(s) may be configured to determine an estimated amount of time to generate the at least one electronic activity using the language complexity score and the character count or the word count. In some embodiments, the processor(s) may be configured to generate the first feature array for the at least one electronic activity based on the estimated amount of time to generate the at least one electronic activity.

In some embodiments, the processor(s) may be configured to, for at least one electronic activity of the first plurality of electronic activities, generate the first feature array by extracting one or more activity field-values from the at least one electronic activity to match the at least one electronic activity to a third node profile of at least one participant of the at least one electronic activity. In some embodiments, the processor(s) may be configured to determine, from the third node profile to which the at least one electronic activity is matched, an importance metric of the at least one participant of the at least one electronic activity based on at least one field-value pair of the third node profile satisfying an importance determination policy. In some embodiments, the processor(s) may be configured to generate the feature array for the at least one electronic activity based on the importance metric of the at least one participant.

In some embodiments, the processor(s) may be configured to, for at least one electronic activity of the first plurality of electronic activities, generate the first feature array by comparing the at least one electronic activity with at least a second electronic activity of the plurality of electronic activities to determine a difference in the content between the at least one electronic activity and the second electronic activity. In some embodiments, the processor(s) may be configured to determine that the difference in content is below a threshold. In some embodiments, the processor(s) may be configured to generate the feature array for the at least one electronic activity based on determining that the difference in content is below the threshold.

In some embodiments, the processor(s) may be configured to, for at least one electronic activity of the first plurality of electronic activities, generate the first feature array by identifying a recipient of the at least one electronic activity. In some embodiments, the processor(s) may be configured to determine that none of the plurality of first electronic activities were sent from the identified recipient. In some embodiments, the processor(s) may be configured to generate the feature array for the at least one electronic activity based on the determination that none of the remaining electronic activities of the plurality of first electronic activities were sent from the identified recipient.

In some embodiments, the processor(s) may be configured to identify, for at least one electronic activity of the plurality of electronic activities, a third node profile corresponding to a recipient of the first electronic activity. In some embodiments, the processor(s) may be configured to determine a connection type of a connection between the first node profile and third node profile. In some embodiments, the processor(s) may be configured to discard, from the plurality of first electronic activities, the at least one electronic activity prior to generating the first performance profile, based on the connection type of the connection between the first node profile and the third node profile.

In some embodiments, the processor(s) may be configured to determine the type of at least one electronic activity of the plurality of first electronic activities by determining that the at least one electronic activity is one of an electronic mail activity, an electronic calendar activity or a phone activity.

In some embodiments, the processor(s) may be configured to determine, from the plurality of first electronic activities, a vacation period for the first node profile using a vacation detection policy. In some embodiments, the processor(s) may be configured to determine that the time period overlaps with at least a portion of the vacation period. In some embodiments, the processor(s) may be configured to adjust the first performance profile responsive to determining that the time period overlaps with at least the portion of the vacation period.

Another aspect of this disclosure is directed to a non-transitory computer-readable storage medium having instructions embodied thereon which, when executed by one or more processors, cause the one or more processors to perform a method for generating a performance profile of a node profile. The method can include accessing a plurality of first electronic activities linked to a first node profile maintained by the one or more processors and having an associated timestamp within a time period. For each first electronic activity of the plurality of first electronic activities, the method can include determining a type of the first electronic activity. The method can include selecting a feature extraction policy to generate a first feature array for the first electronic activity based on the type of the first electronic activity. The method can include generating the first feature array for the first electronic activity based on the type of the first electronic activity. The method can include generating a first performance profile of the first node profile for the time period by providing the generated first feature array for each first electronic activity to one or more models trained using second feature arrays corresponding to second electronic activities of second node profiles. Each second node profile can be assigned a respective second performance profile. The method can include storing an association between the first node profile and the first performance profile.

The present disclosure relates to systems and methods for determining an engagement profile of a participant. The systems and methods may generate the engagement profile based on analysis of the electronic activity level. An example implementation may contain the following steps. The system may access for a first record object electronic activities linked with the first record object. The system may determine the participants involved in the electronic activities linked to the first record object. The system may identify for a participant electronic activities a set of electronic activities including the participant. The system may determine an engagement profile of the participant based on a first number of electronic activities of the set of electronic activities sent by the participant, a second number of the set of electronic activities received by the participant and a temporal distribution of the set of electronic activities. The system may store the engagement profile in one or more data structures.

At least one aspect of the present disclosure relates to a method for generating an engagement profile. The method may include accessing for a first record object of a system of record of a data source provider, a plurality of electronic activities linked with the first record object. Each electronic activity may identify one or more participants associated with the first record object. The first record object may include a first object field-value pair identifying a stage of a process corresponding to the first record object. The method may include identifying for a participant of the one or more participants, from the plurality of electronic activities, a set of electronic activities including the participant. The method may include determining an engagement profile of the participant based on a first number of electronic activities of the set of electronic activities sent by the participant, a second number of the set of electronic activities received by the participant and a temporal distribution of the set of electronic activities. The method may include storing in one or more data structures an association between an identifier of the participant and the engagement profile of the participant for the first record object.

In some implementations of the method, the first record object may be of a first record object type and may include an object field-value pair storing a stage value indicating a proximity to a completion of an event associated with the first record object. In some implementations of the method, determining the engagement profile may further include determining a distribution of the set of electronic activities within a timeframe defined by a stage indicated by the stage value indicating the proximity to the completion of the event.

In some implementations of the method, the method may include determining a volume of the plurality of electronic activities occurring during each of a plurality of stages indicating a different proximity to a completion of an event associated with the first record object. In some implementations of the method, determining the engagement profile may further include determining the engagement profile based on a volume of plurality of electronic activities occurring during each of the plurality of stages.

In some implementations of the method, the method may include determining historical electronic activities of the participant linked with second record objects of the system of record. In some implementations of the method, the method may include determining a first volume of the plurality of electronic activities occurring during each of a plurality of stages indicating a different proximity to a completion of an event associated with the first record object. In some implementations of the method, the method may include determining a second volume of the historical electronic activities occurring during each of a second plurality of stages indicating a different proximity to a second completion of a second event associated with each of the second record objects. In some implementations of the method, determining the engagement profile may further include determining the engagement profile based on the first volume of the plurality of electronic activities during each of the plurality of stages and the second volume of the plurality of electronic activities during each of the second plurality of stages.

The method can include determining a completion score indicating a likelihood of completing an event associated with the first record object. In some implementations of the method, the completion score may be based on the engagement profile of the participant. In some implementations of the method, the method may include determining one or more field-value pairs of a node profile of the participant. In some implementations of the method, the method may include identifying an engagement profile generation policy based on the one or more field-value pairs of the node profile. In some implementations of the method, determining the engagement profile of the participant may include determining the engagement profile using the identified engagement profile generation policy.

The method can include determining a second engagement profile generation policy for a second participant of the one or more participants. In some implementations of the method, the method may include determining by using a second engagement profile generation policy, a second engagement profile for the second participant. In some implementations of the method, the method may include determining a stage value indicating a proximity to a completion of an event associated with the first record object based on the second engagement profile for the second participant.

The method can include determining a second engagement profile generation policy for each of the one or more participants. In some implementations of the method, the method may include determining by using a respective second engagement profile generation policy, a second engagement profile for each of the one or more participants. In some implementations of the method, the method may include determining a completion score indicating a likelihood of completing an event associated with the first record object. In some implementations of the method, the completion score may be based on the second engagement profile for each of the one or more participants.

The method can include identifying a plurality of record objects of the system of record associated with the participant. In some implementations of the method, the method may include determining a respective set of historical electronic activities of the participant linked with each of the plurality of record objects. In some implementations of the method, the method may include determining by using the engagement profile generation policy, a respective engagement profile for each of the plurality of record objects based on the respective set of historical electronic activities. In some implementations of the method, the method may include generating a production profile of the participant based on the respective engagement profile for each of the plurality of record objects.

In some implementations of the method, the method may include determining for a new record object, a completion score for the participant. In some implementations of the method, the completion score may indicate a likelihood of completing an event associated with the first record object. In some implementations of the method, the method may include generating a recommendation to assign the new record object to the participant responsive to determining that the completion score satisfies a record object assignment policy.

At least one aspect of the present disclosure relates to a system configured for generating an engagement profile. The system may include one or more hardware processors configured by machine-readable instructions. The processor(s) may be configured to access for a first record object of a system of record of a data source provider, a plurality of electronic activities linked with the first record object. Each electronic activity may identify one or more participants associated with the first record object. The first record object may include a first object field-value pair identifying a stage of a process corresponding to the first record object. The processor(s) may be configured to identify for a participant of the one or more participants, from the plurality of electronic activities, a set of electronic activities including the participant. The processor(s) may be configured to determine an engagement profile of the participant based on a first number of electronic activities of the set of electronic activities sent by the participant, a second number of the set of electronic activities received by the participant and a temporal distribution of the set of electronic activities. The processor(s) may be configured to store in one or more data structures. An association between an identifier of the participant and the engagement profile of the participant for the first record object.

In some implementations of the system, the first record object may be of a first record object type and includes an object field-value pair storing a stage value indicating a proximity to a completion of an event associated with the first record object. In some implementations of the system, determining the engagement profile may further include determining a distribution of the set of electronic activities within a timeframe defined by a stage indicated by the stage value indicating the proximity to the completion of the event.

In some implementations of the system, the processor(s) may be configured to determine a volume of the plurality of electronic activities occurring during each of a plurality of stages indicating a different proximity to a completion of an event associated with the first record object. In some implementations of the system, determining the engagement profile may further include determining the engagement profile based on a volume of plurality of electronic activities occurring during each of the plurality of stages.

In some implementations of the system, the processor(s) may be configured to determine historical electronic activities of the participant linked with second record objects of the system of record. In some implementations of the system, the processor(s) may be configured to determine a first volume of the plurality of electronic activities occurring during each of a plurality of stages indicating a different proximity to a completion of an event associated with the first record object. In some implementations of the system, the processor(s) may be configured to determine a second volume of the historical electronic activities occurring during each of a second plurality of stages indicating a different proximity to a second completion of a second event associated with each of the second record objects. In some implementations of the system, determining the engagement profile may further include determining the engagement profile based on the first volume of the plurality of electronic activities during each of the plurality of stages and the second volume of the plurality of electronic activities during each of the second plurality of stages.

In some implementations of the system, the processor(s) may be configured to determine a completion score indicating a likelihood of completing an event associated with the first record object. In some implementations of the system, the completion score may be based on the engagement profile of the participant. In some implementations of the system, the processor(s) may be configured to determine one or more field-value pairs of a node profile of the participant. In some implementations of the system, the processor(s) may be configured to identify an engagement profile generation policy based on the one or more field-value pairs of the node profile. In some implementations of the system, determining the engagement profile of the participant may include determining the engagement profile using the identified engagement profile generation policy.

In some implementations of the system, the processor(s) may be configured to determine a second engagement profile generation policy for a second participant of the one or more participants. In some implementations of the system, the processor(s) may be configured to determine by using a second engagement profile generation policy, a second engagement profile for the second participant. In some implementations of the system, the processor(s) may be configured to determine a stage value indicating a proximity to a completion of an event associated with the first record object based on the second engagement profile for the second participant.

In some implementations of the system, the processor(s) may be configured to determine a second engagement profile generation policy for each of the one or more participants. In some implementations of the system, the processor(s) may be configured to determine, by using a respective second engagement profile generation policy, a second engagement profile for each of the one or more participants. In some implementations of the system, the processor(s) may be configured to determine a completion score indicating a likelihood of completing an event associated with the first record object. In some implementations of the system, the completion score may be based on the second engagement profile for each of the one or more participants.

In some implementations of the system, the processor(s) may be configured to identify a plurality of record objects of the system of record associated with the participant. In some implementations of the system, the processor(s) may be configured to determine a respective set of historical electronic activities of the participant linked with each of the plurality of record objects. In some implementations of the system, the processor(s) may be configured to determine, by using the engagement profile generation policy, a respective engagement profile for each of the plurality of record objects based on the respective set of historical electronic activities. In some implementations of the system, the processor(s) may be configured to generate a production profile of the participant based on the respective engagement profile for each of the plurality of record objects.

In some implementations of the system, the processor(s) may be configured to determine for a new record object a completion score for the participant. In some implementations of the system, the completion score may indicate a likelihood of completing an event associated with the first record object. In some implementations of the system, the processor(s) may be configured to generate a recommendation to assign the new record object to the participant responsive to determining that the completion score satisfies a record object assignment policy.

At least one aspect of the present disclosure relates to a non-transitory computer-readable storage medium having instructions embodied thereon, the instructions being executable by one or more processors to perform a method for generating an engagement profile. The method may include accessing for a first record object of a system of record of a data source provider, a plurality of electronic activities linked with the first record object. Each electronic activity may identify one or more participants associated with the first record object. The first record object may include a first object field-value pair identifying a stage of a process corresponding to the first record object. The method may include identifying for a participant of the one or more participants, from the plurality of electronic activities, a set of electronic activities including the participant. The method may include determining an engagement profile of the participant based on a first number of electronic activities of the set of electronic activities sent by the participant, a second number of the set of electronic activities received by the participant and a temporal distribution of the set of electronic activities. The method may include storing in one or more data structures. An association between an identifier of the participant and the engagement profile of the participant for the first record object.

At least one aspect of the present disclosure relates to a method for predicting the performance of a member node. The method may include identifying, by one or more processors, a first node profile from a plurality of node profiles corresponding to a plurality of unique entities. Each node profile of the plurality of node profiles includes one or more node field-value pairs. Each node field-value pair of the node profile is associated with a corresponding field and a node field value. The method may include identifying, by the one or more processors, a first plurality of electronic activities transmitted or received via electronic accounts associated with one or more data source providers and associated with the first node profile. The method may include identifying, by the one or more processors, a first group of the plurality of the node profiles of a first category. Each node profile of the first group of the plurality of node profiles is associated with a predetermined event. The method may include selecting, by the one or more processors, from the first group of the plurality of the node profiles, a second group of node profiles having node field-value pairs corresponding to one or more node field-value pairs of the first node profile. The method may include parsing, by the one or more processors, each electronic activity of the first plurality of electronic activities to identify a creation timestamp of the electronic activity and at least one participant characteristic of participants of the electronic activity. The method may include generating, by the one or more processors, an input array based on the timestamp and the at least one participant characteristic identified from each electronic activity of the first plurality of electronic activities. The method may include generating, for each node profile of the second group of node profiles, a respective array based on creation timestamps and participant characteristics identified from electronic activities identifying an entity corresponding to the node profile of the second group of node profiles. The method may include determining, by the one or more processors, by providing the input array as an input in a machine learning model trained using the generated respective arrays, a probability score indicating a likelihood that the node profile belongs to the first category. The method may include storing, by the one or more processors, an association between the first node profile and the probability score.

In some embodiments of the method, the method can include identifying, by the one or more processors, a third group of the plurality of the node profiles of a second category. Each node profile of the third group of the plurality of node profiles is associated with the predetermined event. The method may further include selecting, by the one or more processors, from the third group of the plurality of the node profiles, a fourth group of node profiles having node field-value pairs corresponding to the one or more node field-value pairs of the first node profile. The method may further include generating, for each node profile of the fourth group of node profiles, a respective array based on the creation timestamps and the participant characteristics identified from electronic activities identifying an entity corresponding to the node profile of the fourth group of node profiles. The method may further include training, by the one or more processors, the machine learning model using the respective arrays based on the creation timestamps and the participant characteristics identified from electronic activities identifying the entity corresponding to the node profile of the fourth group of node profiles.

In some embodiments of the method, the machine learning model includes one or more of a convolutional neural network or a bayesian algorithm to determine the probability score.

In some embodiments of the method, it may further include receiving, by the one or more processors for each of the plurality of node profiles, a performance profile indicating at least one of an electronic activity transmission frequency or an electronic activity transmission count. The method may further include identifying the first group of the plurality of node profiles based on the performance profile.

In some embodiments of the method, the one or more node field-value pairs of the first node profile store a role value of the first node profile. The participant characteristic comprises a role value of the node profile corresponding to the participant. The method can include identifying a type of the electronic activity. The method may further include generating the input array based on the type of the electronic activity. The method can include receiving a list from a first entity containing an identification of each of the first group of the plurality of node profiles. In some embodiments of the method, each node profile of the second group of node profiles includes a first field-value pair corresponding to an entity name that matches a corresponding first field-value pair of the first node profile and a second field-value pair corresponding to a job title that matches a corresponding second field-value pair of the first node profile.

At least one aspect of the present disclosure relates to a system configured to predict performance of a member node. The system may include one or more hardware processors configured by machine-readable instructions. The processor(s) may be configured to identify a first node profile from a plurality of node profiles corresponding to a plurality of unique entities. Each node profile of the plurality of node profiles includes one or more node field-value pairs. Each node field-value pair of the node profile is associated with a corresponding field and a node field value. The processor(s) may be configured to identify a first plurality of electronic activities transmitted or received via electronic accounts associated with one or more data source providers and associated with the first node profile. The processor(s) may be configured to identify a first group of the plurality of the node profiles of a first category, each node profile of the first group of the plurality of node profiles associated with a predetermined event. The processor(s) may be configured to select from the first group of the plurality of the node profiles, a second group of node profiles having node field-value pairs corresponding to one or more node field-value pairs of the first node profile. The processor(s) may be configured to parse each electronic activity of the first plurality of electronic activities to identify a creation timestamp of the electronic activity and at least one participant characteristic of participants of the electronic activity. The processor(s) may be configured to generate an input array based on the timestamp and the at least one participant characteristic identified from each electronic activity of the first plurality of electronic activities. The processor(s) may be configured to generate, for each node profile of the second group of node profiles, a respective array based on creation timestamps and participant characteristics identified from electronic activities identifying an entity corresponding to the node profile of the second group of node profiles. The processor(s) may be configured to determine, by providing the input array as an input in a machine learning model trained using the generated respective arrays, a probability score indicating a likelihood that the node profile belongs to the first category. The processor(s) may be configured to store an association between the first node profile and the probability score.

In some embodiments of the system, the processor(s) may be further configured to identify a third group of the plurality of the node profiles of a second category. Each node profile of the third group of the plurality of node profiles is associated with the predetermined event. The processor(s) may be further configured to select, from the third group of the plurality of the node profiles, a fourth group of node profiles having node field-value pairs corresponding to the one or more node field-value pairs of the first node profile. The processor(s) may be further configured to generate, for each node profile of the fourth group of node profiles, a respective array based on the creation timestamps and the participant characteristics identified from electronic activities identifying an entity corresponding to the node profile of the fourth group of node profiles. The processor(s) may be further configured to train the machine learning model using the respective arrays based on the creation timestamps and the participant characteristics identified from electronic activities identifying the entity corresponding to the node profile of the fourth group of node profiles. In some embodiments of the system, the machine learning model includes one or more of a convolutional neural network or a bayesian algorithm to determine the probability score.

In some embodiments of the system, the processor(s) may be further configured to receive, for each of the plurality of node profiles, a performance profile indicating at least one of an electronic activity transmission frequency or an electronic activity transmission count. The processor(s) may be further configured to identify the first group of the plurality of node profiles based on the performance profile.

In some embodiments of the system, the one or more node field-value pairs of the first node profile store a role value of the first node profile. In some embodiments of the system, the participant characteristic comprises a role value of the node profile corresponding to the participant. In some embodiments of the system, the processor(s) may be further configured to identify a type of the electronic activity. The processor(s) may be further configured to generate the input array based on the type of the electronic activity. In some embodiments of the system, the processor(s) may be further configured to receive a list from a first entity containing an identification of each of the first group of the plurality of node profiles. In some embodiments of the system, each node profile of the second group of node profiles includes a first field-value pair corresponding to an entity name that matches a corresponding first field-value pair of the first node profile and a second field-value pair corresponding to a job title that matches a corresponding second field-value pair of the first node profile.

At least one aspect of the present disclosure relates to a non-transitory computer-readable storage medium having instructions embodied thereon, the instructions being executable by one or more processors to perform a method for predicting performance of a node. The method may include identifying, by one or more processors, a first node profile from a plurality of node profiles corresponding to a plurality of unique entities. Each node profile of the plurality of node profiles includes one or more node field-value pairs. Each node field-value pair of the node profile is associated with a corresponding field and a node field value. The method may include identifying, by the one or more processors, a first plurality of electronic activities transmitted or received via electronic accounts associated with one or more data source providers and associated with the first node profile. The method may include identifying, by the one or more processors, a first group of the plurality of the node profiles of a first category. Each node profile of the first group of the plurality of node profiles is associated with a predetermined event. The method may include selecting, by the one or more processors, from the first group of the plurality of the node profiles, a second group of node profiles having node field-value pairs corresponding to one or more node field-value pairs of the first node profile. The method may include parsing, by the one or more processors, each electronic activity of the first plurality of electronic activities to identify a creation timestamp of the electronic activity and at least one participant characteristic of participants of the electronic activity. The method may include generating, by the one or more processors, an input array based on the timestamp and the at least one participant characteristic identified from each electronic activity of the first plurality of electronic activities. The method may include generating, for each node profile of the second group of node profiles, a respective array based on creation timestamps and participant characteristics identified from electronic activities identifying an entity corresponding to the node profile of the second group of node profiles. The method may include determining, by the one or more processors, by providing the input array as an input in a machine learning model trained using the generated respective arrays, a probability score indicating a likelihood that the node profile belongs to the first category. The method may include storing, by the one or more processors, an association between the first node profile and the probability score.

In some embodiments of the non-transitory computer-readable storage medium, the method may further include identifying, by the one or more processors, a third group of the plurality of the node profiles of a second category. Each node profile of the third group of the plurality of node profiles is associated with the predetermined event. The method may further include selecting, by the one or more processors, from the third group of the plurality of the node profiles, a fourth group of node profiles having node field-value pairs corresponding to the one or more node field-value pairs of the first node profile. The method may further include generating, for each node profile of the fourth group of node profiles, a respective array based on the creation timestamps and the participant characteristics identified from electronic activities identifying an entity corresponding to the node profile of the fourth group of node profiles. The method may further include training, by the one or more processors, the machine learning model using the respective arrays based on the creation timestamps and the participant characteristics identified from electronic activities identifying the entity corresponding to the node profile of the fourth group of node profiles.

One aspect of the present disclosure relates to a method for generating performance profiles using electronic activities matched with record objects of one or more systems of record. The method may include accessing a plurality of record objects of a system of record of a data source provider. Each record object of the plurality of record objects corresponding to a record object type and may include one or more object fields having one or more object field values. Each of the plurality of record objects may include one or more electronic activities. The method may include identifying, from the plurality of record objects, a subset of record objects associated with a node profile corresponding to an entity. The method may include identifying, for each record object of the subset of record objects, electronic activities linked to the record object. The method may include determining, for each record object of the subset of record objects, a respective entity engagement profile for the entity based on the electronic activities linked to the record object and one or more object field-value pairs of the record object. The method may include generating a composite entity engagement profile of the entity based on each respective entity engagement profile corresponding to each record object of the subset of record objects. The method may include storing, in one or more data structures, an association between the entity and the entity performance profile.

Another aspect of the present disclosure relates to a system for generating performance profiles using electronic activities matched with record objects of one or more systems of record. The system may include one or more hardware processors configured by machine-readable instructions. The processor(s) may be configured to access a plurality of record objects of a system of record of a data source provider. Each record object of the plurality of record objects may include one or more object fields having one or more object field values. Each of the plurality of record objects may include one or more electronic activities. The processor(s) may be configured to identify, from the plurality of record objects, a subset of record objects associated with a node profile corresponding to an entity. The processor(s) may be configured to identify, for each record object of the subset of record objects, electronic activities linked to the record object. The processor(s) may be configured to determine, for each record object of the subset of record objects, a respective entity engagement profile for the entity based on the electronic activities linked to the record object and one or more object field-value pairs of the record object. The processor(s) may be configured to generate a composite entity engagement profile of the entity based on each respective entity engagement profile corresponding to each record object of the subset of record objects. The processor(s) may be configured to store, in one or more data structures, an association between the entity and the entity performance profile.

Yet another aspect of the present disclosure relates to a non-transitory computer-readable storage medium having instructions embodied thereon, the instructions being executable by one or more processors to perform a method for generating performance profiles using electronic activities matched with record objects of one or more systems of record. The method may include accessing a plurality of record objects of a system of record of a data source provider. Each record object of the plurality of record objects may include one or more object fields having one or more object field values. Each of the plurality of record objects may include one or more electronic activities. The method may include identifying, from the plurality of record objects, a subset of record objects associated with a node profile corresponding to an entity. The method may include identifying, for each record object of the subset of record objects, electronic activities linked to the record object. The method may include determining, for each record object of the subset of record objects, a respective entity engagement profile for the entity based on the electronic activities linked to the record object and one or more object field-value pairs of the record object. The method may include generating a composite entity engagement profile of the entity based on each respective entity engagement profile corresponding to each record object of the subset of record objects. The method may include storing, in one or more data structures, an association between the entity and the entity performance profile.

FIG. 1 illustrates a tiered system architecture for aggregating electronic activities and synchronizing the electronic activities to one or more systems of record according to embodiments of the present disclosure;

FIG. 2 illustrates a process flow for aggregating electronic activities and synchronizing the electronic activities to one or more systems of record according to embodiments of the present disclosure;

FIG. 3 illustrates a processing flow diagram for aggregating electronic activities and synchronizing the electronic activities to one or more systems of record according to embodiments of the present disclosure;

FIG. 4 illustrates a node graph generation system for constructing a node graph based on electronic activity according to embodiments of the present disclosure;

FIGS. 5A-5C illustrate various types of example electronic activities according to embodiments of the present disclosure;

FIG. 6A illustrates a representation of a node profile of a node according to embodiments of the present disclosure;

FIG. 6B illustrates representations of three electronic activities and representations of three states of a node profile of a node according to embodiments of the present disclosure;

FIG. 7 illustrates a series of electronic activities between two nodes according to embodiments of the present disclosure;

FIG. 8 illustrates electronic activities involving two nodes and the impact a time decaying score has on the connection strength between the two nodes according to embodiments of the present disclosure;

FIG. 9 illustrates a block diagram of an example electronic activity linking engine according to embodiments of the present disclosure;

FIG. 10 illustrates a plurality of example record objects, and their interconnections, according to embodiments of the present disclosure;

FIG. 11 illustrates the restriction of a first grouping of record objects with a second grouping of record objects according to embodiments of the present disclosure;

FIG. 12 illustrates the application of a plurality of matching strategies and then pruning of the matched record objects with a second plurality of matching strategies according to embodiments of the present disclosure;

FIG. 13 illustrates an example calculation for calculating the engagement score of an opportunity record object according to embodiments of the present disclosure;

FIG. 14 illustrates an example user interface identifying various pieces of information that can be extracted from an electronic activity according to embodiments of the present disclosure;

FIG. 15 illustrates an example user interface identifying a record object corresponding to an opportunity according to embodiments of the present disclosure;

FIG. 16 illustrates a block diagram of an example process flow for processing electronic activities in a single-tenant configuration according to embodiments of the present disclosure;

FIG. 17 illustrates a block diagram of an example process flow for processing electronic activities in a multi-tenant configuration according to embodiments of the present disclosure;

FIG. 18 illustrates a block diagram of an example process flow for matching electronic activities with record objects according to embodiments of the present disclosure;

FIG. 19 illustrates a block diagram of an example method to match electronic activities directly to record objects according to embodiments of the present disclosure;

FIG. 20 illustrates a block diagram of an example process flow for matching electronic activities with record objects according to embodiments of the present disclosure;

FIG. 21 illustrates a block diagram of an example method to match electronic activities with record objects according to embodiments of the present disclosure;

FIG. 22 illustrates a block diagram of an example process to match electronic activities with node profiles according to embodiments of the present disclosure;

FIG. 23 illustrates a block diagram of an example method to match electronic activities with node profiles according to embodiments of the present disclosure;

FIG. 24 illustrates a block diagram of an example method to match electronic objects with node profiles according to embodiments of the present disclosure;

FIG. 25 illustrates a block diagram of a series of electronic activities between two nodes according to embodiments of the present disclosure;

FIG. 26 illustrates a representation of a node profile of a node according to embodiments of the present disclosure;

FIG. 27 illustrates a block diagram of an example method to generate confidence scores of values of fields based on data points according to embodiments of the present disclosure;

FIG. 28 illustrates a simplified block diagram of a representative server system and client computer system according to embodiments of the present disclosure;

FIG. 29 illustrates an example flow for measuring goals based on matching electronic activities to record objects, according to embodiments of the present disclosure;

FIG. 30 illustrates an example method of measuring goals based on matching electronic activities to record objects, according to embodiments of the present disclosure;

FIG. 31 illustrates an example system for managing electronic activity driven targets, according to embodiments of the present disclosure;

FIG. 32 illustrates an example method for managing electronic activity driven targets, according to embodiments of the present disclosure;

FIG. 33 illustrates a use case diagram of an example system for generating performance profiles according to embodiments of the present disclosure;

FIG. 34 illustrates a flow diagram of an example method for generating performance scores based on node performance profiles according to embodiments of the present disclosure;

FIG. 35 illustrates a use case diagram of an example sequence for generating performance profiles of member nodes, according to embodiments of the present disclosure;

FIG. 36 illustrates a flow diagram of an example method for generating performance profiles of member nodes, according to embodiments of the present disclosure;

FIG. 37 illustrates a block diagram of a series of electronic activities, according to embodiments of the present disclosure;

FIG. 38 illustrates an example method for updating a node profile, according to embodiments of the present disclosure;

FIG. 39 illustrates an example system for generating a performance profile of a node profile, according to embodiments of the present disclosure;

FIG. 40 illustrates a method for generating a performance profile of a node profile, according to embodiments of the present disclosure;

FIG. 41 illustrates a block diagram of an example process flow for determining an engagement profile according to embodiments of the present disclosure;

FIG. 42 illustrates a block diagram of an example method to generate an engagement profile according to embodiments of the present disclosure;

FIG. 43 illustrates a block diagram of an example process flow for predicting success/performance of a member node based on a type of task and a job title according to embodiments of the present disclosure;

FIG. 44 illustrates an example method for predicting performance of a member node according to embodiments of the present disclosure;

FIG. 45A illustrates a use case diagram showing a plurality of record objects within a system of record for generating performance profiles according to embodiments of the present disclosure;

FIG. 45B illustrates a set of graphical representations of engagement profiles corresponding to an entity according to embodiments of the present disclosure;

FIG. 45C illustrates a plurality of electronic activity distributions for different entities linked to the same record object according to embodiments of the present disclosure;

FIG. 45D illustrates a graphical representation of an example composite engagement profile for the entity corresponding to the engagement profiles of FIG. 45B according to embodiments of the present disclosure; and

FIG. 46 illustrates an example method for generating performance profiles using electronic activities matched with record objects of one or more systems of record according to embodiments of the present disclosure.

The present disclosure relates to systems and methods for constructing a node graph based on electronic activity. The node graph can include a plurality of nodes and a plurality of edges between the nodes indicating activity or relationships that are derived from a plurality of data sources that can include one or more types of electronic activities. The plurality of data sources can include email or messaging servers, phone servers, servers storing calendar information, meeting information, among others. The plurality of data sources further includes systems of record, such as customer relationship management systems, enterprise resource planning systems, document management systems, applicant tracking systems or other source of data that may maintain electronic activities, activities or records.

The present disclosure further relates to systems and methods for using the node graph to manage, maintain, improve, or otherwise modify one or more systems of record by linking and or synchronizing electronic activities to one or more record objects of the systems of record. In particular, the systems described herein can be configured to automatically synchronize real-time or near real-time electronic activity to one or more objects of systems of record. The systems can further extract business process information from the systems of record and in combination with the node graph, use the extracted business process information to improve business processes and to provide data driven solutions to improve such business processes.

Referring briefly to FIG. 1 , FIG. 1 illustrates a tiered system architecture for aggregating electronic activities and synchronizing the electronic activities to one or more systems of record according to embodiments of the present disclosure. As shown in FIG. 1 , at the first tier, the system aggregates electronic activities from one or more data source providers. At the second tier, the system extracts information from the aggregated electronic activities and one or more systems of record of one or more data source providers to construct and maintain a node graph including the plurality of nodes and edges indicating the connections between the nodes. At the third tier, the system utilizes the electronic activities, the systems of record, and the node graph to provide data driven insights to improve one or more business processes of the data source providers and to assist various data source providers in extracting data driven insights.

FIG. 2 illustrates a process flow for aggregating electronic activities and synchronizing the electronic activities to one or more systems of record according to embodiments of the present disclosure. The system can be configured to receive and aggregate electronic activities identifying one or more nodes. The system can parse the electronic activities and extract information from the electronic activities to generate node profiles for each node, log activities and maintain changes made to each of the node profiles maintained by the system. The system can further be configured to extract information from the electronic activities of the nodes and determine insights or metrics that can be shared with one or more other nodes and the users of the system. The system can be further configured to synchronize the electronic activities to objects of one or more systems of record.

In a particular use case, sales representatives of an organization may be involved in electronic activities, such as emails, phone calls, meetings, among others that can be tracked and captured by the system via ingestion from one or more data sources of the organization or other organizations. The system can extract information from the electronic activities that may be associated with deals or opportunities the sales representatives are working on. The system can use the information from these electronic activities to generate reports for managers of the organization. These reports are generated based on data derived from electronic activity without requiring the sales representatives to perform any additional activities. Furthermore, the managers also do not need to spend time generating these reports as the system can automatically generate these reports. Furthermore, the system can identify trends and behaviors that may be determined through machine learning techniques otherwise not tracked by the managers, thereby providing reports that may otherwise not be generated by the managers. Further, sales representatives may also no longer be required to spend time synchronizing electronic activities to one or more systems of record. Rather, the system can be configured to automatically synchronize the electronic activities to the appropriate objects of the one or more systems of record. The system can further receive information from the one or more systems and records to determine the results associated with the sales representative's efforts and perform analytics to generate recommendations to assist the sales representatives achieve their goals and eventually improve their performance as sales representatives as well as provide company management with recommendations about improving the performance of the overall business.

Referring now to FIG. 3 , FIG. 3 illustrates a processing flow diagram for aggregating electronic activities, processing the electronic activities to update node profiles of people and to construct a node graph, and synchronizing the electronic activities to one or more systems of record. The process flow 9302 can be executed by a data processing system 9300 that can receive electronic activity and other data from a plurality of data source providers 9350 a - n . Each data source provider 9350 can include one or more data sources 9355 a - n and/or one or more system of record instances 9360 . Examples of data sources can include electronic mail servers, telephone log servers, contact servers, other types of servers and end-user applications that may receive or maintain electronic activity data or profile data relating to one or more nodes. The data processing system 9300 can ingest electronic activity ( 9305 ). The data processing system 9300 can featurize and tag the ingested electronic activity ( 9310 ) and store the featurized data in a featurized data store ( 9315 ). The data processing system 9300 can process the featurized data ( 9320 ) to generate a node graph including a plurality of node profiles ( 9325 ). The data processing system 9300 can further maintain a plurality of system of record instances 9330 a - n corresponding to system of record instances of the data source providers 9350 . The data processing system 9300 can utilize the system of record instances to augment the node profiles of the node graph by synchronizing data stored in the system of record instances maintained by the data processing system ( 9335 ). The data processing system 9300 can further match the ingested electronic activities to one or more record objects maintained in one or more systems of record instances of the data source provider from which the electronic activity was received ( 9340 ). The data processing system 9300 can further synchronize the electronic activity matched to record objects to update the system of record instances of the data source provider ( 9335 ). Furthermore, the data processing system 9300 can use the featurized data to provide performance predictions and generate other business process related outputs, insights and recommendations ( 9345 ).

As described herein, electronic activity can include any type of electronic communication that can be stored or logged. Examples of electronic activity can include electronic mail messages, telephone calls, calendar invitations, social media messages, mobile application messages, instant messages, cellular messages such as SMS, MMS, among others, as well as electronic records of any other activity, such as digital content, such as files, photographs, screenshots, browser history, internet activity, shared documents, among others.

The electronic activity can be stored on one or more data source servers. The electronic activity can be owned or managed by one or more data source providers, such as companies that utilize the services of the data processing system 9300 . The electronic activity can be associated with or otherwise maintained, stored or aggregated by an electronic activity source, such as Google G Suite, Microsoft Office365, Microsoft Exchange, among others. In some embodiments, the electronic activity can be real-time (or near real-time) electronic activity, asynchronous electronic activity (such as emails, text messages, among others) or synchronous electronic activity (such as meetings, phone calls, video calls), or other activity in which two parties are communicating simultaneously.

1. Systems and Methods for Generating a Node Graph Using Electronic Activities

As described above, the present disclosure relates to systems and methods for constructing a node graph based on electronic activity. The node graph can include a plurality of nodes and a plurality of edges between the nodes indicating activity or relationships that are derived from a plurality of data sources that can include one or more types of electronic activities. The plurality of data sources can further include systems of record, such as customer relationship management systems, enterprise resource planning systems, document management systems, applicant tracking systems or other source of data that may maintain electronic activities, activities or records.

Referring now to FIG. 4 , FIG. 4 illustrates a node graph generation system 200 for constructing a node graph based on electronic activity. The node graph generation system 200 can be, include or be part of the data processing system 9300 described in FIG. 3 . The node graph generation system 200 can include an electronic activity ingestor 205 , an electronic activity parser 210 , a tagging engine 265 , a source health scorer 215 , a node profile manager 220 , a node profile database 225 , a record data extractor 230 , an attribute value confidence scorer 235 , a node pairing engine 240 , a node resolution engine 245 , an electronic activity linking engine 250 , a record object manager 255 , a data source provider network generator 260 , a tagging engine 265 and a filtering engine 270 . The node graph generation system 200 can receive electronic activity and systems of record data from one or more data source providers 9350 . The data source providers can provide electronic activity or data stored or maintained on a plurality of data sources 355 and one or more systems of record 360 .

Referring now to FIG. 5A , FIG. 5A illustrates an example electronic message. The electronic message 505 can identify one or more recipients 510 , one or more senders 512 , a subject line 514 , an email body 516 , an email signature 518 and a message header 520 . The message header can include additional information relating to the transmission and receipt of the email message, including a time at which the email was sent, a message identifier identifying a message, an IP address associated with the message, a location associated with the message, a time zone associated with the sender, a time at which the message was transmitted, received, and first accessed, among others. The electronic message 505 can include additional data in the electronic message 505 or in the header or metadata of the electronic message 505 .

Referring now to FIG. 5B , FIG. 5B illustrates an example call entry representing a phone call or other synchronous communication is shown. The call entry 525 can identify a caller 530 , a location 532 of the caller, a time zone 534 of the caller, a receiver 536 , a location 538 of the receiver, a time zone 540 of the receiver, a start date and time 542 , an end date and time 544 , a duration 548 and a list of participants 548 . In some embodiments, the times at which each participant joined and left the call can be included. Furthermore, the locations from which each of the callers called can be determined based on determining if the user called from a landline, cell phone, or voice over IP call, among others. The call entry 525 can also include fields for phone number prefixes (e.g., 800 , 866 , and 877 ), phone number extensions, and caller ID information.

Referring now to FIG. 5C , FIG. 5C illustrates an example calendar entry 560 . The calendar entry 560 can identify a sender 562 , a list of participants 562 , a start date and time 566 location 532 of the caller, an end date and time 568 , a duration 570 of the calendar entry, a subject 572 of the calendar entry, a body 574 of the calendar entry, one or more attachments 576 included in the calendar entry and a location of event, described by the calendar entry 578 . The calendar entry can include additional data in the calendar entry or in the header or metadata of the calendar entry 560 .

In some embodiments, the electronic activities are exchanged between or otherwise involve nodes. In some embodiments, nodes can be representative of people or companies. In some embodiments, nodes can be member nodes or group nodes. A member node may refer to a node representative of a person that is part of a company or other organizational entity. A group node may refer to a node that is representative of the company or other organizational entity and is linked to multiple member nodes. The electronic activity may be exchanged between member nodes in which case the system is configured to identify the member nodes and the one or more group nodes associated with each of the member nodes.

The data processing system 9300 or the node graph generation system 200 can be configured to assign each electronic activity a unique electronic activity identifier. This unique electronic activity identifier can be used to uniquely identify the electronic activity. Further, each electronic activity can be associated with a source that provides the electronic activity. In some embodiments, the data source can be the company or entity that authorizes the system 9300 or 200 to receive the electronic activity. In some embodiments, the source can correspond to a system of record, an electronic activity server that stores or manages electronic activity, or any other server that stores or manages electronic activity related to a company or entity. As will be described herein, the quality, health or hygiene of the source of the electronic activity may affect the role the electronic activity plays in generating the node graph. The node graph generation system 200 can be configured to determine a time at which the electronic activity occurred. In some embodiments, the time may be based on when the electronic activity was transmitted, received or recorded. As will be described herein, the time associated with the electronic activity can also affect the role the electronic activity plays in generating the node graph.

Referring again to FIG. 4 , additional details relating to the functions performed by various modules of the node graph generation system are provided herein.

A. Electronic Activity Ingestion

The electronic activity ingestor 205 can be any script, file, program, application, set of instructions, or computer-executable code that is configured to enable a computing device on which the electronic activity ingestor 205 is executed to perform one or more functions of the electronic activity ingestor 205 described herein. The electronic activity ingestor 205 can be configured to ingest electronic activities from the plurality of data source providers. The electronic activities may be received or ingested in real-time or asynchronously as electronic activities are generated, transmitted or stored by the one or more data source providers.

The node graph generation system 200 can ingest electronic activity from a plurality of different source providers. In some embodiments, the node graph generation system 200 can be configured to manage electronic activities and one or more systems of record for one or more enterprises, organizations, companies, businesses, institutions or any other group associated with a plurality of electronic activity accounts. The node graph generation system 200 can ingest electronic activities from one or more servers that hosts, processes, stores or manages electronic activities. In some embodiments, the one or more servers can be electronic mail or messaging servers. The node graph generation system 200 can ingest all or a portion of the electronic activities stored or managed by the one or more servers. In some embodiments, the node graph generation system 200 can ingest the electronic activities stored or managed by the one or more servers once or repeatedly on a periodic basis, such as daily, weekly, monthly or any other frequency.

The node graph generation system 200 can further ingest other data that may be used to generate or update node profiles of one or more nodes maintained by the node graph generation system 200 . The other data may also be stored by the one or more servers that hosts, processes, stores or manages electronic activities. This data can include contact data, such as Names, addresses, phone numbers, Company information, titles, among others.

The node graph generation system 200 can further ingest data from one or more systems of record. The systems of record can be hosted, processed, stored or managed by one or more servers of the systems of record. The systems of record can be linked or otherwise associated with the one or more servers that host, process, store or manage electronic activities. In some embodiments, both the servers associated with the electronic activities and the servers maintaining the systems of record may belong to the same organization or company.

The electronic activity ingestor 205 can receive an electronic activity and can assign each electronic activity, an electronic activity unique identifier 502 to enable the node graph generation system 200 to uniquely identify each electronic activity. In some embodiments, the electronic activity unique identifier 502 can be the same identifier as a unique electronic activity identifier included in the electronic activity. In some embodiments, the unique electronic activity is included in the electronic activity by the source of the electronic activity or any other system.

The electronic activity ingestor 205 can be configured to format the electronic activity in a manner that allows the electronic activity to be parsed or processed. In some embodiments, the electronic activity ingestor 205 can identify one or more fields of the electronic activity and apply one or more normalization techniques to normalize the values included in the one or more fields. In some embodiments, the electronic activity ingestor 205 can format the values of the fields to allow content filters to apply one or more policies to identify one or more regex patterns for filtering the content, as described herein.

It should be appreciated that the electronic activity ingestor 205 can be configured to ingest electronic activities in a real-time or near real-time basis for accounts of one or more enterprises, organizations, companies, businesses, institutions or any other group associated with a plurality of electronic activity account with which the node graph generation system 200 has integrated. When an enterprise client subscribes to a service provided by the node graph generation system 200 , the enterprise client provides access to electronic activities maintained by the enterprise client by going through an onboarding process. That onboarding process allows the system 200 to access electronic activities owned or maintained by the enterprise client from one or more electronic activities sources. This can include the enterprise client's mail servers, one or more systems of record, one or more phone services or servers of the enterprise client, among other sources of electronic activity. The electronic activities ingested during an onboarding process may include electronic activities that were generated in the past, perhaps many years ago, that were stored on the electronic activities' sources. In addition, in some embodiments, the system 200 can be configured to ingest and re-ingest the same electronic activities from one or more electronic activities sources on a periodic basis, including daily, weekly, monthly, or any reasonable frequency.

The electronic activity ingestor 205 can be configured to receive access to each of the electronic activities from each of these sources of electronic activity including the systems of record of the enterprise client. The electronic activity ingestor 205 can establish one or more listeners, or other mechanisms to receive electronic activities as they are received by the sources of the electronic activities enabling real-time or near real-time integration.

As more and more data is ingested and processed as described herein, the node graph generated by the node graph generation system 200 can get richer and richer with more information. The additional information, as will be described herein, can be used to populate missing fields or add new values to existing fields, reinforce field values that have low confidence scores and further increase the confidence score of field values, adjust confidence scores of certain data points, and identify patterns or make deductions based on the values of various fields of node profiles of nodes included in the graph.

As more data is ingested, the node graph generation system 200 can use existing node graph data to predict missing or ambiguous values in electronic activities such that the more node profiles and data included in the node graph, the better the predictions of the node graph generation system 200 , thereby improving the processing of the ingested electronic activities and thereby improving the quality of each node profile of the node graph, which eventually will improve the quality of the overall node graph of the node graph generation system 200 .

The node graph generation system 200 can be configured to periodically regenerate or recalculate the node graph. The node graph generation system 200 can do so responsive to additional data being ingested by the system 200 . When new electronic activities or data is ingested by the node graph generation system 200 , the system 200 can be configured to recalculate the node graph as the confidence scores (as will be described later) can change based on the information included in the new electronic activities. In some embodiments, the ingestor may re-ingest previously ingested data from the one or more electronic activity sources or simply ingest the new electronic activity not previously ingested by the system 200 .

B. Electronic Activity Parsing

The electronic activity parser 210 can be any script, file, program, application, set of instructions, or computer-executable code, which is configured to enable a computing device on which the electronic activity parser 210 is executed to perform one or more functions of the electronic activity parser 210 described herein.

The electronic activity parser 210 can be configured to parse the electronic activity to identify one or more values of fields to be used in generating node profiles of one or more nodes and associate the electronic activities between nodes for use in determining the connection and connection strength between nodes. The node profiles can include fields having name-value pairs. The electronic activity parser 210 can be configured to parse the electronic activity to identify values for as many fields of the node profiles of the nodes with which the electronic activity is associated.

The electronic activity parser 210 can be configured to first identify each of the nodes associated with the electronic activity. In some embodiments, the electronic activity parser 210 can parse the metadata of the electronic activity to identify the nodes. The metadata of the electronic activity can include a To field, a From field, a Subject field, a Body field, a signature within the body and any other information included in the electronic activity header that can be used to identify one or more values of one or more fields of any node profile of nodes associated with the electronic activity. In some embodiments, non-email electronic activity can include meetings or phone calls. The metadata of such non-email electronic activity can include a duration of the meeting or call, one or more participants of the meeting or call, a location of the meeting, locations associated with the initiator and receiver of the phone call, in addition to other information that may be extracted from the metadata of such electronic activity. In some embodiments, nodes are associated with the electronic activity if the node is a sender of the electronic activity, a recipient of the electronic activity, a participant of the electronic node, or identified in the contents of the electronic activity. The node can be identified in the contents of the electronic activity or can be inferred based on information maintained by the node graph generation system 200 and based on the connections of the node and one or more of the sender or recipients of the electronic activity.

The electronic activity parser 210 can be configured to parse the electronic activity to identify attributes, values, or characteristics of the electronic activity. In some embodiments, the electronic activity parser 210 can apply natural language processing techniques to the electronic activity to identify regex patterns, words or phrases, or other types of content that may be used for sentiment analysis, filtering, tagging, classifying, deduplication, effort estimation, and other functions performed by the data processing system 200 .

In some embodiments, the electronic activity parser 210 can be configured to parse an electronic activity to identify values of fields or attributes of one or more nodes. For instance, when an electronic mail message is ingested into the node graph generation system 200 , the electronic activity parser 210 can identify a FROM field of the electronic mail message. The FROM field can include a name and an email address. The name can be in the form of a first name and a last name or a last name, first name. The parser can extract the name in the FROM field and the email address in the FROM field to determine whether a node is associated with the sender of the electronic mail message.

C. Signature Parsing

In some embodiments, the electronic activity parser 210 can be configured to identify a signature in a body of an electronic message. The parser 210 can identify the signature by utilizing a signature detection policy that includes logic for identifying patterns of signatures. In some embodiments, a signature can include one or more values of attributes, such as values for attributes including but not limited to a name, a phone number, a company name, a company division, a company address, a job title, one or more social network handles or links, an email address, among others. By parsing the signature, the electronic activity parser 210 can identify each of the values corresponding to the various fields of a node profile associated with the sender of the electronic activity. In addition to information included in the signature, the electronic activity parser can utilize information from the header of the electronic activity (i.e. first and last name) to identify where the signature is located by finding the same first name, last name and email address within a predetermined proximity or distance of each other in a region of the body, for instance, the bottom of the body. Stated in another way, the present disclosure describes methods and systems for utilizing header data of an electronic activity, which in certain embodiments, is verified to make it easier to locate a signature of an email, which may be buried under, around or with other textual content. In some embodiments, one or more of a first name, a last name and an email address extracted from the header of the electronic activity is used to identify text strings that match the extracted first name, last name and the email address. Responsive to determining that text strings matching the first name, last name and the email address are within a predetermined distance of one another, the parser 210 can identify the text strings are portions of the signature of the electronic activity. The information parsed from the signature can be used to determine a confidence score of a value of a field as further described herein with respect to the attribute value confidence scorer 235 . The electronic activity parser 210 can also use signature parsing for node selection and in the identification of the node, to which the activity, containing the signature can be associated.

D. Node Profiles

The node profile manager 220 can be any script, file, program, application, set of instructions, or computer-executable code that is configured to enable a computing device on which the node profile manager 220 is executed to perform one or more functions of the node profile manager 220 described herein. The node profile manager is configured to manage node profiles associated with each node. Node profiles of nodes are used to construct a node graph that includes nodes linked to one another based on relationships between the nodes that can be determined from electronic activities parsed and processed by the node graph generation system 200 as well as other information that may be received from one or more systems of record.

Referring now to FIG. 6A , FIG. 6A illustrates a representation of a node profile of a node. The node profile 600 can include a unique node profile identifier 602 and one or more fields or attributes 610 a - 610 n . Each attribute 610 can include one or more value data structures 615 . Each value data structure can include a value 620 , an occurrence metric 625 , a confidence score 630 and one or more entries 635 a - n . Each entry 635 can identify a data source 640 from which the value was identified (for instance, a source of a system of record or a source of an electronic activity), a number of occurrences of the value that appear in the electronic activity, a time 645 associated with the electronic activity (for instance, at which time the electronic activity occurred) and an electronic activity unique identifier 502 identifying the electronic activity. In some embodiments, the occurrence metric 625 can identify a number of times that value is confirmed or identified from electronic activities or systems of record. The node profile manager 220 can be configured to update the occurrence metric each time the value is confirmed. In some embodiments, the electronic activity can increase the occurrence metric of a value more than once. For instance, for a field such as name, the electronic activity parser can parse multiple portions of an electronic activity. In some embodiments, parsing multiple portions of the electronic activity can provide multiple confirmations of, for example, the name associated with the electronic activity.

The node profile manager 220 can be configured to maintain a node profile for each node that includes a time series of data points for every value data structure 615 that are generated based on electronic activities identifying the respective node. The node profile manager 220 can maintain, for each field of the node profile, one or more values data structures 615 . The node profile manager 220 can maintain a confidence score for each value of the field. As will be described herein the confidence score of the value can be determined using information relating to the electronic activities or systems of record that contribute to the value. The confidence score for each value can also be based on the below-described health score of the data source from which the value was received. Further, the node profile manager 220 can maintain an occurrence metric that identifies a number of times electronic activities or systems of record have contributed to the value. In some embodiments, the occurrence metric is equal to or greater than the number of electronic activities or systems of record that contribute to the value. The node profile manager 220 further maintains an array including the plurality of entries 635 . As more and more electronic activities and data from more systems of record are ingested by the node graph generation system 200 , values of each of the fields of node profiles of nodes will become more enriched thereby further refining the confidence score of each value.

In some embodiments, the node profile can include different types of fields for different types of nodes. Member nodes and group nodes may have some common fields but may also include different fields. Further, member nodes may include fields that get updated more frequently than group nodes. Examples of some fields of member nodes can include i) First name; ii) Last name; iii) Email; iv) job title; v) Phone; vi) Social media handle; vii) LinkedIn URL; viii) website; among others. Each of the fields can be a 3-dimensional array. In some embodiments, each field corresponds to one or more name value pairs, where each field is a name and each value for that field is a value. Examples of some fields of group nodes can include i) Company or Organization name; ii) Address of Company; iii) Phone; iv) Website; v) Social media handle; vi) LinkedIn handle; among others. Each of the fields can be a 3-dimensional array. In some embodiments, each field corresponds to one or more name value pairs, where each field is a name and each value for that field is a value.

The node profile manager 220 can maintain, for each field of each node profile, a field data structure that can be stored as a multidimensional array. The multidimensional array can include a dimension relating to data points that identify a number of electronic activities or system of records that contribute to the field or the value of the field. Another dimension can identify the source, which can have an associated trust score that can be used to determine how much weight to assign to the data point from that source. Another dimension can identify a time at which the data point was generated (for instance, in the case of a data point derived from an electronic activity such as an email, the time the data point was generated can be the time the electronic activity was sent or received). In the case of a data point being derived from a system of record, the time the data point was generated can be the time the data point can be entered into the system of record or the time the data point was last accessed, modified, confirmed, or otherwise validated in or by the system of record. These dimensions are all used to determine a confidence score of the value as will be described herein. In some embodiments, the node profile manager 220 can assign a contribution score to each data point. The contribution score can be indicative of the data point's contribution towards the confidence score of the value. The contribution score of a data point can decay over time as the data point becomes staler. The contribution scores of each of the data points derived from electronic activities and systems of record can be used to compute the confidence score of the value of a field of the node profile.

Referring now to FIG. 6B , FIG. 6B illustrates a representation of three electronic activities and a representation of three states of a node profile of a node according to embodiments of the present disclosure. As shown in FIG. 6B , three electronic activities sent at a first time, a second time and third time are shown. The first electronic activity 652 a includes or is associated with a first electronic activity identifier 654 a (“EA-003”). The second electronic activity 652 b includes or is associated with a second electronic activity identifier 654 b (“EA-017”). The third electronic activity 652 c includes or is associated with a third electronic activity identifier 654 b (“EA-098”). Collectively, the electronic activities can be referred to herein as electronic activities 652 or individually as electronic activity 652 . Each electronic activity can include corresponding metadata, as described above, a body, and a respective signature 660 a - c included in the body of the respective electronic activity 652 . As shown in FIG. 6B , each of the signatures 660 a - c is different from the others.

FIG. 6B also includes three different representations of a node profile corresponding to three different times. The node profile corresponds to a node profile of the sender of the electronic activities 652 as determined by the node profile manager 220 . The first representation 662 a of the node profile was updated after the first electronic activity 652 a was ingested by the node graph generation system 200 but before the second and third electronic activities 652 b and 652 c were ingested by the system 200 . The second representation 662 b of the node profile was updated after the first and second electronic activities 652 a and 652 b were ingested by the node graph generation system 200 but before the third electronic activity 652 c was ingested by the system 200 . The third representation 662 c of the node profile was updated after all three electronic activities 652 were ingested by the node graph generation system 200 .

Each of the representations 662 of the node profile can include fields and corresponding values. For example, in the first representation 662 a , the field “First Name” is associated with 2 different values, John and Johnathan. The first representation 662 a also includes the field “Title” which is associated with the value “Director.” In contrast, the second representation 662 b and 662 c both include an additional value “CEO” for the field “Title.” Furthermore, in the third representation 662 c , the field “Company Name” is associated with 2 different values, Acme and NewCo in contrast with the first two representations 662 a and 662 b of the node profile. The values of the last name and cell phone number remain the same in all three representations 662 of the node profile.

Each of the values included in the node profile can be supported by one or more data points. Data points can be pieces of information or evidence that can be used to support the existence of values of fields of node profiles. A data point can be an electronic activity, a record object of a system of record (as will be described herein), or other information that is accessible and processable by the system 200 . In some embodiments, a data point can identify an electronic activity, a record object of a system of record (as will be described herein), or other information that is accessible and processable by the system 200 that serves as a basis for supporting a value in a node profile. Each data point can be assigned its own unique identifier. Each data point can be associated with a source of the data point identifying an origin of the data point. The source of the data point can be a mail server, a system of record, among others. Each of these data points can also include a timestamp. The timestamp of a data point can identify when the data point was either generated (in the case of an electronic activity such as an email) or the record object that serves as a source of the data point was last updated (in the case when the data point is extracted from a system of record). Each data point can further be associated with a trust score of the source of the data point. The trust score of the source can be used to indicate how trustworthy or reliable the data point is. The data point can also be associated with a contribution score that can indicate how much the data point contributes towards a confidence score of the value associated with the data point. The contribution score can be based on the trust score of the source (which is based in part on a health score of the source) and a time at which the data point was generated or last updated.

A confidence score of the value can indicate a level of certainty that the value of the field is a current value of the field. The higher the confidence score, the more certain the value of the field is the current value. The confidence score can be based on the contribution scores of individual data points associated with the value. The confidence score of the value can also depend on the corresponding confidence scores of other values of the field, or the contribution scores of data points associated with other values of the field.

The table below illustrates various values for various fields and includes an array of data points that contribute to the respective value. As shown in the table, the same electronic activity can serve as different data points for different values. Further, the table illustrates a simplified form for the same of convenience and understanding.

Different values can be supported by different number of data points. The three electronic activities shown in FIG. 6B ( 652 a - c ) are included in the table below. Using the table and the representations 662 a - c of the node profile, one can understand how the system 200 is capable of determining values of fields of node profiles and changes to node profiles as more electronic activities and data points are processed by the system 200 .

The signature 660 b is different from the signature 660 a in that the title of the person John Smith has changed from Director to CEO. The data points supporting or contributing the value Director include the first electronic activity 652 a but not the second electronic activity 652 b . Also, the data points include information received from systems of records including data points that correspond to time periods after the value is no longer accurate. For instance, the data point DP ID 225 is a data point supporting the value “Director” for the node profile even though person has been promoted to CEO. The system 200 is configured to process and accept all data points but can assign different contribution scores based on the source of the data point and allow the system 200 to accurately maintain a state of the node profile even if some of the data that is received may be inaccurate or stale.

As will be described further below, it can be challenging to match electronic activities to node profiles. The system 200 can match the third electronic activity 652 c to the node profile 662 even though the electronic activity identified a different email address, a different company name, and a different office number. In some embodiments, the system 200 can determine, by parsing the electronic activity, information about the sender that can be used to identify the correct node profile. In this particular case, the system 200 can rely on the first name, last name, and cell phone number (which is generally unique) to map the electronic activity to the correct node profile 662 as opposed to other node profiles including the name John Smith. Table 1:

As a result of populating values of fields of node profiles using electronic activities, the node profile manager 220 can generate a node profile that is unobtrusively generated from electronic activities that traverse networks. In some embodiments, the node profile manager 220 can generate a node profile that is unobtrusively generated from electronic activities and systems of record.

As described herein, the present disclosure relates to methods and systems for assigning contribution scores to each data point (for example, electronic activity) that contributes to a value of a field such that the same electronic activity can assign different contribution scores to different values of a single node profile and of multiple node profiles. The contribution score can be based on a number of different electronic activities contributing to a given value of a field of a node profile, a recency of the electronic activity, among others. In some embodiments, a system of record of an enterprise accessible to the node graph generation system can include data that can also contribute to a value of a field of a node profile. The contribution score can be based on a trust score or health score of the system of record, a number of different electronic activities or systems of record contributing to the value of the field of the node profile, a number of different electronic activities or systems of record contributing to other values of the field of the node profile, a recency of the value being confirmed by the system of record, among others.

In some embodiments, a method of updating confidence scores of values of fields based on electronic activity includes associating the electronic activity to a first value of a first field, assigning a first contribution score to the first value, associating the electronic activity to a second value of a second field, assigning a second contribution score to the second value, and updating a confidence score of the first value and the second value based on the first contribution score and the second contribution score.

Furthermore, the present disclosure relates to methods and systems for maintaining trust scores for sources and adjusting a contribution score of a data point for one or more values of fields of node profiles based on the trust score of a source.

E. Matching Electronic Activity to Node Profiles

The node profile manager 220 can be configured to manage node profiles by matching electronic activities to one or more node profiles. Responsive to the electronic activity parser 210 parsing the electronic activity to identify values corresponding to one or more fields or attributes of node profiles, the node profile manager 220 can apply an electronic activity matching policy to match electronic activities to node profiles. In some embodiments, the node profile manager 220 can identify each of the identified values corresponding to a sender of the electronic activity to match the electronic activity to a node profile corresponding to the sender.

Using an email message as an example of an electronic activity, the node profile manager 220 may first determine if the parsed values of one or more fields corresponding to the sender of the email message match corresponding values of fields. In some embodiments, the node profile manager 220 may assign different weights to different fields based on a uniqueness of values of the field. For instance, email addresses may be assigned greater weights than first names or last names or phone numbers if the phone number corresponds to a company.

In some embodiments, the node profile manager 220 can use data from the electronic activity and one or more values of fields of candidate node profiles to determine whether or not to match the electronic activity to one or more of the candidate node profiles. The node profile manager 220 can attempt to match electronic activities to one or more node profiles maintained by the node profile manager 220 based on the one or more values of the node profiles. The node profile manager 220 can identify data, such as strings or values from a given electronic activity and match the strings or values to corresponding values of the node profiles. In some embodiments, the node profile manager 220 can compute a match score between the electronic activity and a candidate node profile by comparing the strings or values of the electronic activity match corresponding values of the candidate node profile. The match score can be based on a number of fields of the node profile including a value that matches a value or string in the electronic activity. The match score can also be based on different weights applied to different fields. The weights may be based on the uniqueness of values of the field, as mentioned above. The node profile manager 220 can be configured to match the electronic activity to the node with the greatest match score. In some embodiments, the node profile manager can match the electronic activity to each candidate node that has a match score that exceeds a predetermined threshold. Further, the node profile manager 220 can maintain a match score for each electronic activity to that particular node profile, or to each value of the node profile to which the electronic activity matched. By doing so, the node profile manager 220 can use the match score to determine how much weight to assign to that particular electronic activity. Stated in another way, the better the match between the electronic activity and a node profile, the greater the influence the electronic activity can have on the values (for instance, the contribution scores of the data point on the value and as a result, in the confidence scores of the values) of the node profile. In some embodiments, the node profile manager 220 can assign a first weight to electronic activities that have a first match score and assign a second weight to electronic activities that have a second match score. The first weight may be greater than the second weight if the first match score is greater than the second match score. In some embodiments, if no nodes are found to match the electronic activity or the match score between the email message and any of the candidate node profiles is below a threshold, the node profile manager 220 can be configured to generate a new node profile to which the node profile manager assigns a unique node identifier 602 . The node profile manager 220 can then populate various fields of the new node profile from the information extracted from the electronic activity parser 210 after the parser 210 parses the electronic activity.

In addition to matching the electronic activity to a sender node, the node profile manager is configured to identify each of the nodes to which the electronic activity can be matched. For instance, the electronic activity can be matched to one or more recipient nodes using a similar technique except that the node profile manager 220 is configured to look at values extracted from the TO field or any other field that can include information regarding the recipient of the node. In some embodiments, the electronic activity parser can be configured to parse a name in the salutation portion of the body of the email to identify a value of a name corresponding to a recipient node. In some embodiments, the node profile manager 220 can also match the electronic activity to both member nodes as well as the group nodes to which the member nodes are identified as members.

In some embodiments, the electronic activity parser 210 can parse the body of the electronic activity to identify additional information that can be used to populate values of one or more node profiles. The body can include one or more phone numbers, addresses, or other information that may be used to update values of fields, such as a phone number field or an address field. Further, if the contents of the electronic activity includes a name of a person different from the sender or recipient, the electronic activity parser 210 can further identify one or more node profiles matching the name to predict a relationship between the sender and/or recipient of the electronic activity and a node profile matching the name included in the body of the electronic activity.

The node profile manager 220 can be configured to maintain a node profile data structure that maintains separate values for the same field. For instance, the electronic message can be destined to john.smith@example.com <Johnathan Smith> and the body of the email states “Dear Johnathan”. The parser can be configured to identify a first name, a last name and an email address for the recipient applying logic to specific portions of the electronic activity. In certain embodiments, the node profile manager 220 can be configured to run statistical analysis of all nodes and determine that John is a very common name and thus identify that this node not only has Johnathan as first name but also John is the other First Name value. Moreover, the node profile manager 220 can be configured to determine if a value of a field is unique enough to match the electronic activity to the node based on the value of the field. If the value of the field does not meet a predetermined threshold, other values of fields may be used to match the electronic activity to a given node. In addition, values of fields may be prioritized for matching the electronic activity to the node. For instance, the name John is relatively common and as such, attempting to match an electronic activity to a node using the value “John” for the field “First Name” may be less dispositive than matching a more unique value, such as an email address. In some embodiments, the node profile manager 220 can weigh fields that have values that are relatively more unique higher than fields that have values that are relatively less unique when matching an electronic activity to a node. In some embodiments, the node profile manager 220 can be configured to restrict matching electronic activities to nodes using values of fields that are determined to not be sufficiently unique.

The node profile manager 220 can be configured to identify a node that has fields having values that match the values included in the node profile of the node. To do so, the node profile manager may determine that john.smith@example.com belongs to only one node. The node profile manager can then select that node to be the recipient of the email message. The node profile manager would then populate each of the fields of the node profile with an entry for each value of each respective field that was identified by the electronic activity parser 210 . In particular, the node profile manager can generate, for each value of a field that is identified by the electronic activity parser 210 , an entry in that value data structure that identifies the electronic activity, a source of the electronic activity, a time associated with the electronic activity and a number of occurrences within the electronic activity that include the value. In the email message described above, the node profile manager can update the value data structure of the Name field of the recipient node with an entry that identifies the source of the email, the time associated with the email and a total number of occurrences of the value in the email. In this case, the total number of occurrences was 2 because the first name of the recipient was listed as Johnathan and the salutation identified the name Johnathan.

Referring briefly to FIG. 7 , FIG. 7 illustrates a series of electronic activities between two nodes, N 1 702 and N 2 704 . N 1 702 may correspond to a node associated with an entity whose electronic activities are ingested by the node graph generation system 200 , while node N 2 704 may correspond to a node external to the entity associated with the node N 1 . A node profile 715 for node N 2 is maintained by the node profile manager 220 . Before the electronic activity 710 was ingested by the node graph generation system 200 , the node profile included the five fields, name, email, phone, company and job title. This information was previously included in the node profile and may have been determined by ingesting information from a system of record. At that time, the confidence score of each of the fields is 1. When the first electronic activity is ingested by the system 200 , the node profile manager can update the node profile 715 and increase the confidence score of values of fields that can be verified by the electronic activity. By virtue of the electronic activity being successfully transmitted from N 1 to N 2 , the node profile manager 220 can update the confidence score of the email value j@acme.com and the company name Acme by parsing the email address and determining that the domain name of the email matches a domain name of the company node, to which N 2 belongs. In some embodiments, the node profile manager 220 may determine that the electronic activity is successfully transmitted by determining that the N 1 did not receive a bounce back electronic activity that indicates that the electronic activity was not successfully transmitted. Examples of bounce back electronic activity can include emails indicating that the destination email address is invalid or incorrect, the person is no longer with company, among others.

In some embodiments, the node graph generation system 200 can, via the electronic activity parser or through some other module, parse bounce back electronic activities to determine a reason for why the electronic activity bounced back. In some embodiments, the node graph generation system 200 can use natural language processing to determine a cause for the bounce back activity. In this way, the node graph generation system 200 can determine if an email address associated with a person or node is still valid or if it is incorrect or if the person is no longer associated with the company identified by the domain of the email address.

Node N 2 can then send back a response email to node N 1 that includes a signature 726 in the body of the electronic activity. The node profile manager can update, from the successful transmission of the email response and the parsing of the signature, the node profile of N 2 by increasing the confidence score of the name of John Smith, the title from the signature, the company name 2 times (one of which was derived by matching the domain name of the email to the domain name of the group node in the node graph) as it is included in the email address and in the signature, and further add a new value for the phone number, which is extracted from the signature. The extracted phone number can represent his direct office number, while the phone number previously maintained in the node profile can be a general company number. In some embodiments, the system can be configured to classify phone numbers as a general company number or a direct office number based on the frequency of the number appearing in different node profiles. In some embodiments, the node graph generation system 200 can be configured to classify phone numbers as a general company number or a direct office number by performing regex patterns to determine if an “ext.” or an “x” followed by some numbers is included in the value. The regex can also be configured to identify phone number prefixes, such as “800.” The system can identify the phone numbers as the publicly known phone number of the company. In some embodiments, the node graph generation system 200 can be configured to restrict or otherwise prevent a phone number determined to be a general company number from being inserted as a value of a personal number. In some embodiments, the node graph generation system 200 can be configured to determine the value of phone numbers of other nodes corresponding to the same company and if the system determines that the number to be added to a node matches the number of multiple other nodes belonging to the same entity or company, the system can probabilistically determine, for instance, that the number is a work number and update the number as a value in the work number field (instead of a personal number field). Similar techniques can be applied for determining or inferring other information by comparing the data of a node profile to patterns observed from a plurality of related node profiles. In some embodiments, the system can determine whether the first predetermined digits (for instance, the first 6 digits) are identical to the first predetermined digits of phone numbers of other nodes belonging to the same company. If the first predetermined digits of the number match the first predetermined digits of phone numbers of other nodes belonging to the same company, the system can determine that the number is a work number. Similarly, an address extracted from a signature can be determined to be a work address if the address matches the address of other nodes belonging to the same entity or company. In this way, any value of a field of a node extracted can be determined to be specific to a company if other nodes corresponding to people belonging to the company also include the same value for the field or inter-related values in other fields. Additional details regarding increasing or adjusting the confidence score of various values of fields of node profiles based on occurrences of electronic activities are provided herein.

Generally, the node profile manager 220 can attempt to match electronic activities, such as emails, to node profiles based on an email address. However, in some instances, a user may send or receive an email address from a second email address, such as a personal email address instead of a work email address. The node profile manager 220 can analyze the electronic activity and look at other signals from the electronic activity to see if the electronic activity should be matched to a previously established node profile that corresponds to the user that does not include the second email address instead of a creating a new node profile based on the second email address.

For instance, the node profile manager 220 can be configured to identify an email that includes an email address john.smith@gmail.com. The node profile manager 220 can determine that either no node profile includes the john.smith@gmail.com as a value of an email address field or even if the email appears as a value in the email address field of a node profile, the confidence score of the value of the email address is below a certain threshold sufficient for the node profile manager 220 . In some embodiments, the node profile manager 220 can apply one or more policies or rules for generating new nodes. For instance, the node profile manager 220 can implement an email address based node profile generation policy in which the system is configured to not create new node profiles if the email address corresponds to an email address of one or more predefined email systems. For instance, the email address based node profile generation policy can include one or more rules for generating new node profiles or restricting the generation of new node profiles. In some embodiments, the node profile generation policy can restrict the creation or generation of new node profiles if the email address corresponds to an email address of one or more predefined email systems. For instance, the predefined email systems can include email systems that provide “free” email addresses like “gmail.com” or “yahoo.com”. In such cases, the node profile manager 220 can be configured to use other signals from the electronic activity to attempt to match the electronic activity to a node profile for which the email address did not provide a match to a node profile. The node profile manager 220 can use fuzzy matching techniques including a first name, last name, email address prefix, a phone number or any other information that can be extracted from the email address to match the electronic activity to an existing node profile. In some embodiments, the node profile manager 220 can also identify other node profiles to which the electronic activity can be matched and identify likely node profiles based on connection strengths between the node profiles to which the electronic activity can be matched and the one or more likely node profiles.

As discussed above, in the case that John Smith inadvertently sent an email from his gmail address as opposed to his company email address, john.smith@example.com, the node profile manager 220 can use one or more of the first name, last name, phone number or other information included in the signature of the email to match the electronic activity to a node profile that includes the email address, john.smith@example.com. In this way, if other signals are pointing or expecting a work email address, the electronic activity will be matched to the node profile with the work email address.

F. Node Profile Value Prediction and Augmentation

The node profile manager 220 can be configured to augment node profiles with additional information that can be extracted from electronic activities or systems of record or that can be inferred based on other similar electronic activities or systems of record. In some embodiments, the node profile manager 220 can determine a pattern for various fields across a group of member nodes (such as employees of the same company). For instance, the node profile manager 220 can determine, based on multiple node profiles of member nodes belonging to a group node, that employees of a given company are assigned email addresses following a given regex pattern. For instance, [first name].[last name]@[company domain].com. As such, the node profile manager 220 can be configured to predict or augment a value of a field of a node profile of an employee of a given company when only certain information of the employee is known by the node profile manager 220 .

As shown in the table above, the node profile manager 220 can be configured to determine that the email address for Adam Jones is adam.jones@example.com by observing a regex pattern the company Example uses when assigning email addresses to its employees. In some embodiments, the node profile manager 220 can update the email address field of Adam Jones accordingly. In some embodiments, the node profile manager 220 can be configured to transmit an email to adam.jones@example.com to check whether the email address is valid or if a bounce back email is received. If no bounce back email is received indicating that the email address is not valid or cannot be found, the confidence score of adam.jones@example.com can increase even though the email address was unknown to the node graph generation system 200 based on the electronic activities ingested by the system 200 .

Similarly, the node profile manager 220 can infer the first and last names of people having email addresses corresponding to a company by parsing information using the known regex patterns. As shown above, the node profile manager 220 can predict that the name of the person associated with the email address linda.chan@example.com is Linda Chan based on the regex pattern observed from other known node profiles maintained by the node profile manager 220 . In some embodiments, the node profile manager 220 can infer the first and last names of people having email addresses corresponding to a company by also using other data points in the electronic activity, such as parsing email header metadata, email signature, or a greeting at the top of the email body to correlate with and confirm the name, predicted from the regex pattern above. As previously described with respect to the description associated with Table 1, the system can rely on multiple data points to match an electronic activity to a particular node profile (for instance, relying in part on the cell phone number included in the signature as discussed with respect to Table 1). In this way, further confirmation of the inference of the first name and/or last name can be obtained, thereby improving the accuracy of the node profile and the overall node graph. It should further be appreciated that if multiple people have the same name or initials, the company may assign alternate email address naming conventions for such people. For instance, a company may include a middle initial in the email address for person if the email address generated using the company's primary regex pattern for assigning email addresses is already taken. In such cases, the node profile manager 220 may again further rely on other data points in the electronic activity, such as parsing email header metadata, email signature, or a greeting at the top of the email body to infer the first and last names of the person.

In this way, by knowing the regex patterns of email addresses assigned by a company, the node profile manager 220 can be configured to predict email addresses of people at the company for which we have some information. Furthermore, if an email address is known, we can predict other information not otherwise known based on the email address. In some embodiments, even if some information is known, the confidence score of that information can be updated based on the node profile manager 220 being configured to predict certain values.

In some embodiments, the node profile manager 220 can be configured to maintain both work and personal phone numbers and work and personal geographical locations of node profiles. The node profile manager 220 can be configured to determine if a phone number extracted from an electronic activity is a work phone number or a personal phone number through one or more verification techniques. In some embodiments, the node profile manager 220 can be configured to compare the phone number of a node with phone numbers of other nodes belonging to the same company or branch/office. Corporations generally will assign phone numbers to employees that are similar to one another, for instance, all the numbers of the corporation can be 617-550-XXXX. As such, the node profile manager 220 can categorize a phone number as a work number for a node if the phone number starts with 617 550 when at least a threshold number of nodes belonging to the same email domain @example.com also have the phone number beginning with 617-550. In some embodiments, the threshold number can be 2, 3, 4, 5, or more. In some embodiments, the threshold number can be based on a percentage of another value, such as a total number of nodes belonging to the same domain and also having the phone number beginning with the same subset of digits. Conversely, the node profile manager 220 can be configured to categorize a phone number as a personal number if the phone number starts with a different set of numbers. It should be appreciated that more broadly, the node profile manager 220 can be configured to extract a regex pattern or specific template of numbers by comparing the phone numbers of multiple node profiles corresponding to the same corporation.

In some embodiments, the node profile manager 220 can be configured to compare a location of a person with an area code of a phone number associated with the person to determine if a phone number is to be classified as a work phone number or a personal phone number. If the person lives in the same area as the company's office, the person's personal phone number can have similar first few digits as the company's general phone number. In some such embodiments, the node profile manager 220 can be configured to negate the similar digits between the person's phone number and the company's assigned phone numbers to determine if the number identified in the node profile or to be included in the node profile is to be classified as a work phone number or a personal phone number. If the person lives in an area that is further away from the company based on existing information in the node profile, the node profile manager 220 can be configured to classify a number similar to the company's general phone number or having an area code corresponding to an area where the company is located as a work phone number. If the person lives in an area close to the company, the node profile manager 220 can be configured to identify the digits of the phone number that match the company's general phone number and use the remaining digits to determine if the number corresponds to a work phone number or a personal phone number of the person.

If the person lives far away from their work address, the node profile manager 220 can be configured to reduce the likelihood of assigning, as a personal phone number, a phone number that has an area code corresponding to the person's work address. More generally, the node profile manager 220 can be configured to rely on additional fields to determine if a particular number belongs to a work phone number or a personal phone number of the person.

As described herein, the node profile manager 220 can be configured to used information from node profiles to predict other values. In particular, there is significant interplay between dependent fields such as phone numbers and addresses, and titles and companies, in addition to email addresses and names, among others.

G. Electronic Activity Tagging

The tagging engine 265 can be any script, file, program, application, set of instructions, or computer-executable code that is configured to enable a computing device on which the tagging engine 265 is executed to perform one or more functions of the tagging engine 265 described herein.

The tagging engine 265 can use information identified, generated or otherwise made available by the electronic activity parser 210 . The tagging engine can be configured to assign tags to electronic activities, node profiles, systems of record, among others. By having tags assigned to electronic activities, node profiles, records ingested from one or more systems of record, among others, the node graph generation system 200 can be configured to better utilize the electronic activities to more accurately identify nodes, and determine types and strengths of connections between nodes, among others. In some embodiments, the tagging engine 265 can be configured to assign a confidence score to one or more tags assigned by the tagging engine. The tagging engine 265 can periodically update a confidence score as additional electronic activities are ingested, re-ingested and analyzed. Additional details about some of the types of tags are provided herein.

The tagging engine 265 can assign one or more tags to electronic activities. The tagging engine 265 can determine, for each electronic activity, a type of electronic activity. Types of electronic activities can include meetings, electronic messages, and phone calls. For meetings and electronic messages such as emails, the tagging engine 265 can further determine if the meeting or electronic message is internal or external and can assign an internal tag to meetings or emails identified as internal or an external tag to meetings and emails identified as external. Internal meetings or emails may be identified as internal if each of the participants or parties included in the meeting or emails belong to the same company as the sender of the email or host of the meeting. The tagging engine 265 can determine this by parsing the email addresses of the participants and determining that the domain of the email addresses map to the domain name or an array of domain names, belonging to the same company or entity. In some embodiments, the tagging engine 265 can determine if the electronic activity is internal by parsing the email addresses of the participants and determining that the domain of the email addresses map to the same company or entity after removing common (and sometimes free) mail service domains, such as gmail.com and yahoo.com, among others. The tagging engine 265 may apply some additional logic to determine if all emails belong to the same entity and use additional rules for determining if an electronic activity is determined to be internal or external. The tagging engine 265 can also identify each of the participants and determine whether a respective node profile of each of the participants is linked to the same organization. In some embodiments, the tagging engine 265 can determine if the node profiles of the participants are linked to a common group node (such as the organization's node) to determine if the electronic activity is internal. For phone calls, the tagging engine 265 may determine the parties to which the phone numbers are either assigned and determine if the parties belong to the same entity or different entities.

In some embodiments, the node graph generation system 200 can be configured to generate, maintain an update an array of domain names that belong to the same company or entity. The node graph generation system 200 may do so by monitoring electronic activities and predicting whether certain domain names belong to the same entity. The node graph generation system 200 can monitor a large number of electronic activities of an entity and determine multiple email accounts of a first domain communicate with multiple email accounts of a second domain in a manner that appears to be internal communications. In some embodiments, the node graph generation system 200 can automatically identify all possible domain names of the company based on a frequency of communications that look like internal communications between identified members of a company name, the fact that in multiple systems of record majority of the communicating node profiles belong to the same or related company profile, or by a similarity of the ending part of domain names, for example “us.ibm.com” and “uk.ibm.com”. Electronic activities can appear to be internal communications based on analyzing the words used in emails, the meeting numbers used in meeting and calendar invites, as well as determining if the email addresses match certain regex rules that may indicate that the domain names belong to the same company. For instance, electronic activities include email addresses having domain names us.example.com and uk.example.com may increase a likelihood that both us.example.com and uk.example.com appear to belong to the same company, Example. In some embodiments, if there a certain number of emails from certain users of us.example.com to other users of uk.example.com and the emails appear to be internal communications, the node graph generation system 200 or the node profile manager 220 can be configured to update the node profile of the company, Example, to include both domain names, us.example.com and uk.example.com. It should be appreciated that the node graph generation system 200 can then automatically update other node profiles and tags previously assigned to electronic activities responsive to determining that two domains belong to the same company. It should further be appreciated that the node graph generation system 200 can also automatically update confidence scores of certain values of fields of other node profiles and confidence scores of tags previously assigned to electronic activities responsive to determining that two domains belong to the same company.

In some embodiments, the tagging engine 265 can assign an internal tag or external tag to an electronic activity by applying certain logic. For instance, the tagging engine can determine that the electronic activity is internal if all the domains associated with the electronic activity are internal (or belong to the same domain). In some embodiments, if the tagging engine 265 determines that only some of the domains are internal and one or more domains are personal (i.e. not business external), then the tagging engine can be configured to attempt to match the personal email addresses to nodes and see if those nodes are linked to the same company. If the tagging engine fails to match the personal email addresses to nodes and see if those nodes are linked to the same company, the tagging engine can be configured to tag the electronic activity as external and may not link the electronic activity to a group node belonging to the domain. In some embodiments, if the tagging engine 265 determines that some domains of the email addresses included in the electronic activity are internal and some are business external, the tagging engine 265 can be configured to link the electronic activity to the group node corresponding to the external company, and further determine if individual nodes matching the email address (or first and last names) exist, and if so, linking the electronic activity with the respective individual nodes. In the event that the tagging engine 265 cannot identify an individual node that matches the email address or first and last names, the system 200 can create new individual nodes based on the respective email address or first and last names that were used to unsuccessfully identify the individual node. In the event that no individual (people) or group (company) nodes match, and the domain corresponding to the electronic activity doesn't belong to the list of free/public domains like @gmail then the system 200 can be configured to automatically create a new group (company) node or generate a flag or notification for an administrator to take an action.

The tagging engine 265 can further assign a sent tag to emails that are sent by a node associated with the data source provider from which the electronic activity was received or a received tag to emails that are received by a node associated with the data source provider from which the electronic activity was received.

In addition, the tagging engine can be configured to assign an inbound tag to received electronic activities corresponding to meeting invitations and assign an outbound tag to electronic activities corresponding to meeting invitations transmitted to other people. Moreover, meetings can be tagged with additional tags, such as a “future” tag when a meeting is scheduled for a time in the future. The “future” tag is subsequently replaced with a “past” tag once the time at which the meeting is scheduled to occur is in the past. Moreover, the tagging engine 265 can further assign tags indicating if the meeting took place or not based on other signals, such as electronic activities exchanged within a predetermined time frame of the scheduled meeting time as described herein or containing written confirmations that the meeting took place or not, such as follow-up notes between participants or cancellation notice emails. For electronic activities identified as meetings, the tagging engine 265 can further assign a tag identifying if the meeting is in person or if the meeting is a conference call. In some embodiments, the tagging engine 265 can employ a meeting type policy to determine the type of meeting. In some embodiments, the policy can include rules for parsing the location portion or body of a meeting to determine the location. If the location identifies a physical address or a room or if one of the participants included in the email is a non-human participant associated with a meeting room or other type of rooms, the tagging engine 265 can determine that the electronic activity is an in-person meeting and can assign an in-person meeting tag indicating that the meeting is an in-person meeting. In some embodiments, an in-person tag can be assigned to the electronic activity and a confidence score can be determined for the in-person tag that is assigned.

The confidence score associated with the in-person tag can be indicative of a likelihood that the meeting is actually an in-person meeting. The tagging engine 265 can further be configured to assign an occurrence tag that can be used to indicate a likelihood that the meeting occurred. The tagging engine 265 can further be configured to assign a respective participant attendance tag for each participant that attended the meeting.

To determine the confidence score associated with the in-person tag, the node graph generation system 200 can scan or analyze electronic activities associated with the participants of the meeting (and in some embodiments, the electronic activities of all users of the system 200 ) to identify receipts or other electronic activity, communications, among others indicative of the user physically going to the meeting. In some embodiments, the system 200 can scan electronic activities to find flight information, transportation receipts, and ride-sharing receipts, which may include information that would indicate the user physically going to the location associated with the meeting. For instance, if the meeting is at 100 Main St, San Francisco, Calif. on a certain date, electronic activities from an airline identifying a local airport may be used to increase the confidence score of the in-person tag. Similarly, even a flight cancellation receipt may increase the confidence score of the in-person tag. This is because even though the person may not have attended the meeting, the proof that a flight was reserved indicates that the meeting was intended to be an in-person meeting. The occurrence tag, which indicates whether the meeting actually occurred, can have its own confidence score. The greater the confidence score of the occurrence tag, the more likely the meeting occurred. As such, a flight confirmation email may increase the confidence score of the occurrence tag, while a flight cancellation email may conversely, decrease the confidence score of the occurrence tag. If multiple participants receive flight cancellation emails, the system may decrease the confidence score of the occurrence tag as it may be indicative of the meeting being canceled. However, if multiple participants received flight reservation emails and only a subset of the participants received flight cancellation emails, the system may not decrease the confidence score of the occurrence tag by the same amount as the system may assume that the meeting is still occurring but only the subset of participants are not attending. In such cases, the system may decrease the confidence score of the participant attendance tag for those participants that received flight cancellation emails. Moreover, the system can detect and parse an electronic receipt from a ride sharing service identifying one of the addresses as or near the meeting location (for example, 100 Main St, San Francisco, Calif.) and use the electronic activity to further increase the confidence score of the in-person meeting tag as well as the occurrence tag and the participant attendance tag.

On the other hand, the tagging engine 265 can determine that the meeting is a conference call by applying the meeting type policy and determining if a phone number or dial-in instructions are provided in the electronic activity. Furthermore, the tagging engine 265 may receive information from other engines or modules of the system to determine if participants are in close proximity to one another, based on time zone and location estimation algorithms used to predict a location of a node as well as determine or predict the locations of the participants based on electronic activities that occur within a predetermined time window of the meeting time that involve the participants. Some of the rules rely on determining a predicted work schedule of the node, a predicted location of the node, and inferred behavior before and after the meeting that can be determined from other electronic activities.

In some embodiments, the tagging engine 265 or the system 200 can be configured to cause the system 200 to initiate a call to a phone number included in a meeting invite and responsive to joining the meeting, identify one or more participants of the meeting for instance, based on identifying the phone number from which each of the participants is calling in and comparing those phone numbers to the data in the node graph or node profiles used to generate the node graph, converting speech to text, voice recognition, voice footprinting, among others. In some embodiments, the tagging engine can determine the participants who attended the meeting based on the attendees that accessed a link to a web session and in some such embodiments, used their email address to log into the web session. In some embodiments, the tagging engine 265 can determine what time a participant joined, a level of contribution of the participant during the meeting, how long the participant attended the meeting for, and generate one or more additional tags based on one or more of the participants' involvement.

As described above with respect to in-person meetings, the tagging engine 265 can also provide occurrence tags for conference call or virtual meetings as well as attendance tags for participants of such meetings. The occurrence tags can have respective confidence scores indicating the likelihood that the meeting actually occurred. Similarly, the participant attendance tags can be assigned to participants and can have respective confidence scores indicating the likelihood that the participant actually attended the meeting. The confidence scores of the occurrence tags and the attendance tags can be determined based on electronic activities that reference the meeting. In some embodiments, an electronic activity representing a phone log of a user's phone dialing into to a meeting number can be used to increase the confidence score of the occurrence tag of the meeting as well as the confidence score of the attendance tag.

The tagging engine 265 can further be configured to assign tags to people identified or included in one or more electronic activities. These tags can identify a role of the person included in the electronic activity. The tags can include a sender tag indicating a participant as a sender of the electronic activity or an organizer tag indicating a participant as an organizer of a meeting. Other similar types of tags can be assigned to participants based on whether they are included in the To line, the CC line or the BCC line. The tagging engine 265 can further be configured to tag participants based on the context of the electronic activity. For instance, if the electronic activity is determined to be associated with an opportunity, the tagging engine can assign tags to various participants, including tags indicating who the buyer is, who the seller is, who the decision maker is, who the champion is, among others. This information can be determined based on node profiles of the participants, their level of involvement in the electronic activity or the opportunity in general, among others. The tags can be assigned with certain confidence scores. As additional electronic activities are processed, the confidence scores of these tags can increase or decrease.

In some embodiments, natural language processing can be used to parse electronic activities exchanged between the participants to determine the type of meeting. For instance, an electronic activity exchanged after the meeting may indicate a phrase such as “Thanks for the lunch” which may indicate that the meeting was an in-person meeting, among others. In some embodiments, the tagging engine 265 can further tag electronic activities, such as meetings, with tags indicating if the meeting actually took place. As described above, the tagging engine 265 can tag a meeting as having taken place responsive to identifying a subsequent electronic message that included a phrase such as “Thanks for the lunch.” In some embodiments, the tagging engine can determine that the meeting is an in-person meeting by detecting an address or physical location in the body or location fields of the electronic activity. The tagging engine can further attribute a confidence score to the tag based on various data points the tagging engine relies on to determine that the electronic activity corresponds to an in-person meeting. The confidence score of the tag can increase or decrease based on additional electronic activity parsed by the system. For instance, electronic activity exchanged between the participants that may include various phrases that are detected via natural language processing, for instance, “great seeing you,” or “thanks for lunch” can increase the confidence score of the in-person tag indicating that the meeting is an in-person meeting. In addition, the electronic activity exchanged between the participants can increase the confidence score of the participant attendance tags of the sender and recipient of the email. Similarly, electronic activities including receipts of transportation (for instance, uber/lyft/flight receipts) to or from the physical location associated with the meeting may be used to increase the confidence score of the in-person tag assigned to the meeting, the occurrence tag assigned to the meeting and the participant attendance tag assigned to respective participants of the meeting. Additional details regarding tagging electronic activity are provided herein.

The tagging engine 265 can further assign tags indicating if an email is a blast email. In some embodiments, the tagging engine 265 can determine if an email is a blast email by parsing the message header of the email, identifying a message identifier field of the email and extracting the value of the message identifier field. The tagging engine can then compare the value of the message identifier field and compare the value to values of other electronic activities to determine if the values partially match. Furthermore, the tagging engine 265 can compare the words included in the body or subject line of the electronic activities that at least partially match and if the ratio of similar words to different words exceeds a threshold, the tagging engine 265 can determine if the email is a blast email. In some embodiments, the tagging engine 265 can determine electronic activities corresponding to a blast email by analyzing multiple electronic activities and identifying a subset of the multiple electronic activities as blast emails responsive to determining that each electronic activity of the subset has a low variability of word count relative to the other electronic activities in the subset and a low variability in a language complexity index relative to the other electronic activities in the subset.

In some embodiments, other signals may be used to determine if the email is a blast email, for instance, a time at which the emails were sent, and if a similar email was previously sent to a large number of people. In some embodiments, the tagging engine 265 can assign a blast email tag to an instant electronic activity responsive to determining that a similar electronic activity that is similar to the instant electronic activity above a predetermined similarity threshold was associated to a large number of nodes in a node storage database maintained by the system 200 . In certain embodiments, the tagging engine 265 can learn from previously tagged electronic activities known to be blast emails and use the learnings from such electronic activities to assign a tag to an instant email having language that is similar above a predetermined similarity threshold to one or more electronic activities previously tagged as blast emails. By determining if an email is a blast email, effort estimation can be more accurately computed.

The tagging engine 265 can further assign tags indicating if an email is a cold email. In some embodiments, the tagging engine 265 can determine if an email is a cold email by applying natural language processing to identify patterns or signals that may indicate that the email is a cold email or by determining a tone of an email. In some embodiments, the tagging engine 265 may determine that an email is a cold email if the participants of the email have not exchanged any electronic activity in the past. In some embodiments, the tagging engine 265 may determine that an email sent from a sender to a recipient is a cold email if the recipient of the email has not previously transmitted a response to any electronic activity sent from the sender to the recipient in the past. In some embodiments, even if the recipient of the email has not previously transmitted a response to any electronic activity sent from the sender to the recipient in the past the tagging engine 265 may determine that an email sent from a sender to a recipient is not a cold email if the recipient and the sender have communicated via other forms of communication or via other email addresses associated with a respective node of the sender or recipient in the past. In this way, if the recipient starts a new job and gets a new email address, electronic activities sent to the new email address by a sender who has previously communicated with the recipient at the old job would not be classified or tagged as a cold emails because the node graph would indicate that the sender has communicated with the recipient in the past albeit via a different email address of the recipient that is determined based on the values of email addresses stored in a node profile of the recipient. In some embodiments, the tagging engine 265 can determine if an email is a cold email based on a number of cold emails the sender has sent in the past to one or more recipients as well as by looking at the node graph to determine a number of nodes with which the sender and recipient are commonly connected.

The tagging engine 265 can further assign tags indicating a classification of the electronic activity based on the participants included in the electronic activity. For instance, if one of the participants is a lawyer, the tagging engine 265 can assign a tag indicating that the electronic activity relates to legal. Moreover, the tagging engine 265 can further assign tags indicating a classification of the electronic activity based on the subject matter included in the electronic activity. The tagging engine 265 can determine a subject matter based on natural language processing, keywords, regex patterns or other rules that may be used to determine the subject matter. In some embodiments, filtering policies that may be provided or configured by users, companies, accounts, among others, may be used by the tagging engine 265 to assign one or more tags. Such tags can be used for filtering, matching electronic activities to record objects of systems of record, determining if emails are personal or business related, among others.

In some embodiments, the tagging engine 265 can be configured to determine if an electronic activity is a personal electronic activity or if it is a business related electronic activity. In some embodiments, the tagging engine 265 can determine that an electronic activity is personal based on parsing the contents of the electronic activity. In some embodiments, the tagging engine 265 can determine that the electronic activity is personal if the electronic activity is sent during non-work hours and the context of the electronic activity is unrelated to work. In some embodiments, the tagging engine 265 can determine that the electronic activity is personal if the participants of the electronic activity have titles or job functions that typically do not overlap or correspond to companies that do not generally engage in work related activities. In some embodiments, the tagging engine 265 can also evaluate various features, characteristics or values of fields of node profiles of the participants of the electronic activity to determine whether the electronic activity is personal. For instance, the tagging engine 265 may determine that the electronic activity is likely to be personal if the participants of the electronic activity have the same last name, as derived from the header of the electronic activity, the body or contents of the electronic activity, a signature included in the electronic activity or from the node profiles of the participants of the electronic activity. It should be appreciated that the tagging engine 265 may not need to rely on information stored in a node profile of a participant of the electronic activity to determine if the electronic activity is personal. For example, the tagging engine 265 can determine if the participants share the same last name by parsing the header of the electronic activity, the body or contents of the electronic activity, a signature included in the electronic activity. Further, if the participants have previously communicated with one another using their personal email addresses or if the contents of the electronic activity suggest that they have a prior relationship outside of work, the tagging engine 265 can determine that the participants may be related outside of work and may be configured to determine that the electronic activities exchanged between them are personal electronic activities. The tagging engine 265 can be configured to tag such electronic activities with a personal tag indicating that the electronic activity is determined to be personal. As described herein, the tagging engine 265 or the system, in general, can assign a confidence score to the tag based on how confident the system believes the electronic activity is personal (or on-work related) in nature, based on a number of methods, described above.

In some embodiments, the system 200 or the node profile manager 220 can be configured to determine that two node profiles have a personal (non-professional) relationship either based on the electronic activities exchanged between them that may be tagged with a personal tag. The system can then tag the two node profiles as having a personal relationship. The system can further determine a confidence score for the tag classifying the two node profiles based on how confident the system is in its prediction that the two node profiles have a personal relationship. In some embodiments, the system 200 or the node profile manager 220 can further determine if two nodes have a personal relationship based on commonalities in values in their node profiles, for instance, their home addresses (if they are neighbors), college or school affiliations (alumni/classmates), same last names, other non-professional affiliations, or other signals that may indicate the two node profiles may have a personal relationship.

The system 200 or the tagging engine 265 can be configured to use the personal tag between the node profiles to classify subsequent electronic activities exchanged between the node profiles. In some embodiments, as described below, the system can be configured to restrict matching electronic activities with a personal tag to record objects. The system can further be configured to either unmatch or unlink previously matched electronic activities from record objects of systems of record or remove such activities from existing data structures.

It should be appreciated that the system can conversely or similarly determine that certain electronic activities are professional in nature and tag such electronic activities with a professional tag. The system 200 can also be configured to determine that relationships between node profiles may also be professional based on their respective node profiles as well as past electronic activities exchanged between them.

It also should be appreciated that the system 200 or the tagging engine 265 can conversely or similarly determine that certain electronic activities can be more professional in nature. In some embodiments, the tagging engine 265 can determine that an electronic activity is professional if the content of the electronic activity relates to sales, recruiting, scheduling an appointment or other business related activities. The tagging engine 265 can then assign a professional tag to such an electronic activity indicating that the electronic activity is professional in nature. The tagging engine 265 can further assign a tag indicating that the electronic activity is relating to sales, recruiting or scheduling an appointment based on the context of the electronic activity. Such tags can be used to determine whether or not to match the electronic activity to a record object of a system of record. For instance, if the electronic activity relates to sales, the system 200 can tag the electronic activity with a sales tag, which the system 200 can use to determine to match the electronic activity to a record object of one or more systems of record as a sales related electronic activity can be a useful data point for a company in evaluating various aspects of their business processes. In another example, electronic activities relating to scheduling can be provided a scheduling tag, which can be used by the system 200 to filter out or restrict such electronic activities from being matched to record objects. Restricting certain electronic activities from being matched to record objects reduces the computing resources required for matching electronic activities to record objects by reducing the total volume of electronic activities to match. Restricting certain electronic activities from being matched to record objects also reduces the amount of noise in systems of record as scheduling related electronic activities add noise to the system of record.

It should be appreciated that certain tags, such as scheduling tags can be used to filter out electronic activities from a queue of electronic activities that the system 200 may attempt to match to record objects. Other such types of tags may include personal tags indicating that the electronic activity is personal, internal tags indicating that the electronic activity as internal to a company, among others.

The tagging engine 265 can further identify certain types of electronic activities that may enhance the generation of the node graph or further define roles of nodes. For instance, in an out of office email response, a person may identify a second person to contact in their absence. The tagging engine 265 can tag the electronic activity as an out of office response but further allow the node profile manager 220 to update the node profile of the nodes to indicate the potential relationship between the person who is out of office and the second person to contact in their absence or create a new node profile for that person if such a node profile doesn't yet exist.

The tagging engine 265 can assign additional tags, such as vacation tags that can be used by the node profile manager 220 to update the node profile of the node accordingly. The tagging engine 265 can assign a vacation tag to an electronic activity responsive to determining that the electronic activity corresponds to the person being on vacation. The node profile manager 220 can parse the timing of the vacation from the electronic activity and update the node profile of the person on vacation. This information can then be passed to one or more systems of record and cause the systems of record to update their settings for the given person.

In addition, the tagging engine 265 can be configured to assign a ‘no longer with company’ tag to an electronic activity responsive to parsing the electronic activity. This information can then be passed to one or more systems of record and cause the systems of record to update their settings for the given person. In addition, the ‘no longer with company’ tag can cause the system 200 to stop future emails to be sent to the person, and also trigger the system 200 to determine which company that person joined.

In some embodiments, the tagging engine 265 can be configured to assign a ‘parental leave’ tag to an electronic activity responsive to parsing the electronic activity. The parental leave tag can be helpful to predict when a person may be returning to work. In addition, the system 200 can assign a parental leave tag to a node profile and further associate the node profile to one or more other nodes or persons that have been identified as taking over the responsibilities of the person on parental leave.

In some embodiments, the tagging engine 265 can tag an electronic activity with a deceased tag responsive to parsing the electronic activity. In some embodiments, the system 200 can then update the associated node profile indicating that the person is deceased.

In some embodiments, the tagging engine 265 can identify a unique electronic activity identifier for the electronic activity and generate a plurality of tags to assign to the electronic activity. The tagging engine 265 can generate tags to indicate if the electronic activity is external or internal, the participants associated with the electronic activity, an amount of time to generate or perform the electronic activity, job titles or seniority levels of the participants based on their job titles, departments in the organization, to which participants may belong based on their job titles, any values, opportunities or record objects with which the electronic activity may be linked or otherwise associated, one or more stages of the sales opportunity or any other system of record process, among others.

The tagging engine 265 can be configured to assign custom tags based on one or more tagging policies of one or more users or subscribers of the system 200 . For instance, a subscriber of the node graph generation system 200 may desire to generate custom tags that allows the subscriber to tag all electronic activity including ride sharing receipts that identify the company's address. The subscriber may choose to then use these tags to identify all electronic activity that include ride sharing receipts that identify the company's address to gather information about the employees' use of ride sharing to and from work. The subscriber can use the information to improve business processes, such as considering providing a shuttle service to employees or negotiating with a ride sharing company for discounted pricing. The tagging engine 265 can provide a subscriber an interface through which subscribers can define policies for assigning such custom tags.

It should be appreciated that custom tags can be defined using one or more pieces of information from electronic activities. For instance, custom tags can be defined for certain email addresses, certain names, certain combination of senders and recipients, as well as based on words, phrases or other content included in the subject line or body of an electronic activity. For instance, emails that include “legal@example.com” can be tagged as Legal. Emails that mention “cell” or “mobile” and a regex pattern that matches a cell phone number in the body of an email but not part of the signature block of the email can be tagged as Cell. Emails that include a regex pattern that matches a social security number in the body of an email can be tagged as social security number, while emails that include a regex pattern that matches a credit card number in the body of an email can be tagged as credit card number. The tagging engine 265 , the filtering engine 270 or the node graph generation system 200 can then use these tags to process the electronic activities tagged with these tags in accordance to one or more processing policies, such as filtering policies described herein. The filtering policies can also be customized for a given user, company or subscriber of the system 200 such that a company can deploy rules to handle such emails in accordance with the company's specific rules.

The tagging engine 265 may iteratively tag and re-tag the same electronic activities as more information is received. The tagging engine can be configured to recalculate, re-ingest and re-featurize, and re-tag all data associated with electronic activities to further refine the tags.

The tagging engine 265 can tag electronic activities based on context derived from features of such electronic activities. As described above, the tagging engine 265 can assign tags indicating a type of meeting: in-person vs. conference call; internal vs. external, a location of the participants to determine if the meeting is an in-person meeting, a time zone of the meeting, countries associated with participants of the meetings, among others.

In some embodiments, the tagging engine 265 can identify if the meeting is a conference call or a web-based meeting. In some embodiments, the type of activity can determine the types of tags to assign to the activity. For instance, for meetings, the tagging engine 265 can assign the following tags: External, internal, in-person, conference call, and custom tags, based on NLP, regex and other rules, customized by the user. For emails, the tagging engine 265 can assign the following tags: External, internal, sent, received, blast, cold. In some embodiments, blast detection techniques can be used to determine if the email is a blast email. These techniques include natural language processing analysis, blast email header analysis, volume of electronic activity for a given node, as well as MIME message data. Generally, blast emails do not include a Blast Message ID that is common across all of the blast emails. As such, detecting an email as a blast email is quite complex. In fact, blast emails are generally generated to appear as non-blast emails and as such, the present disclosure provides techniques that are based on the low variability of language complexity and word count. In some embodiments, the blast email tag assigned can include metadata identifying, for instance, the number of emails in a blast, the tool used to send the blast. The blast email tag can be used to group all emails of the blast and can include metadata about the group of emails. The tagging engine can deploy artificial intelligence to stitch the blast message ID together across multiple emails to identify if a portion of a message ID is common across multiple emails. For calls, the tagging engine 265 can assign tags to the call indicating if the call was electronically logged or manually entered. The call can be tagged based on the caller and the receiver, duration, disposition, etc.

In some embodiments, the tagging engine 265 can employ custom policies for tagging electronic activities. For instance, the tagging engine can tag every first meeting with a company as a new business meeting. The tagging engine can tag every meeting with a CXO title, such as CEO, CMO, COO, CLO, CFO, CSO, as CXO. The tagging engine can tag every meeting with CFO as finance. A reporting engine can then use these tags to generate custom reports for instance, a report identifying all new business meetings, or all activities involving finance, among others.

Tags can also be assigned for certain words, such as product names, taglines, competitor mentions, among others. By parsing emails of employees to identify the use of certain words or phrases specifically defined for a particular entity, the tagging engine can tag such electronic activities to particular products and use such electronic activities to determine if training is needed, if the correct messaging is being used or if the employees are implementing the latest messaging outlined by the company. For instance, a company can train reps to say X, but then train reps to say Y, and then use tags (from NLP) to determine which reps actually say Y. For example, if a company has 18,000 sales reps, how does the company ensure their employees are using the new training or actively selling a new product. In addition, the tagging engine 265 can apply policies to tag electronic activities based on a sentiment analysis. For instance, the tagging engine 265 can apply employee activities tags based on, negative or positive sentiment with the mention of the company's competitor or the company's feature.

In some embodiments, the tagging engine 265 can assign tags based on predicting likelihood of deal or business process completion and time to completion from electronic activities. Additional details regarding how this is determined is described herein and based in part on stage classification and the roles of the participants in the electronic activities.

In some embodiments, tags can be defined by rules. Some rules can be global rules, company rules defined by company, team level rules and user level rules.

H. Filtering Engine

The filtering engine 270 can be any script, file, program, application, set of instructions, or computer-executable code that is configured to enable a computing device on which the filtering engine 270 is executed to perform one or more functions of the filtering engine 270 described herein.

The filtering engine 270 can use information identified, generated or otherwise made available by the tagging engine 265 . The filtering engine 270 can be configured to block, remove, redact, delete, or authorize electronic activities tagged or otherwise parsed or processed by the tagging engine 265 . For example, the tagging engine 265 can be configured to assign tags to electronic activities, node profiles, systems of record 9360 , among others. The filtering engine 270 can be configured with a policy or rule that prevents ingestion of an electronic activity having a specific tag or any combination of tags, such as a credit card tag or social security tag. By applying filtering rules or policies to tags assigned to electronic activities, node profiles, or records from the one or more systems of record, among others, the node graph generation system 200 can be configured to block, delete, redact or authorize electronic activities at the ingestion step or redact out parts or whole values of any of the fields in the ingested electronic activities. Additional details about some of the types of filtering based on tags are provided herein.

I. Source Health Scores Including Field-Specific Health Scores, Overall Health Scores and Determining Trust Scores Based on Health Scores

The source health scorer 215 can be any script, file, program, application, set of instructions, or computer-executable code that is configured to enable a computing device on which the source health scorer 215 is executed to perform one or more functions of the source health scorer 215 described herein. The source health scorer 215 is configured to access a system of record and retrieve all data stored in the system of record. The source health scorer 215 can then identify each record object stored in the system of record and determine, for each record object, a number of missing values of fields. The source health scorer can then generate a field-specific score for each field indicating a health or quality of each field of the system of record. The source health scorer 215 can further determine an overall health score for the source based on the field-specific scores of each field. In some such embodiments, the overall health score is based on missing field values.

The source health scorer 215 can further be configured to determine if the values of fields of record objects are accurate by comparing the values to node profiles maintained by the node profile manager 220 or to record objects maintained by the record objects manager. Based on the number of values that are inconsistent with the values maintained by the node graph generation system 200 , the source health scorer can generate a health score for the system of record.

The source health scorer 215 can similarly generate a health score for each system of record. The source health scorer 215 can then compare the health score of a given system of record to the aggregate health scores of a plurality of systems of record to determine a relative trust score of the system of record. In some embodiments, the source health scorer 215 can assign different weights or scores to different types of systems of record. The source health scorer 215 may assign lower health scores to data included in a system of record that is generated using manual entry relative to node profiles that are automatically populated or generated by the node graph generation system 200 based on electronic activities.

Further, different types of sources can include emails, or email signatures within an email, one or more systems of record, among many other source types. The trust score of a source can be determined based on the health score of the source, at least in the case of a system of record. In some embodiments, the trust score assigned to electronic activity such as an email can be greater than a trust score assigned to a data point derived from a system of record as the system of record can be manually updated and changed. Additional details regarding the health score of a system of record are described below.

In some embodiments, the health score of a system of record maintained by a data source provider can be determined by comparing the record objects of the system of record with data that the system has identified as being true. For instance, the system 200 can identify, based on confidence scores of values (as described below) of fields, that certain values of fields are true. For instance, the system may determine that a value is true or correct if multiple data points provide support for the same value. In some embodiments, the multiple data points may for example, be at least 5 data points, at least 10 data points, or more. The system 200 can then, for a value of a field of a record object of the system of record, compare the value of the system of record to the value known to the system to be true. The system can repeat this for each field of a record object to determine if any values of a record object are different from the values the system knows to be true. In some embodiments, when determining the health score, the system may only compare those values of fields of record objects of the system of record that the system has a corresponding value that the system knows is true. For instance, the system may know that a phone number of a person “Roger Nadal” is 617-555-3131 and may identify such a number as true based on multiple data points. However, the system may not know an address of the person Roger Nadal. In such an instance, the system may only compare the phone number of the record object corresponding to Roger Nadal to determine the health score of the system of record but not compare the address of the person Roger Nadal as the system does not know the address of Roger Nadal. Furthermore, even if the node profile of Roger Nadal had an address but the confidence score of the address was below a predetermined threshold, the system would not compare the address from the system of record to the address of the node profile since the system does not have enough confidence or certainty that the address is true. As such, the system can be configured to determine the health score of a system of record by comparing certain values of record objects of the system of record to values the system knows as true or above a predetermined confidence score. In this way, in some embodiments, the health score of the system of record is based on an accuracy of the data included in the system of record rather than how complete the system of record is not.

As described above, the health score of a system of record can be an overall health score that can be based on aggregating individual field-specific health scores of the system of record. It should be appreciated that the system 200 can assign different weights to each of the field-specific health scores based on a volume of data corresponding to the respective field, a number of values that does not match values the system 200 knows to be true, among others.

In certain situations, the system 200 can compute trust scores for data points based on the health score of a system of record. In some embodiments, the system 200 can compute the trust score based on the overall health score of the system of record that is the source of the data point. However, in some embodiments, it may be desirable to configure the system 200 to provide more granularity when assigning a trust score to a system of record that is the source of the data point. For instance, a company may meticulously maintain phone numbers of record objects but may not be so meticulous in maintaining job titles of record objects such that the field specific health score for the phone number field of the system of record is much better than the field-specific health score for the job title field and also better than the overall health score of the system of record determined based on the aggregate of the respective field specific health scores of fields of the system of record. In some embodiments, as will be described herein, if a data point supporting a phone number of a node profile is provided by the system of record, the system 200 may be configured to determine a trust score for the data point based on the field specific health score of the field “phone number” for the system of record rather than the overall health score of the system of record, which is lower because the field specific health score of the field “job title” of the system of record is much lower than the field specific health score of the field “phone number.” By determining trust scores based on the field-specific health scores of systems of record, the system 200 may be able to more accurately rely on the data point and provide a more accurate contribution score of the data point as will be described herein. Additional concepts relating to health scores and trust scores are provided herein with respect to section 5 relating to monitoring health scores of systems of record. ix. Node Field Value Confidence Scoring

The attribute value confidence scorer 235 can be any script, file, program, application, set of instructions, or computer-executable code, that is configured to enable a computing device on which the attribute value confidence scorer 235 is executed to perform one or more functions of the attribute value confidence scorer 235 described herein. The attribute value confidence scorer 235 can be configured to determine a confidence of each value of an attribute of a node profile. The confidence of a value is determined based in part on a number of electronic activities or sources that contribute to the value, time since each electronic activity provided support or evidence of the value, time since the field value in the source system of record was last modified or confirmed by a human operator, as well as the source of the electronic activity. Electronic activity that is received from mail servers or another source that does not involve manual entry may be assigned a greater weight (or trust/health score) than a source that involves manual entry, such as a customer relationship management tool.

The attribute value confidence scorer 235 can be configured to determine a confidence of each value of an attribute of a node profile. An attribute or field can have multiple candidate values and the value with the highest confidence score can be used by the node graph generation system for confirming or validating the value of the field. The attribute value confidence scorer 235 can apply one or more scoring algorithms to determine the likelihood that each value is a correct value of the attribute. It should be appreciated that a value does not need to be current to be correct. In some embodiments, as new entities are onboarded into the system, electronic activities and systems of record corresponding to systems of record of the new entities can be processed by the system 200 . In processing these electronic activities and systems of record, some electronic activities can be associated with dates many years in the past. Such electronic activities are not discarded. Rather, the system processes such electronic activities and information extracted from these electronic activities are used to populate values of fields of node profiles. Since each data point is associated with a timestamp, the data point may provide evidence for a certain value even if that value is not a current value. One example of such a value can be a job title of a person. The person many years ago may simply have been an associate at a law firm. However, that person is now a partner at the firm. If emails sent from this person's email account are processed by the system 200 , more recently sent emails will have a signature of the person indicating he's a partner, while older emails will have a signature of the person indicating he's an associate. Both values, partner and associate are correct values except only partner is the current value for the job title field. A confidence score of the current value may be higher in some embodiments as data points that are more recent may be assigned a higher contribution score than data points that are older. Additional details about contribution scores and confidence scores are provided below.

In some embodiments, a node profile can correspond to or represent a person. As will be described later, such node profiles can be referred to as member node profiles. The node profile can be associated with a node profile identifier that uniquely identifies the node profile. Each node profile can include a plurality of attributes or fields, such as First name, Last name, Email, job title, Phone, LinkedIn URL, Twitter handle, among others. In some embodiments, a node profile can correspond to a company. As will be described later, such node profiles can be referred to as group node profiles. The group node profile can be similar to the member node profile of a person except that certain fields may be different, for example, a member node profile of a person may include a personal cell phone number while a group node of a company may not have a personal cell phone number but may instead have a field corresponding to parent company or child company or fields corresponding to CEO, CTO, CFO, among others. As described herein, member node profiles of people and group node profiles of companies for the most part function the same and as such, descriptions related to node profiles herein relate to both member node profiles and group node profiles. Each field or attribute can itself be a 3-dimensional array. For instance, the First name attribute can have two values: first name_1|first name_2, one Last name value and three email address values email_A|email_B|email_C. Each value can have an Occurrence (counter) value, and for each occurrence that contributes to the Occurrence value, there is an associated Source (for example, email or System of record) value and an associated timestamp (for example, today, 3:04 pm PST) value. In this way, in some embodiments, each value of a field or attribute can include a plurality of arrays, each array identifying a data point or an electronic activity, a source of the data point or electronic activity, a time associated with the data point or electronic activity, a contribution score of the data point or electronic activity and, in some embodiments, a link to a record of the data point or electronic activity. It should be appreciated that the data point can be derived from a system of record. Since systems of records can have varying levels of trust scores, the contribution score of the data point can be based on the trust score of the system of record from which the data point was derived. Stated in another way, in addition to each attribute being a 3-dimensional array, in some embodiments, each value of an attribute can be represented as a plurality of arrays. Each array can identify an electronic activity that contributed to the value of the attribute, a time associated with the electronic activity and a source associated with the electronic activity. In certain embodiments, the sub-array of occurrences, sources and times can be a fully featured sub-array of data with linkage to where the data came from.

J. Node Profile Inferences

Certain information about a node can be inferred by the node graph generation system 200 based on information included in electronic activities ingested by the system 200 . For instance, the node profile manager 220 or the electronic activity tagging engine 265 can infer if a person has left a job or switched jobs if the occurrence counter for a first value stops increasing or the frequency at which the occurrences of the first value appear has been reduced and the occurrence counter for a second value is increasing or the occurrences are more recent or are received from a source that has a higher trust score indicating that the person has changed email addresses, which can indicate that the person has switched jobs. In certain embodiments, the system 200 can determine if the second value corresponds to an email address corresponding to another employer or another company. In some embodiments, the system 200 can determine if the domain name of the email address corresponds to a list of known domain names corresponding to personal, non-work email addresses (for instance, gmail.com, outlook.com), among others. In some embodiments, the system 200 can determine if the domain name is associated with a predetermined minimum number of accounts with the same domain name. The node profile manager 220 can look at relevancy of Source, recency of time and Occurrences to determine whether to update the email field from the first email (Email_A) to the second email (Email_B).

In some embodiments, the attribute value confidence scorer 235 described herein can provide mechanisms to confirm validity of data using multiple data sources. For instance, each electronic activity can be a source of data. As more electronic activities are ingested and increase the occurrence of a value of a data field, the system can confirm the validity of the value of the field based on the number of occurrences. As such, the system described herein can compute a validity score of a value of a field of a node profile based on multiple data sources. For instance, the system can determine how many data sources indicate that the job title of the person is VP sales and can use the health score of those sources to compute a validity score or confidence score of that particular value. In addition, the timestamp associated with each electronic activity can be used to determine the validity score or confidence score of that particular value. More recent electronic activities may be given greater weight and therefore may influence the validity score of the particular value more than electronic activity that is much older.

It should be appreciated that electronic activity that is generated and ingested in real-time or near real-time can be assigned a greater weight as the electronic activity has no bias, whereas data input manually into a system of record may have some human bias. In certain embodiments in which data is imported from systems of records, the weight the data has on a confidence score of the value is based on a trust score of the system of record from which the data is imported.

In some embodiments, the attribute value confidence scorer 235 can determine a confidence score of a data point based on the data sources at any given time. A data point can be a value of a field. For example, “VP, product” can be a value for a job title of a node profile. The attribute value confidence scorer 235 can utilize the electronic activities ingested in the system to determine how many electronic activities have confirmed that the value for the job title is VP, product for that node in the email signatures present in those electronic activities. In some embodiments, the attribute value confidence scorer 235 can take into account a recency of the activity data and the source type or a health score of the source type to determine the confidence score of the value of the field. In some embodiments, the node profile manager can determine a current value of a field based on the value of the field having the highest confidence score.

K. Stitching Time Series Together

The system can be configured to maintain a time series array for each field of a node profile that can be used to determine a timeline of events associated with the node. The system can maintain the time series array based on timestamps of all data sources of all values for each field of the node. For instance, the timeline can be used to determine a career timeline with work history information, a series of job title changes indicating promotions, among other things. In addition, the timeline of events can track a person's movement across companies or geographic locations over time as well as a list of other nodes or persons the company has been affiliated or associated with at different points in time. For instance, the job title of a node profile can include the following values over a period of time: director|vp sales|president|CEO. In certain embodiments, each of the values of the title can have an increase in a confidence score at different times and as a confidence score of a given value of the title field increases, the confidence score of the preceding value of the title field decreases.

L. Node Connections

The node pairing engine 240 can be any script, file, program, application, set of instructions, or computer-executable code that is configured to enable a computing device on which the node pairing engine 240 is executed to perform one or more functions of the node pairing engine 240 described herein. The node pairing engine 240 can compute a connection strength between nodes based on electronic activity associated with both of the nodes. More of the recent electronic activity between the two nodes will indicate a greater connection strength. Moreover, with different tags assigned to those electronic activities, the node pairing engine 240 can further determine the relationship between the two nodes and the context in which the two nodes are connected. For instance, two nodes may be connected through their work on one or more opportunities or one node may report to the second node, among others. The context behind the relationships can be derived from the electronic activity associated with the two nodes as well as other electronic activity associated with each node independent of the other node. In certain embodiments, the node pairing engine 240 can use metadata from the electronic activities to infer connection strength or relationships. For instance, the node pairing engine can compute an average time a node takes to respond to another node and use the average time to respond to determine a connection strength. In some embodiments, the average time to respond is inversely proportional to the strength of the connection. Furthermore, the node pairing engine 240 can look at other information relating to the electronic activities to infer connection strengths. If a node responds to another node outside of business hours can be an indicator of connection strength or connection relationships.

The node pairing engine 240 can determine a connection strength between nodes at a given point in time across a timeline. As the nodes exchange further electronic activity, the connection strength can increase. The system is configured to determine the connection strength at a particular time period by filtering the electronic activities based on their respective times. In certain embodiments, the node pairing engine 240 can recalculate a connection strength between nodes responsive to a trigger. In some embodiments, the trigger can be based on a confidence score falling below a predetermined threshold indicating that the confidence in a particular value is unstable or unusable. For instance, the trigger can be satisfied or actuated when the node pairing engine 240 determines that the confidence score of a particular value of a field, such as a current employer of a person is below a predetermined confidence score (indicating that the person may no longer be at a particular company). In certain embodiments, certain changes to values in fields can trigger recalculating a connection strength irrespective of activity volume, for instance, when a new value under the employer field is added in the node.

In some embodiments, the node pairing engine 240 can determine a connection strength between two nodes by identifying each of the electronic activities that associate the nodes to one another. In contrast to other systems that may rely on whether a node has previously connected with another node, the node pairing engine 240 can determine a connection strength at various time periods based on electronic activities that occur before that time period. In particular, the node pairing engine 240 can determine staleness between nodes and take the staleness to determine a current connection strength between nodes. As such, the node pairing engine 240 can determine a temporally changing connection strength. For instance, the node pairing engine 240 can determine how many interactions recently between the two nodes. The node pairing engine 240 can determine whether the connection between the two nodes is cold or warm based on a length of time since the two nodes were involved in an electronic activity or an amount of electronic activity between the two nodes. For instance, the node pairing engine 240 can determine that the connection strength between two nodes is cold if the two nodes have not interacted for a predetermined amount of time, for instance a year. In some embodiments, the predetermined amount of time can vary based on previous electronic activity or past relationships by determining additional information from their respective node profiles. For instance, former colleagues at a company may not have a cold connection strength even if they do not communicate for more than a year.

Referring briefly to FIG. 8 , FIG. 8 illustrates electronic activities involving two nodes and the impact a time decaying relevancy score has on the connection strength between the two nodes. As shown in FIGS. 8 , N 1 and N 2 may exchange a series of electronic activities. The node pairing engine 240 or the system 200 can maintain a log of each of the electronic activities involving both nodes. Each electronic activity can have a unique electronic activity identifier and can identify a type of activity and maintain a time decaying relevancy score that can decrease in strength over time as time goes by. The node pairing engine 240 can compute the connection strength in part by taking the sum of the respective time decaying relevancy score of each of the electronic activities between the two nodes. In some embodiments, the node pairing engine 240 can take into account other factors for computing the connection strength, for instance, by comparing one or more fields of the node profiles. For instance, nodes that belong to the same organization, report to each other via a clear reporting logic (and lack of reporting up alternative nodes) or have previously worked together can contribute to the connection strength between the nodes.

In certain embodiments, the node pairing engine 240 can determine that a first node reports to a second node based on monitoring electronic activity exchanged between the two nodes as well as electronic activity that includes both nodes. In some embodiments, the node pairing engine 240 can apply one or more rules to predict a relationship between two nodes based on the metadata information associated with the electronic activities including both nodes.

In some embodiments, the connection strength between two nodes can be greater if the node pairing engine 240 can determine, from the electronic activities involving the two nodes, a type of relationship between the two nodes. For instance, if the node pairing engine 240 can determine that one of the nodes is the only known superior node and the other of the nodes is the likely subordinate (instead of simply knowing that the two nodes are colleagues or on the same team), the node pairing engine 240 can increase the connection strength between the two nodes.

In some embodiments, the node pairing engine 240 figured to determine the connection strength between two nodes by monitoring the type of electronic activities exchanged between them, the time of day, the day of the week, the mode of communication (email versus telephone versus text message versus office phone versus cell phone), and the duration of such communications. The system 200 can determine that if two nodes are communicating over a weekend, the connection is stronger than other connections that may only have communications limited to weekdays during office hours. The system 200 can also determine that the connection strength between two nodes may be strong if the two nodes are responding to each over the weekend, if they follow up with phone calls after receiving emails, or other patterns that may indicated a strong connection strength.

The node pairing engine 240 can be configured to identify a plurality of node pairs that have a strong connection strength. The node pairing engine 240 can then apply machine learning techniques to analyze electronic activities between the nodes of the node pair as well as analyze the node profiles of each node and the nodes to which each of the nodes are connected. The node pairing engine 240 can then generate a connection strength determination model that can be configured to determine the connection strength between two nodes using the model that is trained on node pairs known to have a strong connection strength. In some embodiments, the node pairing engine can further train the model with node pairs that have a weak connection strength in a similar fashion.

The node paring engine 240 or the tagging engine 265 can further tag the connection between the nodes as professional, personal, colleagues, ex-colleagues, alumni, classmates, among others. These tags can be updated as more and more electronic activities are processed over time and the confidence score of these tags can be adjusted accordingly. The connection strength between nodes can be used by companies to determine which employee to assign to leads, accounts, or opportunities based on the node's connections strengths with the lead, employees at the account, and employees of the account that may likely be working on the opportunity. Additional details about assigning employees to record such record objects are described below with respect to Section 12.

M. Node Resolution

The node resolution engine 245 can be any script, file, program, application, set of instructions, or computer-executable code that is configured to enable a computing device on which the node resolution engine 245 is executed to perform one or more functions of the node resolution engine 245 described herein.

The node resolution engine 245 is configured to resolve nodes to which electronic activities are to be linked or otherwise associated. The node resolution engine 245 can use the parsed information from the electronic activity to identify values included in node profiles to determine a match score between the electronic activity and a given node profile. The node resolution engine 245 can match the electronic activity to one or more node profiles based on a match score between the electronic activity and each of the node profiles exceeding a certain threshold. Different fields are assigned different weights based on the uniqueness of each value. In some embodiments, the uniqueness of each value can be determining how many node profiles include the same value for the given field relative to the total number of node profiles.

In some embodiments, the node resolution engine 245 may match the electronic activity to the nodes between which the electronic activity occurred. The node resolution engine 245 or the node pairing engine can establish an edge between the two nodes corresponding to the electronic activity.

In some embodiments, the node resolution engine 245 may not be able to determine if the electronic activity matches any of the existing node profiles maintained by the node profile manager. In some such embodiments, the node resolution engine 245 can cause a new node profile to be generated and populated with values extracted from the electronic activity. Before the node resolution engine 245 or other module of the system 200 determines to generate a new node, the node resolution engine 245 can be configured to execute a node creation process. In some embodiments, the node resolution engine 245 can determine if the metadata of the electronic activity has attributes that are high confidence that match, such as phone number, LinkedIn ID, or email address. At the initial stage, the node resolution engine 245 can create a temporary node because not enough information is known to match the electronic activity to an existing node. As a response to the electronic activity is received, additional information can be parsed from the response to the electronic activity, which can then be used to further populate the temporary node. The temporary node can then be matched to existing node profiles to determine if an existing node matches the temporary node. If so, the temporary node can be merged with the existing node profile. In some embodiments, the process of merging involves appending the temporary node with another node because there might be mutually exclusive information that should be added.

In some embodiments, the node resolution engine 245 can perform identity resolution or deduplication based on one or more unique identifiers associated with a node profile. For instance, if one system of record provides a first email address, uniquename@example1.com and another system of record provides a second email address, uniquename@example2.com, while there is not a direct match, the node resolution engine 245 can resolve the two identifiers if there is a statistically significant number of matching or near matching fields, tags, or other statistical resemblances.

In particular, the node resolution engine 245 can parse the string before the @ in the email to determine one or more of a first name and last name of the person. The node resolution engine 245 can apply several techniques to do so. First, the node resolution engine 245 can check to see if there are any rules in place for the domain name of the email that indicate a particular pattern for assigning email addresses by the domain. For instance, does the company associated with the domain assign email addresses using any of the following conventions: firstname.lastname@domainname.com, FirstInitialLastname@domainname.com, firstname@domainname.com, among others. This can be determined by looking at node profiles (and email addresses) of other people belonging to the same company. Second, the node resolution engine 245 can parse the string before the @ to attempt to recognize names from the strings. the node profile manager 220 maintains node profiles that include first names and last names and as such, the node resolution engine 245 can attempt to match a sequence of characters in the string to the list of first names and last names to see if certain names are included in the string. Upon identifying names from the string, the node resolution engine 245 can determine if the name is typically a first name or a last name based on a frequency of such names being first names or last names. Upon identifying the names with some level of statistical confidence, the node resolution engine 245 can identify a first name and a last name of a person associated with the email address and may use the first name, the last name and the company name to try and match the email address to an existing node profile of the person.

In some embodiments, the node resolution engine 245 or the node profile manager 220 can build a frequency distribution of first and last names from information included in the node profiles maintained by the node profile manager 220 . The node resolution engine 245 can determine from a full name, a first name and a last name based on certain names being more common as last names and other names being more common as first names. The node resolution engine 245 can then determine a domain of the email. The node resolution engine can then calculate the probability that the string before the @ in the email corresponds to a person.

In some embodiments, the node resolution engine 245 can further determine if additional fields that could be matching—such as a social handle or a phone number to then have more surface to compare one node to other nodes to identify if any of the nodes can be merged.

In some embodiments, the node resolution engine can utilize time zone detection to resolve if two nodes belong to the same person. The system 200 can compute a time zone of each node by monitoring their electronic activities and deducing that the time zone they are in is based on the times at which the electronic activities are ingested by the system 200 . For instance, the node resolution engine 245 can determine that two nodes are different if the time zones deduced from their electronic activity match different time zones.

In some embodiments, the node resolution engine 245 can be configured to periodically perform deduplication by comparing each node to every other node to determine if two nodes can be merged.

N. Systems of Record Data Extraction

The record data extractor 230 can be any script, file, program, application, set of instructions, or computer-executable code, that is configured to enable a computing device on which the record data extractor 230 is executed to perform one or more functions of the record data extractor 230 described herein.

The record data extractor 230 can be configured to extract data from one or more records of one or more systems of record. The record data extractors 230 can identify record objects included in a system of record and extract data from each of the record objects, including values of particular fields. In some embodiments, the record data extractor 230 can be configured to extract values of fields included in the record object that are also included in the node profile maintained by the node graph generation system 200 .

O. Linking Electronic Activity to Systems of Record Data

The electronic activity linking engine 250 can be any script, file, program, application, set of instructions, or computer-executable code, that is configured to enable a computing device on which the electronic activity linking engine 250 is executed to perform one or more functions of the electronic activity linking engine 250 described herein. Additional details regarding the electronic activity linking engine is provided below.

P. Systems of Record Object Management

The record object manager 255 can be any script, file, program, application, set of instructions, or computer-executable code that is configured to enable a computing device on which the record object manager 255 is executed to perform one or more functions of the record object manager 255 described herein. The record object manager 225 can be configured to maintain data regarding record objects of multiple systems of record and can be configured to augment information for a record object by extracting information from multiple record objects across a plurality of systems of record. The record object manager 255 can function as a systems of record object aggregator that is configured to aggregate data points from many systems of record, calculate the contribution score of each data point, and a timeline of the contribution score of each of those data points. The record object manager 255 or the system 200 in general can then enrich the node graph generated and maintained by the node graph generation system 200 by updating node profiles using the data points and their corresponding contribution scores. In certain embodiments, the record object manager 255 can be further configured to utilize the data from the node graph to update or fill in missing data in a target system of record provided the data in the node graph satisfies a predetermined confidence value. Additional details regarding the record object manager 255 is provided below.

Q. Organizational Node Graph

The data source provider network generator 260 can be any script, file, program, application, set of instructions, or computer-executable code, that is configured to enable a computing device on which the data source provider network generator 260 is executed to perform one or more functions of the data source provider network generator 260 described herein. Additional details relating to the functionality of data source provider network generator 260 are provided below with respect to the generation of a company cloud described in Section 9.

2. Systems and Methods for Linking Electronic Activity to Systems of Record

At least one aspect of the disclosure relates to systems and methods of linking electronic activities to record objects of systems of record. The linking can be performed by the electronic activity linking engine 250 (and other components) of the node graph generation system 200 illustrated in FIG. 4 .

Enterprises and other companies spend significant amount of resources to maintain and update one or more systems of records. Examples of systems of records can include customer relationship management (CRM) systems, enterprise resource planning (ERP) systems, document management systems, applicant tracking systems, among others. Typically, these systems of records are manually updated, which can result in multiple issues. First, the information that is updated into the systems of records can be incorrect either due to human error or in some cases, malicious intent. Second, the information may not be updated in a timely manner. Third, employees may not be motivated enough to even update the systems of records, resulting in systems of records that include outdated, incorrect, or incomplete information. To the extent that enterprises rely on the data included in their systems of records to make projections or predictions, such projections and predictions may also be inaccurate as the data relied upon is also inaccurate. The present disclosure aims to address these challenges that enterprises face with their existing systems of records. In particular, the present disclosure describes systems and methods for linking electronic activities to record objects included in one or more systems of record. Electronic activities, such as electronic mail, phone calls, calendar events, among others, can be used to populate, update, and maintain states of record objects of systems of record. As electronic activities are exchanged between users, these electronic activities can be parsed to not only update a node graph as described above, but further update shadow record objects for one or more systems of records of enterprises that have provided access to such systems of record to the data processing system 9300 shown in FIG. 3 or the node graph generation system 200 . As described herein, the shadow record objects can be synced with the record objects of the one or more systems of records of the enterprises. In some embodiments, the electronic activities can be used to directly update the one or more systems of records of the enterprises without first updating a shadow record object. As described herein, and also referring to FIG. 3 , the updating of record objects with electronic activity can refer to updating record objects within systems of record 9360 and/or shadow record objects within the shadow systems of record. By way of the present disclosure, the node graph generation system 200 can use the electronic activities to populate, maintain, and update states of record objects of systems of record.

As described herein, the node graph generation system 200 can include the electronic activity linking engine 250 that is configured to link electronic activities to record objects of one or more systems of record. By linking the electronic activities to such record objects, the electronic activity linking engine 250 can be configured to update states of one or more record objects based on the electronic activities.

Linking electronic activities to record objects can also be referred to as matching or mapping the electronic activities to record objects. Linking the electronic activities to the record objects can provide context to the electronic activities. The linked electronic activities can be stored in association with one or more record objects to which the electronic activity is linked in a system of record. Linking an electronic activity to a record object can provide context to the electronic activity by indicating what happened in the electronic activity or record object, who was involved in the electronic activity or record object, and to what contact, node, person or business process, the electronic activity or record object should be assigned. Linking the electronic activity to the record object can indirectly provide context as to why the electronic activity occurred. For example, the linking of electronic activity, such as an email, to a lead record object (in the context or a customer relationship management system) can provide context to the email that the email was sent to establish or further a lead with the intent of converting the lead into an opportunity (and the lead record object into an opportunity record object). Although the description provided herein may refer to record objects and business processes corresponding to customer relationship management systems, it should be appreciated that the present disclosure is not intended to be limited to such systems of records but can apply to many types of systems of record including but not limited to enterprise resource planning systems, document management systems, applicant tracking systems, among others. For the sake of clarity, it should be appreciated that electronic activities can be matched to record objects directly without having to link the electronic activities to node profiles. In some embodiments, the electronic activities can be matched to node profiles and those links can be used to match some of the electronic activities to record objects.

Referring now to FIG. 9 , FIG. 9 illustrates a block diagram of an example electronic activity linking engine 250 . The electronic activity linking engine 250 can use metadata to identify a data source provider associated with an ingested electronic activity and identify a corresponding system of record. The electronic activity linking engine 250 can match the electronic activity to a record object of the corresponding system of record. The electronic activity linking engine 250 can include, or otherwise use, a tagging engine, such as the tagging engine 265 described above to determine and apply tags to the ingested electronic activities. The electronic activity linking engine 250 can include a feature extraction engine 310 to extract features from the electronic activities that can be used to link electronic activities with one or more record objects of systems of records. In some embodiments, some of the features can include values corresponding to values stored in one or more node profiles maintained by the node graph generation system 200 . The features, however, can include other information that may be used to in conjunction with information also included in node profiles to link the electronic activity to one or more record objects included in one or more systems of record.

The electronic activity linking engine 250 can include a record object identification module 315 to identify which record object or objects within a system of record to match a given electronic activity. The electronic activity linking engine 250 can include a policy engine 320 . The policy engine 320 can maintain policies that include strategies for matching the electronic activities to the record objects. The electronic activity linking engine 250 can include a stage classification engine 325 to determine a shadow stage for a given opportunity record object. The electronic activity linking engine 250 can include a link restriction engine 330 that can apply one or more policies from the policy engine 320 when linking electronic activities to record objects. The linking engine 250 can link the electronic activity to the record object identified by the record object identification module 315 . Additional details regarding each of the components 310 - 335 are further provided herein.

The features extraction engine 310 of the electronic activity linking engine 250 can be any script, file, program, application, set of instructions, or computer-executable code, that is configured to enable a computing device on which the features extraction engine 310 is executed to extract or identify features from one or more electronic activities and/or corresponding node profiles maintained by the node graph generation system 200 and use the extracted or identified features to generate corresponding feature vectors for the one or more electronic activities.

The features extraction engine 310 can be a component of the electronic activity parser 210 or otherwise interface with the electronic activity parser 210 to parse electronic activities and extract features from electronic activities. For example, the electronic activity parser 210 can parse ingested electronic activities, such as, emails, calendar meetings, and phone calls. The features extraction engine 310 can, for each electronic activity, extract various features from the electronic activity and in some embodiments, from one or more node profiles corresponding to the electronic activity, that the electronic activity linking engine 250 can use to link the electronic activity to one or more record objects of the one or more systems of record. In some embodiments, before an electronic activity can be linked to a record object of a system of record, the electronic activity can be matched to one or more node profiles in the node graph. In this way, the features extraction engine 310 can generate, based on the parsed data from the electronic activity parser 210 , a feature vector for the electronic activity that can be used to link the electronic activity to a record object based on features extracted from the electronic activity as well as one or more node profiles of the node graph.

The feature vector can be an array of feature values that is associated with the electronic activity. The feature vector can include each of the features that were extracted or identified in the electronic activity by the feature extraction engine 310 . For example, the feature vector for an email can include the sending email address, the receiving email address, and data parsed from the email signature. Each feature value in the array can correspond to a feature or include a feature-value pair. For example, the contact feature “John Smith” can be stored in the feature vector as “John Smith” or “name: John Smith” or “first name: John” “last name: Smith.” As described herein, the matching model 340 can use the feature vector to match or link the electronic activity to a record object. The feature vector can include information extracted from an electronic activity and also include information inferred from one or more node profiles of the node graph generation system 200 . The feature vector can be used to link an electronic activity to at least particular record object of a system of record by matching the feature values of the feature vector to a record object. For instance, if the feature vector includes the values “John” for first name and “Smith” for last name, the electronic activity linking engine 250 can link the electronic activity to a record object, such as a lead record object that includes the name “John Smith” assuming other matching conditions are also met.

The features for an electronic activity can be explicit from the electronic activity. The explicit features can be determined from the metadata or content of the electronic activity. For example, the “senders email address” of an email can be parsed from the email's header value, as described in relation to FIG. 5A . In some embodiments, some features for an electronic activity can be derived from the electronic activity. The derived features can be determined or implied based on explicit features of the electronic activity or determined from node profiles of the node graph described above. For example, an example electronic activity may not include a name of the company to which the sender belongs. In such a case, the feature extraction engine 310 can extract the name of the company to which the sender belongs from a node profile of the sender, which can include the name of the company. The name of the company can be retrieved from the node profile of the sender and saved as a value in the feature vector once retrieved from the node profile associated with the sender.

The features included in the feature vector for an electronic activity can include features associated with the generator (or sender) of the electronic activity and features associated with the recipient (or receiver) of the electronic activity. For example, sender's email address and the recipient's email address can both be used as features of the electronic activity. The features for an electronic activity can include, but are not limited to, a contact role, contact name, sender email address, recipient email address, domain, list of recipient email addresses, estimated effort, and time, features extracted from email contents using natural language processing, features extracted from email signature, time of the email sent/delivery, among others. The feature vectors can be used to match electronic activities to record objects of one or more systems of record.

The feature extractor engine 310 can further identify one or more tags assigned to an electronic activity or one or more node profiles associated with the electronic activity by the tagging engine 265 and include those tags or information relating to those tags in the feature vector. In some embodiments, these tags can be used to provide context to certain electronic activities, which can be used by the electronic activity linking engine 250 to link electronic activities to record objects of one or more systems of records.

The record object identification module 315 can be any script, file, program, application, set of instructions, or computer-executable code, that is configured to enable a computing device on which the record object identification module 315 is executed to determine or select one or more record objects to which an electronic activity should be linked or matched.

Briefly referring to FIG. 10 , among others, FIG. 10 illustrates a plurality of example record objects, and their interconnections. The record objects shown in FIG. 10 can be record objects or data records of a system of record, such as a customer relationship management (CRM) system. It should be appreciated that other types of systems of records and record objects may exist and can be integrated with the node graph generation system 200 . For instance, other systems of records can include Applicant Tracking Systems (ATS), such as Lever, located in San Francisco, Calif. or Talend by Talend Inc., located in Redwood City, Calif., enterprise resource planning (ERP) systems, customer success systems, such as Gainsight located in Redwood City, Calif., Document Management Systems, among others.

The systems of record can be one or more of shadow systems of record of the data processing system 9300 or the systems of record of the data source providers. Additional details relating to the shadow systems of record of the data processing system 9300 are provided below. As illustrated in FIG. 10 , the record objects can include a lead record object 1000 , an account record object 1002 , an opportunity record object 1004 , or a contact record object 1006 . Each of the different types of record objects can generally be referred to as record objects.

Each record object can be a data structure or data file into which data is stored or associated. The lead record object 1000 can be a low quality object that includes unqualified contact information typically received through a web inquiry. A lead record object can correspond to one or more stages. Upon reaching a final “Converted” stage, a lead record object can be converted in a one-to-many relationship into a Contact record object (person), an Account record object (company, if new, or added to existing account) and an Opportunity record object (if there is an opportunity for a deal here or added as contact role into existing opportunity).

For example, the lead record object 1000 can include the contact information for a lead or prospective buyer. The lead record object 1000 can include fields, such as, Address, City, Company, CompanyDunsNumber, Description, Email, Industry, NumberOfEmployees, Phone, job title, and Website, among others.

The account record object 1002 can be a data structure that includes fields associated with an account that is held with the data source provider. The fields can include AccountNumber, BillingAddress, Description, Industry, Fax, DunsNumber, LastActivityDate, MasterRecordId, Name, NumberOfEmployees, Ownership, Website, YearStarted, and IsPersonAccount, among others. A system of record can include an account record object 1002 for each of the data provider's customers. The system of record can include multiple account record objects 1002 for a given customer. For example, the system of record can include an account record object 1002 for each division of a given customer. The account record object 1002 can be stored with one or more opportunity record objects 1004 .

In some embodiments, the CRM can include partner record objects, which can also be referred to as partner account record objects. A partner account record object can be similar to an account record object. The partner account record object can include an additional field to designate the record object as a partner account record object rather than a standard account record object. The partner account record object can be an account record object that is associated with a partner to the data source provider. For example, the partner account record object can be an account record object for a distributor of the data source provider that distributes goods to the company of the account record object.

The opportunity record objects 1004 can be data structures that include a plurality of fields for a given opportunity. The opportunity can indicate a possible or planned deal with a customer for which an account record object is already stored in the system of record. The opportunity record objects 1004 can include fields such as AccountId, Amount, CampaignId, CloseDate, Description, ExpectedRevenue, Fiscal, HasOpenActivity, IsClosed, IsWon, LastActivityDate, Name, OwnerId, StageName, Territory2Id, and Type, among others. One or more contact record objects 1006 can be associated with the account record object 1002 . The contact record objects 1006 can be data structures that include fields associated with a contact. The contact record object 1006 can include fields such as AccountId, AssistantName, Birthdate, Department, Description, DoNotCall, Email, Fax, FirstName, HasOptedOutOfEmail, HomePhone, LastName, MailingAddress, and MobilePhone, among others.

One or more contact record objects 1006 can be associated with an opportunity record object 1004 via an Opportunity Contact Role object (OCR). For example, a lead to sell a service to a potential customer can convert into an opportunity record object 1004 when the customer begins the negotiation process to purchase the service. A contact record object 1006 can be generated for each of the customer's employees involved in the purchase. Each of the contact record objects 1006 can be associated with the opportunity record object 1004 for the sale via Opportunity Contact Roles, which contain their own metadata about involvement of specific individuals in the opportunity, such as their Role in this particular opportunity or whether they are the Primary Contact of the Account in this Opportunity.

In some embodiments, a lead record object 1000 can be converted into a contact record object 1006 , an account record object 1002 , and an opportunity record object 1004 . For example, a lead record object 1000 can be converted into a new contact record object 1006 , account record object 1002 , and opportunity record object 1004 once the lead record object 1000 after a predetermined number and nature of electronic activities are associated with the lead record object 1000 . Continuing this example, the lead record object 1000 can be generated based on a web inquiry from an interested party (lead) or via a cold email being sent to a potential new customer. If the customer responds and passes qualification criteria, the lead record object 1000 can be converted into a new contact record object 1006 , account record object 1002 , and opportunity record object 1004 . In some embodiments, the lead record object 1000 can be converted into a, for example, contact record object 1006 that can get attached to or linked with an existing account record object 1002 and an existing opportunity record via an Opportunity Contact Role record.

The fields of each of the different record object types can include hierarchical data or the fields can be linked together in a hierarchical fashion. The hierarchical linking of the fields can be based on the explicit or implicit linking of record objects. For example, a contact record object 1006 can include a “Reports To” field into which an identifier of the contact can be stored. The “Reports To” field can indicate an explicit link in a hierarchy between two contact record objects 1006 (e.g., the first contact record object 1006 to the contact record object 1006 of the person identified by the “Reports To” field). In another example, the linking of the record objects can be implicit and learned by the electronic activity linking engine 250 . For example, the electronic activity linking engine 250 can learn if multiple customers have the same value for a “Parent Account” field across multiple system of record sources with high trust score and derive a statistically significant probability that a specific account belongs to (e.g., is beneath the record object in the given hierarchy) another account record object.

Referring to FIG. 9 , among others, the record object identification module 315 can determine, for a given electronic activity to which record object the electronic activity should be linked. Linking the electronic activity to one or more record objects can enable the status, metrics, and stage of the deal or opportunity to be tracked and analyzed, or the context in which the electronic activity was performed to be understood programmatically. Linking electronic activities to the record objects can also enable employee performance to be measured as described herein. The record object identification module 315 can identify a record object of one of the data processing system's shadow systems of record using the feature vectors and node graph. In this way, the record object identification module 315 can assist, aid or allow the electronic activity linking engine 250 to match the electronic activity with a record object using one or more matching models 340 .

The record object identification engine 315 can include one or more matching models 340 . A matching model 340 can be trained or programmed to aid in matching electronic activities to record objects to allow the electronic activity linking engine 250 to link the electronic activities to the matched record objects. For example, the record object identification engine 315 can include or use one or more matching models 340 to assist, aid or allow the electronic activity linking engine 250 to match electronic activities to record objects. In some embodiments, each of the one or more matching models 340 can be specific to a particular data source provider, electronic activity type, or record object type. In some embodiments, the record object identification engine 315 can include a single matching model that the record object identification engine 315 can use to match electronic activities ingested by the data processing system 9300 to any number of a plurality of record objects of a plurality of systems of records. In some embodiments, the matching models 340 can be data structures that include rules or heuristics for linking electronic activities with record objects. The matching models 340 can include matching rules (which can be referred to as matching strategies) and can include restricting rules (which can be referred to as restricting strategies or pruning strategies). As described further in relation to FIGS. 11 and 12 , the record object identification engine 315 can use the matching strategies to select candidate record objects to which the electronic activity could be linked and use the restricting strategies to refine, discard, or select from the candidate record objects. In some embodiments, the matching models 340 can include a data structure that includes the coefficients for a machine learning model for use in linking electronic activities with record objects.

In some embodiments, the matching model 340 used to link electronic activities to one or more record objects can be trained using machine learning or include a plurality of heuristics. For example, as described above the features extraction engine 310 can generate a feature vector for each electronic activity. The matching model 340 can use neural networks, nearest neighbor classification, or other modeling approaches to classify the electronic activity based on the feature vector. In some embodiments, the record object identification engine 315 can use only a subset of an electronic activity's features to match the electronic activity to a record object.

In some embodiments, the record object identification engine 315 can use matching models 340 trained with machine learning to match, for example, the electronic activity to a record object based on a similarity of the text in and the sender of the electronic activity with the text in and sender of an electronic activity previously matched to a given electronic activity. In some embodiments, the matching model 340 can be updated as electronic activities are matched to record objects. For example, a matching model 340 can include one or more rules to use when matching an electronic activity to a record object. If a user matches an electronic activity to a record object other than the record object to which the electronic activity linking engine 250 matched the electronic activity, record object identification engine 315 can update the matching model 340 to alter or remove the rule that led to the incorrect matching.

In some embodiments, once an electronic activity is matched with a record object, a user can accept or reject the linking. Additionally, the user can change or remap the linking between the electronic activity and the record object. An indication of the acceptance, rejection, or remapping can be used to update the machine learning model or reorder the matching strategies as discussed in relation to FIGS. 11 and 12 . The updated model can be used in the future linking of electronic activity to nodes and the nodes to record objects by the record object identification engine 315 . To train the machine learning models, the system can scan one or more systems of record that include manually matched electronic activity and record objects. The previous manually matched data can be used as a training set for the machine learning models.

In some embodiments, the matching model 340 can include a plurality of heuristics with which the record object identification engine 315 can use to link an electronic activity to one or more record objects. The heuristics can include a plurality of matching algorithms that are encapsulated into matching strategies. The record object identification engine 315 can apply one or more matching strategies from the matching models 340 to the electronic activity to select which record object (or record objects) to link with the electronic activity. In some embodiments, the record object identification engine 315 can use the matching strategies to select candidate record objects to which the electronic activity can be linked. The record object identification engine 315 can use a second set of strategies (e.g., restricting strategies) to prune the candidate record objects and select to which of the candidate record objects the electronic activity should be linked.

The application of each strategy to an electronic activity can result in the selection of one or more record objects (e.g., candidate record objects). The selection of which matching strategies to apply to an electronic activity can be performed by the policy engine 320 . The policy engine 320 is described further below, but briefly, the policy engine 320 can generate, manage or provide a matching policy for each of the data source providers 9350 . The policy engine 320 can generate the matching policy automatically. The policy engine 320 can generate the matching policy with input or feedback from the data source provider 9350 to which the matching policy is associated. For example, the data source provider (for example, an administrator at the data source provider) can provide feedback when an electronic activity is incorrectly linked and the matching policy can be updated based on the feedback.

A given matching policy can include a plurality of matching strategies and the order in which the matching strategies should be applied to identify one or more record objects to which to link the electronic activity. The record object identification module 315 can apply one or more of the plurality of matching strategies from the matching models 340 , in a predetermined order specified or determined via the matching policy, to identify one or more candidate record objects. The record object identification module 315 can also determine, for each matching strategy used to identify a candidate record object, a respective weight that the record object identification module 315 should use to determine whether or not the candidate record object is a good match to the electronic activity. The record object identification module 315 can be configured to compute a matching score for each candidate record object based on the plurality of respective weights corresponding to the matching strategies that were used to identify the candidate record object. The matching score can indicate how closely a record object matches the electronic activity based on the one or more matching strategies used by the record object identification module 315 .

One or more of the matching strategies can be used to identify one or more candidate record objects to which the electronic activity linking engine can match a given electronic activity based on one or more features (e.g., an email address) extracted from the electronic activity or tags assigned to the electronic activity. In some embodiments, the features can be tags assigned by the tagging engine 265 . In some embodiments, the electronic activity can be matched to a node profile that is already matched to a record object, thereby allowing the record object identification module 315 to match the electronic activity to a record object previously matched or linked to a node profile with which the electronic activity may be linked. In addition, the matching strategies can be designed or created to identify candidate record objects using other types of data included in the node graph generation system, or one or more systems of record, among others. In some embodiments, the matching strategies can be generated by analyzing how one or more electronic activities are matched to one or more record objects, including using machine learning techniques to generate matching strategies in a supervised or unsupervised learning environments.

Subsequent strategies can be applied to prune or restrict the record objects that are selected as potential matches (e.g., candidate record objects). For example, and also referring to FIG. 11 , FIG. 11 illustrates the restriction of a first grouping 1102 of record objects with a second grouping 1106 of record objects. A first plurality of strategies 1100 can be applied to select a first grouping 1102 of record objects. A second plurality of strategies 1104 can be applied to identify a second grouping 1106 of record objects that can be used to restrict or prune the first grouping 1102 of record objects. For example, the record object identification module 315 can select the record object to which the electronic activity is linked from the overlap 1108 of the groupings 1102 and 1106 .

For example, and also referring to FIG. 12 , among others, FIG. 12 illustrates the application of a first plurality of matching strategies and a second plurality of matching strategies to generate one or more grouping of record objects and then selecting record objects that satisfy both the first plurality of matching strategies and the second plurality of matching strategies. In some embodiments, the first plurality of matching strategies can be configured to generate the first grouping 1102 of record objects shown in FIG. 11 , while the second plurality of matching strategies 1204 can be configured to generate the second grouping 1104 of record objects. In some embodiments, the first plurality of matching strategies 1100 can be associated with one or more recipients of the electronic activity to be matched and the second plurality of matching strategies 1104 can be associated with a sender of the electronic activity to be matched. The candidate record objects selected by the first plurality of matching strategies 1100 and the second plurality of matching strategies 1104 can be filtered, pruned or otherwise discarded from being matched with the electronic activity using restricting strategies (described further below). In some embodiments, the first plurality of strategies can be referred to as buyer-side or recipient-side strategies and the second plurality of strategies can be referred to as seller-side or sender-side strategies. The policy engine 320 can select one or more matching strategies of the first plurality of matching strategies 1100 , second plurality of matching strategies 1104 and restricting strategies for the record object identification engine 315 to apply in a predetermined order. The matching strategies of the first plurality of matching strategies 1100 and the second plurality of matching strategies 1104 can each be configured to select one of the types of record objects. For example, the matching strategies 1100 and 1104 can each be configured to select one of a lead record object 1000 , an account record object 1002 , an opportunity record object 1004 , a partner record object, among others. For example, a matching strategy can be used to match an electronic activity to an account record object 1002 in the shadow system of records based on an email address extracted from the electronic activity via a number of sequentially used matching strategies. The restriction strategies can be used to remove one or more record objects that are selected by any of the first plurality of matching strategies 1100 or any of the second plurality of matching strategies 1104 .

In an example where the electronic activity includes the email “john.smith@example.com,” the record object identification module 315 can use a first matching strategy, such as a matching strategy for selecting the account record object based on email addresses to identify one or more candidate record objects that may match the email address field of the electronic activity. First, the record object identification module 315 can return all contact record objects with “john.smith@example.com” in the email field. The record object identification engine 315 can then identify the account record objects that are linked with each of the contact record objects with “john.smith@example.com” in the email field.

In some embodiments, if the system was not able to find a contact record object with the field (or other fields) containing “john.smith@example.com”, the system can use a secondary matching strategy 1100 and find an account record object with the domain name that matches the domain name of the email “@example.com”. If after applying the restricting strategies and eliminating possible options, only one account with such domain name is left, the system would have identified the account to which potential contact with email address “john.smith@example.com” should belong and the original electronic activity should be linked to. In this case, the system could automatically create a contact record with email “john.smith@example.com”, linked to the account record with domain name “example.com” and then associate electronic activity from which this process started to the newly created contact record object and right account record object. It is worth noting that the order in which matching strategies 1100 and 1104 and the restriction strategies are applied can impact and modify outcomes of matching model 340 .

Still referring to FIG. 12 , the record object identification engine 315 can use one or more of the matching strategies 1100 associated with account record objects to generate a matched candidate record object array 1202 that identifies one or more candidate record objects that were identified based on the matching strategies 1100 associated with account record objects. The record object identification engine 315 can generate three matched record object arrays 1202 . Each of the matched record object arrays can be associated with a different one of the record object types. For example, the record object identification engine 315 can generate an account record object array, an opportunity object array, a contact object array, a lead object array, and a partner object array (not shown). The results (e.g., the returned record objects) for a given matching strategy 1100 can be appended to the record object array 1202 for the associated record object type. For example, matching strategy 1100 ( 1 ) can be used to return the account record objects with UIDs A 1 and A 17 , the matching strategy 1100 ( 2 ) can be used to return the account record object with the UID A 93 , and the matching strategy 1100 ( 3 ) can be used to return the account record object with the UIDs A 123 and A 320 .

The recipient-side matching strategies 1100 can include a plurality of matching strategies. The matching strategies can be arranged in a predetermined and configurable order. The matching strategies of the recipient-side strategies 1100 can include one or more of matching to opportunity record objects based on contact role, matching to account record objects based on contact record objects, matching to account record objects based on domains, matching to opportunity record objects based on contacts, matching to partner account record objects based on contacts, matching to partner account record objects using domains, among others. The record object identification engine 315 can use the recipient-side strategies 1100 to select a plurality of candidate record objects to form record object arrays 1202 .

Each value in the matched record object arrays 1202 can include an indication of one of the record objects that was matched using the matching strategies (e.g., the recipient-side strategies 1100 ). For example, the matched record object arrays 1202 can include an array of UIDs associated with each of the record objects that were matched by the record object identification engine 315 using the matching strategies. In some embodiments, each value in the array can be a data pair that includes the matched record object UID and a score indicating how confident the system is on the match between the electronic activity and the record object. The score can be based on the matching strategy which returned the given record object. In some embodiments, the score may be adjusted based on previous matches and how a user accepted or modified the previous matches. In some embodiments, a record object can be selected multiple times; for example, a first and a second matching strategy can each select a given record object. A score can be associated with each matching strategy and the score for the record object selected by multiple matching strategies can be an aggregate (for example, a weighted aggregate) of the scores associated with each of the matching strategies that selected the record object. The scores can indicate how well the selected record object satisfied the one or more matching strategies.

The record object identification engine 315 can select record objects based on matching strategies for each of the participants associated with the electronic activity. For example, the electronic activity can be an email with a sender and a plurality of recipients. The sender and the plurality of recipients can be the participants that are associated with the electronic activity. The record object identification engine 315 can apply each of the matching strategies for each of the participants. Multiple matching strategies for a given participant can return the same record object multiple times. A matching strategy applied to multiple participants can return the same record object multiple times. The score that the record object identification engine 315 assigns to each selected record object can be based on the number of times the given record object was returned after the matching strategies were applied for each of the electronic activity's participants. For example, a first record object can be returned or selected four times and a second record object can be returned or selected once. The record object identification engine 315 can assign the first record object a higher relative score than the second record object that was only selected once.

In some embodiments, the record object identification engine 315 can select record objects using matching strategies that select record objects based on tags. The electronic activity can be parsed with a natural language processor and the tags can be based on terms identified in the electronic activity. Parsing the electronic activity with the natural language processor can enable the electronic activity to be matched to record objects by mention. For example, the electronic activity can be parsed and the term “renewal” can be identified in the electronic activity. A “renewal” tag can be applied to the electronic activity. A matching strategy to select record objects based on tags can select a renewal record object opportunity with the electronic activity and include the renewal record object opportunity in the record object array 1202 . In another example, the system 200 can identify identification numbers contained in the electronic activity for which tags can be assigned to the electronic activity. The identification numbers can include serial numbers, account numbers, product numbers, etc. In this example, and assuming a tag identifying an account number is assigned to the electronic activity, a matching strategy to select record object based on tags can select an account record object that includes a field with the account number identified in the electronic activity's tag.

The record object identification engine 315 can apply one or more of a plurality of sender-side strategies 1104 that can be used to select one or more candidate record objects included in one or more second set of record object arrays 1204 . In some embodiments, the record object identification engine 315 can apply one or more of a plurality of sender-side strategies 1104 to restrict or prune the record objects selected using the matching strategies 1100 . By applying the set of sender-side strategies 1104 , the record object identification engine 315 can generate the second set of record object arrays 1204 that can be used to prune or restrict the first set of record object arrays 1202 . For example, the record object identification engine 315 , applying a sender-side strategy 1104 that selects accounts record objects based on an account owner, can select the account record object with UID A 17 and A 123 . The record object identification engine 315 can use sender-side strategies such as selecting record objects for matching based on account teams associated with one or more participants of the electronic activity. For example, the record object identification engine 315 can select a record object that identifies the sender of the electronic activity. as a member of the account team associated with the record object.

The record object identification engine 315 can prune the identified candidate record object by determining the intersection of the first set of record object arrays 1202 (produced with matching strategies 1100 ) and the second set of record object arrays 1204 (produced with matching strategies 1104 ). For example, the account record object array 1202 generated with the set of matching strategies 1100 is, in the example illustrated in FIG. 12 , {A 1 , A 17 , A 93 , A 123 , A 320 }. The account object array 1204 generated with the set of sender-side strategies 1104 is {A 17 , A 123 }. The record object identification engine 315 can determine that the intersection array 1206 of the account record object array 1202 and account record object array 1204 is {A 17 , A 123 }. In this way, the sender-side strategy restricted the record objects A 1 , A 93 and A 320 from being selected as a match to the incoming electronic activity. The record object identification engine 315 can combine the intersection arrays 1206 generated by the intersection of the sender-side strategies 1104 and the recipient-side strategies 1100 to generate an output array 1208 . The output array 1208 can include indications of record objects and the weights or scores associated with each of the record objects.

The record object identification engine 315 can also use restriction strategies to further prune or restrict out record objects selected using the matching strategies 1100 and 1104 . The record object identification engine 315 can use the restriction strategies to select one or more record objects to which the electronic activity should not be matched. For example, although this example is not reflected in FIG. 12 , the record object identification engine 315 can use a restriction strategy to select record objects A 1 and A 17 to generate a restriction record object array including {A 1 , A 17 }. If, using the recipient-side matching strategies, the record object identification engine 315 selects record objects A 1 , A 3 , A 10 , and A 17 to generate {A 1 , A 3 , A 10 , A 17 }, the record object identification engine 315 can remove A 1 and A 17 from the record object array because they were identified in the restriction record object array as record object to which the electronic activity should not be matched.

In some embodiments, the record object identification engine 315 can apply the restriction strategies once the record object identification engine 315 selects one or more record objects with the sender-side strategies 1104 or the recipient-side strategies 1100 . The record object identification engine 315 can apply the restriction strategies before the record object identification engine 315 selects one or more record objects with the sender-side and recipient-side strategies. For example, the restriction strategies can be one of the below-described matching filters.

In some embodiments, the output array 1208 can include one or more record objects that can be possible matches for the electronic activity. The selection from the output array 1208 can be performed by the below described record object identification engine 315 . If the output array 1208 only includes one record object, the electronic activity can be matched with the record object of the output array 1208 . In some embodiments, the electronic activity is only matched with the record object if the confidence score of the record object is above a predetermined threshold. The confidence score of the record object indicates a level of confidence that the record object is the correct record object to which to link the electronic activity. If the output array 1208 includes multiple record objects, the electronic activity can be matched with the record object having the highest confidence score (given that the highest confidence score is above the predetermined threshold). If the output array 1208 does not include any record objects, the confidence score of the record objects are not above the predetermined threshold, or multiple record objects have the same confidence score above the predetermined threshold, the system can request input from the user as to which record object to match the electronic activity. In these cases, the matching strategies can be updated based on the input from the user.

In some embodiments, the record object identification engine 315 can group or link contact record objects on one or both sides of a business process into groups. The record object identification engine 315 can use the groups in the matching strategies. For example, the record object identification engine 315 can group users on a seller side into account teams and opportunity teams. Account teams can indicate a collection of users on the seller side that collaborate to close an initial or additional deals from a given account. Opportunity teams can be a collection of users on the seller side that collaborate to close a given deal. The record object identification engine 315 can add a user to an account or opportunity team by linking the contact record object of the user to the given account team record object or opportunity team record object. The record object identification engine 315 can use account team-based matching strategies or opportunity team-based matching strategies to select record objects with which the electronic activity can be matched.

In some embodiments, at periodic intervals, the record object identification engine 315 can process the electronic activities linked with account record objects and opportunity record objects to generate account teams and opportunity teams, respectively. For a given account record object, the record object identification engine 315 can count the number of times that a seller side user interacts with the account record object (for example, is included in an electronic activity that is linked or matched to the account record object). For example, the record object identification engine 315 can count the number of times the user was included on an email or sent an email that was linked with the account record object. If the count of the interactions is above a predetermined threshold, the record object identification engine 315 can add the user to an account team for the account record object. In some embodiments, the count can be made over a predetermined time frame, such as within the last week, month, or quarter. The record object identification engine 315 can perform a similar process for generating opportunity teams. In some embodiments, the account teams and opportunity teams can be included in the matching and restriction strategies used to match an electronic activity with a record object. Conversely, if the count of the interactions of a particular user is below a predetermined threshold within a predetermined time frame (for example, a week, a month, three months, among others), the record object identification engine 315 can remove the user from the account team or the opportunity team.

In some embodiments, the record object identification engine 315 can select record objects with which to match a first electronic activity based on a second electronic activity. The second electronic activity can be an electronic activity that is already linked to a record object. The second electronic activity can be associated with the first electronic activity. For example, the system 200 can determine that the first and second electronic activities are both emails in a threaded email chain. The system can determine the emails are in the same thread using a thread detection policy. The thread detection policy can include one or more rules for detecting a thread by comparing subject lines and participants of a first email and a second email or in some embodiments, by parsing the contents of the body of the second email to determine if the body of the second email includes content that matches the first email and email header information of the first email is included in the body of the second email. If the second electronic activity is an earlier electronic activity that is already matched to a given record object, the record object identification engine 315 can match the first electronic activity to the same record object.

The policy engine 320 can be any script, file, program, application, set of instructions, or computer-executable code that is configured to enable a computing device on which the policy engine 320 is executed to manage, store, and select matching strategies. The policy engine 320 can generate, manage, and store one or more matching strategy policies for each of the data source providers. For example, the policy engine 320 can generate matching strategy and restriction strategy policies for each division or group of users within a data source provider.

In some embodiments, a matching policy can include a data structure that indicates which matching strategies to apply to an electronic activity for a given data source provider. For example, the matching policy can include a list of matching strategies that are used to select record objects. The list of matching strategies can be manually created by a user or automatically generated or suggested by the system. In some embodiments, the policy engine can learn one or more matching strategies based on observing how one or more users previously matched electronic activities to record objects. These matching strategies can be specific to a particular user, group, account, company, or across multiple companies. In some embodiments, the policy engine can detect a change in linkages between one or more electronic activities and record objects in the system of record (for example, responsive to a user linking an electronic activity to another object inside a system of record manually). The policy engine can, in response to detecting the change, learn from the detected change and update the matching strategy or create a new matching strategy within the matching policy. The policy engine can be configured to then propagate the learning from that detected change across multiple matching strategies corresponding to one or more users, groups, accounts, and companies. The system can also be configured to find all past matching decisions that would have changed had the system detected the user-driven matching change before, and update those matching decisions retroactively using the new learning.

In some embodiments, the matching policy can also identify which restriction strategies to apply to an electronic activity for a given data source provider. For example, the restriction policy can include a list of restriction strategies that are used to restrict record objects. The list of restriction strategies can be manually created by a user or automatically generated or suggested by the system. In some embodiments, the policy engine can learn one or more restriction strategies based on observing how one or more users previously matched or unmatched electronic activities to record objects. These restriction strategies can be specific to a particular user, group, account, company, or across multiple companies. In some embodiments, the policy engine can detect a change in linkages between one or more electronic activities and record objects in the system of record (for example, responsive to a user linking or unlinking an electronic activity to another object inside a system of record manually). The policy engine can, in response to detecting the change, learn from the detected change and update the restriction strategy or create a new restriction strategy within the restriction policy. The policy engine can be configured to then propagate the learning from that detected change across multiple restriction strategies corresponding to one or more users, groups, accounts, and companies. The system can also be configured to find all past matching decisions that would have changed had the system detected the user-driven restriction change before, and update those matching decisions retroactively using the new learning.

The policy engine 320 can update the matching policy with input or feedback from the data source provider to which the matching policy is associated. For example, the data source provider can provide feedback when an electronic activity is incorrectly linked and the matching policy can be updated based on the feedback. Updating a matching policy can include reordering the matching strategies, adding matching or restriction strategies, adjusting individual matching strategy behavior, removing matching strategies, or adding restriction strategies. The link restriction engine 330 can be any script, file, program, application, set of instructions, or computer-executable code, that is configured to enable a computing device on which the link restriction engine 330 is executed to limit to which record objects an electronic activity can be linked.

In some embodiments, data source providers can generate restriction policies or restriction strategies that include rules that indicate conditions under which electronic activities should not be linked to record objects. For example, restriction policies can include rules that prevent internal emails from being linked to a record object. Other restriction policies can limit bot emails (e.g., emails sent to a plurality of people or an email sent as an automatic reply), non-person electronic activity (e.g., electronic activity, such as calendar activity, associated with an asset, such as a conference room), activities, related to persons, who are working in sensitive or unrelated positions (e.g. HR employees), activities, related to persons who do not “own” specific records in the system of record or who do not belong to specific groups of users, or to private or personal electronic activities (e.g., non-work-related emails). These restriction policies or restriction strategies can include one or more matching filters described herein.

The restriction policies can be generated automatically by the system or can be provided by the data source provider. Different restriction policies can be linked together to form a hierarchy of restriction policies, preserving the order in which they should be applied. For example, restriction policies can be set and applied at a group node level (e.g., company level), member node level (e.g., user level), account level, opportunity level, or team level (e.g., groups of users such as account teams or opportunity teams). For example, a restriction policy applied at the company level can apply to the electronic activity sent or received by each employee of the company while a restriction policy applied at the user level is only applied to the electronic activity sent or received by the user.

The link restriction engine 330 can use the restriction policies to remove or discard record objects from the output array 1208 . For example, if a restriction policy indicates that electronic activity from a given employee should not be linked to record object A 17 and record object A 17 is included in the output array 1208 , the link restriction engine 330 can remove record object A 17 from the output array 1208 .

In some embodiments, the link restriction engine 330 can apply the restriction policies to electronic activities prior to the matching performed by the record object identification module 315 . For example, if a restriction policy includes rules that calendar-based electronic activity for a conference room should not be linked to any record object, the link restriction engine 330 can discard or otherwise prevent the record object identification module 315 from linking the electronic activity to a record object.

The tagging engine 265 can be any script, file, program, application, set of instructions, or computer-executable code that is configured to enable a computing device on which the tagging engine 265 is executed to generate tags for the electronic activity. The tagging engine 265 can generate or add tags to electronic activity based on information generated or otherwise made available by the record object identification module 315 and the matching model 340 . The tagging engine 265 can generate a tag array that includes each of the plurality of tags assigned or associated with a given electronic activity. By having tags assigned to electronic activities the node graph generation system 200 can be configured to better utilize the electronic activities to more accurately identify nodes and record objects to which the electronic activity should be linked.

In addition to the above described tags, the tagging engine 265 can assign tags to an electronic activity based on the output of the record object identification module 315 and matching model 340 , among other components of the system described herein. For example, the tagging engine 265 can add one or more tags indicating to which record objects the record object identification module 315 returned as candidate record objects for the electronic activity. For example, and also referring to FIG. 12 , the tagging engine 265 can add tags to indicate each record object contained within the output array 1208 . In some embodiments, the tagging engine 265 can add a tag for each record object contained within the output array 1208 . In some embodiments, the tagging engine 265 can add a tag for each record object contained within the output array 1208 . In some embodiments, the tagging engine 265 can include a tag only for the record object in the output array 1208 that most closely matches the electronic activity.

The linking generator 335 can be any script, file, program, application, set of instructions, or computer-executable code that is configured to enable a computing device on which the linking generator 335 is executed to link electronic activities to record objects. As described above, the system can generate and maintain a shadow system of record for each of a data source provider's system of record. The data source provider's system of record can be referred to as a master system of record or tenant-specific system of record. The linking generator 335 can select a record object from the record object array 1208 and link the electronic activity to the selected record object in the shadow system of record. For example, the record object identification engine 315 can use the confidence scores of the record objects in the record object array to select a record object with which to match the electronic activity.

Also referring to FIG. 12 , the linking generator 335 can link the electronic activity to one or more of the record objects included in the output array 1208 . In some embodiments, the linking generator 335 can link the electronic activity to one or more record objects in the output array 1208 . For example, the linking generator 335 may only link the electronic activity to the record object in the output array 1208 that most closely matches the electronic activity. In some embodiments, the linking generator 335 links the electronic activity with only one of the record objects in the output array 1208 (e.g., the record object having the highest score).

Linking the electronic activity with a record object can include saving the electronic activity (or an identifier thereof) into the shadow system of record in association with the record object. For example, each record object can include a unique identifier. The electronic activity can be saved into the system of record and the record object's unique identifier can be added to a record object field of the electronic activity to indicate to which record object the electronic activity is linked. In some embodiments, each electronic activity can be assigned a unique identifier. The electronic activity's unique identifier can be added to a field in the shadow record object to indicate that the electronic activity is associated with the shadow record object. In some embodiments, the shadow record object can be matched or synced with a record object in a client's system. When the shadow record object and the record object are synced, data, such as the electronic activity's unique identifier in the above example, can be copied to the corresponding field in the matched record object of the client's system. For example, if the linking generator 335 matches an email to a given record object in the shadow system of record, when synced the email can be matched to the given record object in the client's system of record.

By linking the electronic activities to record objects, the system can generate metrics regarding the electronic activities. The metrics can include engagement scores for users, employees, specific deals or opportunities, managers, companies, or other parties associated with a system of record. Additional details regarding metrics and the calculation thereof are described below in Section 11, among others. The engagement scores can indicate amongst other things how likely an opportunity (or deal) is to close successfully (or unsuccessfully) or whether the number of contacts in the account are sufficiently engaged with the sales representative to prevent the account from disengaging with the company. The engagement scores can provide an indication of an employee's productivity and can indicate whether the user should receive additional training or can indicate whether the user is on track to achieve predefined goals. The metrics can be calculated dynamically as the electronic activities are matched to nodes and record objects or the metrics can be calculated in batches, at predetermined intervals. Metrics can also be based on the content or other components of the electronic activity in addition to or in place of the linking of the electronic activity to a node and record object.

For example, FIG. 13 illustrates an example calculation for calculating the engagement score of an opportunity record object. The example calculation can include an electronic activity weight 1300 , a volume vector 1302 indicating a count of each electronic activity type, a seniority weight 1304 , and a department weight 1306 . As illustrated in FIG. 13 , the electronic activity linking engine 250 can determine the engagement score by collecting each of the electronic activities associated with a given opportunity record object. The electronic activity linking engine 250 can count the volume (e.g., number) of each type of electronic activity linked with the opportunity record object. For example, the electronic activity linking engine 250 can tag each ingested electronic activity as being an in-person meeting electronic activity, a conference call electronic activity, a received email electronic activity, a sent email electronic activity, a cold email electronic activity, a blast email electronic activity, or a call, among others. The electronic activity linking engine 250 can also tag the electronic activity using NLP. For example, electronic activity linking engine 250 can tag an email based on mentions of a competitor, product, specific people, specific places, or other phrases contained within the electronic activity. The electronic activity linking engine 250 can also generate tags based on the combination of other tags, linking information, and fields within linked objects.

The count of each of the different types of electronic activities can be stored in the volume vector 1302 . The volume vector 1302 can be multiplied by the weight or points assigned to each of the different electronic activities. The weight or points associated with each of the electronic activity types in the electronic activity weight can indicate the significance of the electronic activity to the successful completion of the deal. In some embodiments, the weights can be set by the electronic activity linking engine 250 . The weights can be set based on the sales motion of the given tenant or data source provider. Each weight can be a normalized value that can represent the significance a given feature, or collection of electronic activities. For example, an email including the VP of Sales can be given a higher weight when compared to an email that only includes managers. In some embodiments, the electronic activity linking engine 250 can reference an organizational hierarchy derived from the node graph and assign relatively higher weights to electronic activities that involve people relatively higher in the organizational hierarchy. For example, having repeated, in-person meetings with a CxO at a prospective client or company can be more beneficial to the successful closing of the deal than cold calling a random contact at the company. Accordingly, the in-person meeting is assigned a higher weight (50 points) that the call, which is assigned a relatively lower weight of 1.

The engagement score can also be based on a seniority weighting factor. The seniority weighting factor can then be applied to the volume weighted scores of the electronic activities. The seniority weighting factor can apply a weighting based on those included on or involved with the electronic activity. In some embodiments, the feature extraction engine 310 can determine which contacts or people are associated with electronic activity. For example, the feature extraction engine 310 can parse the TO: and CC: fields of an email (an example electronic activity) and then, using the node graph, determine seniority, department, job title, or role of each contact listed on the email at their current and past roles. In some embodiments, the seniority weighting factor can be based on the contact record objects to which the matching model 340 (or other component of the system) matched the electronic activity.

The engagement score can also be based on a department weighting factor. The department weighting factor can be normalized across all the departments (such as within a company or account). In some embodiments, once the system determines which contacts are associated with the electronic activity, as described above, the system can determine the department of each of the contacts using the node graph.

The stage classification engine 325 can be any script, file, program, application, set of instructions, or computer-executable code, that is configured to enable a computing device on which the stage classification engine 325 is executed to determine or predict a stage of a deal or opportunity.

In some embodiments, record objects can be associated with a plurality of stages. In some embodiments, the record object can be an opportunity record object or any other record object that describes a business process, such as a sales process, a hiring process, or a support ticket. The stages can be defined by the system or by the data source provider.

Using the example of an opportunity record object in a sales process, the stages can indicate the steps taken in an opportunity or deal from the beginning of the deal to the final disposition of the deal (e.g., close and won or closed and lost). The stages can include, but are not limited to: prospecting, developing, negotiation, review, closed/won, or closed/lost.

Each of the stages can be linked to different tasks or milestones. For example, a sales representative can develop a proposal during the “developing” stage. Each of the stages can be linked to different actions taken by the sales representative or prospect contacts, associated contacts or other people. For example, initially during the prospecting and developing stages a sales representative may be involved in the opportunity or deal. At a later stage, such as negotiations, a sales manager may become involved in the deal.

The stages can be based on the contacts present or involved on both sides of the deal. For example, as the deal advances to higher stages, more senior people may be included in the electronic activities. The stage of the deal can be based on the identification or introduction of an opportunity contact role (OCR) champion. In some embodiments, an administrator or user of the system of record can link the opportunity record object with a contact record object and designate the contact of the contact record object as an opportunity contact role. The champion can be a person on the buyer side of the deal that will support and provide guidance about the deal or opportunity to the seller side. In some embodiments, the OCR champion can be selected based on one or more rules. For example, the one or more rules can include setting the person identified as the VP of sales (or other specific role) as the OCR champion. In some embodiments, the OCR champion can be selected based on historical data. For example, the historical data can indicate that in 90% of the past deals a specific person or role was the OCR champion. Based on the historical data, when the person is added as a recipient of an electronic activity, the person can be identified as the OCR champion. The OCR champion can also be identified probabilistically based on tags associated with the electronic activities linked to the opportunity record object or content within the electronic activities.

In some embodiments, OCRs can be configurable by the company on an account by account basis. Depending on the type, size or nature of the opportunity, the customer or account involved in the opportunity may have different types and numbers of OCRs involved in the opportunity relative to other opportunities the same customer is involved in. Examples of OCRs can include “Champion,” “Legal,” “Decision Maker,” “Executive sponsor” among others.

The system 200 can be configured to assign respective opportunity contact roles to one or more contacts involved in an opportunity. The system 200 can be configured to determine the opportunity contact role of a contact involved in the opportunity based on the contact's involvement. In some embodiments, system 200 can determine the contact's role based on a function the contact is serving. The function can be determined based on the contact's title, the context of electronic activities the contact is involved in, and other signals that can be derived from the electronic activities and node graph. In addition, the system 200 can assign the contact a specific opportunity contact role based on analyzing past deals or opportunities in which the contact has been involved and determining which opportunity contact role the contact has been assigned in the past. Based on historical role assignments, the system 200 can predict which role the contact should be assigned for the present opportunity. In this way, the system 200 can make recommendations to the owner of the opportunity record object to add contacts to the opportunity or assign the contact an opportunity contact role.

In some embodiments, the system 200 can determine that a contact should be assigned an opportunity contact role of “Executive Sponsor.” The system may determine this by parsing electronic activities sent to and from the contact and identify, using NLP, words or a context that corresponds to the role of an Executive sponsor. In addition, the system can determine if the contact has previously been assigned an opportunity contact role of executive sponsor in previous deals or opportunities. The system can further determine the contact's title to determine if his title is senior enough to serve as the Executive sponsor.

In some embodiments, the electronic activity linking engine 250 can use a sequential occurrence of electronic activities to determine contact record objects that should be linked or associated with an opportunity record object. The electronic activity linking engine 250 can also determine the roles of people associated with the contact record objects linked to an opportunity. The identification of people associated with opportunity and account record objects (and their associated roles) can be used to determine stage classification, group of contacts on the buyer side that are responsible for the purchase, and for many other use cases. In some embodiments, the sequential occurrence of electronic activities can be used to determine the role or seniority of users involved in a business process. For example, initial emails linked with an opportunity record object can involve relatively lower-level employees. Later emails linked to the opportunity record object can include relatively higher-level employees, such as managers or Vice Presidents. The electronic activity linking engine 250 can also identify the introduction of contacts in a chain of electronic activities, such as a series of email replies or meeting invites, to determine a contact's participation and role in a business process. For example, the electronic activity linking engine 250 can use NLP and other methods to identify the introduction of a manager as a new OCR based on an email chain.

It should be appreciated that in some embodiments, the node graph generation system 200 can include node profiles corresponding to each of the contact record objects included in one or more shadow system of records or master systems of records. As sequential electronic activities traverse the system 200 , the node graph generation system 200 can parse the electronic activities and determine that additional email addresses are being included or some existing email addresses are being removed in subsequent electronic activities. The node graph generation system can identify node profiles corresponding to the email addresses being added and establish links or relationships between the node profiles included in the electronic activity. As the electronic activity linking engine 250 links electronic activities to record objects, such as opportunity record objects, node profiles included in the electronic activity are also linked to the opportunity record object. The stage classification engine can use this information to classify a stage of the opportunity based in part on node profiles linked to the record object and based on the involvement of the node profiles in the electronic activities that can be determined using effort estimation techniques, volumes of emails exchanged, as well as based on NLP of the content to identify the role of each of the node profiles, as well as historical patterns of linkage of similar node profiles to similar record objects, as discussed below.

In some embodiments, the electronic activity linking engine 250 can also determine a contact's role based on the tags of the electronic activity in which the contact was included. For example, relatively higher-level employees, such as managers, can be more likely to be included electronic activities such as in person meeting invites and conference calls. The electronic activity linking engine 250 can also use NLP on the content of electronic activities to determine the role of contacts. For example, the electronic activity linking engine 250 can process the content of the electronic activities to identify terms that may indicate a role of a contact. For example, an email can include the phrase “my assistant Jeff will schedule the meeting.” The electronic activity linking engine 250 can identify the phrase “my assistant Jeff” and include in the contact record object associated with Jeff the role of “assistant.” The electronic activity linking engine 250 can also determine that the sender of the email is more likely to be a manager because the sender of the email has an assistant.

Similar to how the record object manager 255 maintains the shadow systems of record and corresponding record objects, the stage classification engine 325 can maintain a shadow stage indicating a stage the stage classification engine 325 determines is the current stage for the deal or opportunity. The stage classification engine 325 can determine or estimate the stage of the opportunity using a top-down algorithm or a bottom-up algorithm. With the top-down algorithm, the data source provider can provide a policy that includes a plurality of rules. The rules can indicate requirements for entering or exiting a stage. For example, the data source providers policy may include a rule indicating that an opportunity cannot progress to a negotiation stage until a procurement manager is involved in the deal on the buyers side. In this example, the stage classification engine 325 can monitor the ingested electronic activities. When the stage classification engine 325 detects that the system has linked an electronic activity (such as an email) to the opportunity record object and the electronic activity includes a contact that is a procurement manager (as determined, for example, via the node graph), the stage classification engine 325 can set the shadow stage to negotiation stage. In some embodiments, the shadow stage can be synced to the data source providers stage for the given record object. In some embodiments, the stage classification engine 325 can update a stage of a record object of the master system of record to match the shadow stage of the corresponding record object determined by the stage classification engine 325 . In some such embodiments, the client may provide or select a configuration setting that allows the stage classification engine 325 to update the stage classification of a record object of the master system of record of the client. In some embodiments, the stage classification engine 325 can use a bottom-up approach to predict or determine the stage. The stage classification engine 325 can use machine learning to predict or determine the stage of a deal or opportunity. For example, the stage classification engine 325 can combine the features from each of the electronic activities linked to an opportunity record object into a feature vector. The stage classification engine 325 can use a neural network, or other machine learning technique, to classify the deal into one of the stages based on the feature vector. The machine learning algorithm can be trained using the progression of previous deals through the stages. In some embodiments, the stage classification engine 325 can map the feature vector and plurality of electronic activities to a specific stage as defined by the data source provider. In some embodiments, the stage classification engine 325 can map the feature vector and plurality of electronic activities to a normalized stage as defined by the system. The normalized stages can be used with different data source providers to provide a translatable staging system or nomenclature across the different data source providers. The stage classification engine 325 can maintain mappings between the normalized stages and the stages of the different data source providers. For example, the stage classification engine 325 can define five, normalized stages. A first data source provider can define a deal or opportunity as including 7 stages. A second data source provider can define a deal or opportunity as including 3 stages. The stage classification engine 325 , for the first data source provider, may map stages 1 and 2 to normalized stage 1, stage 3 to normalized stage 2, stage 4 to normalized stage 3, stage 5 to normalized stage 4, and stages 6 and 7 to normalized stage 5. Accordingly, the data source providers stages can be mapped to the normalized stages based on the tasks, requirements, or content of the stages rather than by the naming or numbering of the stages.

The stage classification engine 325 can map the electronic activities or feature vector to one of the five normalized stages. The indication of which normalized stage the electronic activities or feature vector was mapped to can be saved as a shadow stage. When syncing the shadow stage to the master stage of the data source provider, the stage classification engine 325 can map each of the normalized stages to the stages as defined by the data source provider. For example, the first normalized stage may be mapped to the first stage as defined by the data source provider and the second normalized stage may be mapped to the second and third stages as defined by the data source providers.

3. Systems and Methods for Linking Electronic Activities to Record Objects Maintained on Systems of Record

As described above, the system can maintain one or more shadow systems of record and shadow stages for each of the data source providers. The shadow systems of record can mirror the data source provider's systems of record at different instances in time. In some embodiments, as described above, electronic activities ingested by the system from a given data source provider are linked to the data source provider's shadow systems of record to enable the system to perform analysis and generate metrics regarding the data source provider's systems of record. In some embodiments, the system can synchronize the linked electronic activities between the shadow systems of record and the data source provider's master systems of record.

The record object manager 255 can maintain data regarding the record objects in the shadow systems of record and the master systems of record. The record object manager 255 can synchronize shadow systems of record and master systems of record for each of the data source providers. In some embodiments, to synchronize the shadow systems of record and the master systems of record the record object manager 255 can detect changes in the master systems of record. The changes can include added, deleted, or modified account record objects, opportunity record objects, or lead record objects or any other record objects. For example, the record object manager 255 can determine that a new account record object was generated at the master system of record and generate a corresponding copy of the new account record object at the shadow system of record. The corresponding copy of the new account record object at the shadow system of record can be a copy of the new account record object at the master system of record. Responsive to adding the new record object, the system can reprocess previously processed electronic activities to determine if the electronic activities should be matched with the new record object.

Detecting if modifications occurred to the record objects of the master system of record can include determining if one or more fields of the record object changed or if the linking of electronic activities with the record object changed. For example, during a previous synchronization cycle the record object manager 255 could link an electronic activity with a first record object at the master system of record. After the synchronization, a user at the master system of record may modify linkage to link the electronic activity with a second record object. In another example, the system can detect that an additional field value was added. For example, location data can be added to location field of a record object. The record object manager 225 can resynchronize the updated record object to identify potential new matches based on the added location data. The system can also reevaluate previous matches and determine if the location data makes the match with the previous matches more or less likely. The record object manager 255 can determine that the electronic activity was linked by the user to a different record object. The record object manager 255 can provide an indication of the change to the record object identification module 315 as feedback so that matching model 340 can update its machine learning models or matching strategies. In some embodiments, a user can add additional information or change information in a record object. Responsive to the change to the record object, the system can perform the rematching of the electronic activity with nodes and record objects.

The record object manager 255 can synchronize changes to the shadow systems of record to the master systems of record. For example, new linkings of electronic activities to record objects can be synchronized to the master system of record. Synchronizing the shadow system of record to the master system of record can include adding any linked electronic activities since the last synchronization cycle to the master system of record. The electronic activities can be linked to the same record object in the master system of record to which they are linked in the shadow system of record. In some embodiments, the record object manager 255 can add a flag or tag to the electronic activity when the electronic activity is synchronized from the shadow system of record to the master system of record. The flag can include an indication that the electronic activity was synchronized from the shadow system of record. In some embodiments, setting of the flag can cause the master system of record to prompt a user of the master system of record to confirm that the electronic activity was linked to the correct record object. In some embodiments, setting of the flag can cause the master system of record to provide a visual indication to a user of the master system of record that the flagged electronic activity was linked and synchronized from a shadow system of record. In some embodiments, the user can confirm or decline the addition of the linked electronic activity from the shadow system of record. Based on the approval or disapproval of the linked electronic activity, the system can update the matching strategies.

4. Systems and Methods for Generating a Multi-Tenant Master Instance of Systems of Record Using Single-Tenant Instances

In some embodiments, the system 200 or the system 9300 shown in FIG. 3 as described herein can generate a multi-tenant master instance of the systems of record. The multi-tenant master instance of the systems of record can include data from a plurality of master systems of record from a plurality of different data source providers, which can be referred to as tenants, or from the plurality of shadow systems of record, which can themselves be mirrors or copies of master systems of record from the different tenants. In some embodiments, the multi-tenant master instance of the systems of record can be a combination of the record objects from the separate shadow systems of record.

As described herein, the system 200 or the system 9300 shown in FIG. 3 can include shadow systems of record that correspond to respective master systems of record belonging to respective data source providers. In some embodiments, each of the shadow systems of record (and corresponding master systems of record) can include a plurality of record objects. The record object manager 255 can synchronize the record objects (or data therein) from each of the shadow systems of record or master systems of record from different tenants into a multi-tenant master instance of the systems of record. As such, the multi-tenant master instance of the systems of record can include all of the data included in each record object of the one or more shadow systems of record and the corresponding master systems of record. The multi-tenant master instance of the systems of record can be used to further enrich the node profiles maintained by the node profile manager 220 .

The multi-tenant master instance of the systems of record maintained by the system 200 or the system 9300 shown in FIG. 3 can be used to synchronize data between the master systems of record from the different tenants as well as improve the multi-tenant master system of record and individual master systems of record of the data source providers using parsed and normalized activity data received from electronic communications servers of the data source providers. Moreover, the system can update one or more node profiles maintained by the node profile manager 220 using the data from the record objects of the one or more master systems of record. The record object manager 255 can sync fields or data between node profiles and record objects such as, but not limited to, names, phone numbers, email address, domains, other contact information, address, D-U-Ns numbers, job titles, department IDs and other standard company or person information. In some embodiments, some types of systems of record can include record object (and data) types that are not included in other types of systems of record such that one or more of the systems of record may not support all record object types or data types maintained in the multi-tenant master system or record.

The record object manager 255 can populate data from the record objects from the individual master systems of record into the multi-tenant master instance of the systems of record. The record object manager 255 can also be configured to synchronize the record objects (or data contained therein) from the multi-tenant master instance of the systems of record back to the individual shadow systems of record enabling data to be shared between the different tenants. In some embodiments, each shadow system of record can include data that is obtained from a corresponding master system of record of a specific data source provider. This data can be shared with or accessed by the record object manager 255 , which can use the data from each of the shadow systems of record to update the multi-tenant master instance of the systems of record. Moreover, the record object manager 255 can further update the record objects included in the multi-tenant master instance of the systems of record from the node profiles of the nodes maintained by the node profile manager 220 . The record object manager 255 can then use the data included in the multi-tenant master instance of the systems of record, which has been updated from multiple systems of records and the node profiles, to update one or more of the shadow systems of records, which can then be used to update the corresponding master systems of records of the data source providers.

Data source providers or tenants that provide access to their systems of record can establish, via the system 9300 , one or more controls or settings to manage how the data in their respective systems of record are treated. In some embodiments, a tenant can select a setting that restricts the system 9300 from using the information included in the tenant's system of record to update the master instance of the systems of record maintained by the system 9300 . In some embodiments, a tenant can select a setting that restricts the system 9300 from using the information included in the tenant's system of record to update systems of record of other tenants maintained by the system 9300 . Furthermore, in some embodiments, a tenant can select a setting that restricts the system 9300 from using only certain information, such as sensitive or competitive information included in the tenant's system of record to update the master instance of the systems of record maintained by the system 9300 . The system 9300 can provide individual tenants control as to how the data included in a tenant's system of record can be updated, used and shared. For instance, a tenant can select a configuration setting that restricts the system 9300 from updating the tenant's system of record.

Each record object can include a plurality of fields that are populated with data regarding a given record object. As one example, a contact record object can include fields for first name, last name, email, mobile phone number, office phone number, among others. A user can populate the fields of the contact record object at the master system of record of one of the tenants (e.g., one of the data source providers). The record object manager 255 can synchronize the populated fields into the corresponding fields of the record object in the shadow system of record. The node profile manager 220 , described herein, can generate a first node (e.g., a member node). The node profile manager 220 can populate the fields of the first node with the data from the contact record object. In this example, a second user can populate the fields of a second contact record object in a second master system of record of a different tenant. Once synchronized to the system, the node profile manager 220 can generate a second node based on the second record object. In some embodiments, the node resolution engine 245 can determine that the first node and the second node are associated with the same contact. For example, the node resolution engine 245 can determine that the email fields of the first and second nodes are populated with the same email address. Determining that the first and second nodes are associated with the same contact, the node resolution engine 245 can merge the first and second nodes such that the merged node includes data from both the first and the second nodes. The record object manager 255 can sync the merged fields back to the respective record objects and master systems of record.

For example, and continuing the above example, the first user may have entered a phone number into a contact field but not a department identifier into a department field of the first user's respective contact record object. The second user may have entered the department identifier into the department field but not the phone number into the second user's respective contact record object. The record object manager 255 can determine the two contact record objects are associated with the same person and merge the data into the multi-tenant master instance of the systems of record maintained by the system 200 . In some embodiments, the node profile manager 220 can generate a node for the person in the node graph. To sync or otherwise update the merged data back to the respective contact record objects in the corresponding shadow system of record or the corresponding master system of record, the record object manager 255 can update the first user's contact record object with the department identifier and the second user's contact record object with the phone number. In some embodiments, the record object manager 255 can set a flag indicating the multi-tenant master instance of the systems of record as the source of the updated data in the record objects.

When syncing data between the different tenant systems of record and the multi-tenant master instance of the systems of record, the record object manager 255 can resolve conflicts between record objects and field values in the different systems of record that include different data. The record object manager 255 can resolve the conflicts using the above-described node graph. For example, the record object manager 255 can select between conflicting data by selecting the data that has highest likelihood of being accurate. The system 200 can, via the node profile manager 220 , maintain confidence scores of different values of fields to determine a likelihood of the value being accurate. In some embodiments, two values of the same field may both be accurate except one may be more current than the other. In such embodiments, the record object manager 255 can select the value that is accurate and more current. As described herein, a confidence score of a value can be based on contribution scores of one or more data points serving as evidence for the value. The contribution scores of the data points can be based in part on a recency of the data point and a trust score of the source indicating how trustworthy the source is. The trustworthiness of a source, such as a system of record, can be based on a health score of the source, which can be determined based on how many values of record objects of the system of record match values the system 200 knows to be true or accurate and how many values of the record objects do not match values the system 200 knows to be true or accurate.

The record object manager 255 can also resolve conflicts based on the time series of the data for the respective fields. For example, an email field that was recently updated by a user may indicate that the contact recently changed their email address and that the newer email address is an updated email address and not an inaccurate email address. Furthermore, such data may be re-confirmed by extracting the newer email address from an email signature in an electronic activity received from an electronic communications server associated with one of the data source providers. In some embodiments, the record object manager 255 can periodically execute batch jobs to synchronize the shadow and master systems of record. For example, each evening the record object manager 255 can synchronize the shadow and master systems of record. When synchronizing the record objects, the record object manager 255 can reprocess previously synced record objects (and the fields therein) to determine if the record objects should be updated. For example, based on the electronic activities processed during the day, the confidence score associated with a value of a field of a record object in the shadow system of record may have decreased below a predetermined threshold and the record object manager 255 can remove the value from the field of the record object of the shadow system of record during the daily sync.

In some embodiments, the synchronization between from the shadow system or record to the master system of record can be governed by privacy policies. For example, electronic activities, record objects, or data contained therein can be flagged to be labeled as private by the system or a user and may not be synced to the master system of record or to other tenant systems of record. In some embodiments, for little known or possibly sensitive data, the system may not sync fields back to systems of record until the data in the field is identified in a predetermined number of systems of record. For example, if a contact record object for John Smith from a first tenant lists the cell phone of John Smith, the cell phone number may not be synced to other tenants' master systems of record until the system 200 identifies the cell phone number in the contact record object of a predetermined number (e.g., 3) of tenant master systems of record, meaning that at least 2 other companies, connected to the system 200 also possess the phone number for John Smith.

5. Systems and Methods for Monitoring Health of Systems of Record

In some embodiments, the system described herein can be used to monitor the health of a system of record. The source health scorer 215 can monitor the health of the system of record and can calculate a health score for the system of record. The health score for the system of record can be used to determine or otherwise calculate a trust score for the system of record.

The health (or health score) of a system of record can provide an indication of the accuracy or completeness of a system of record's data. In some embodiments, the health score can be calculated with respect to the given system of record. For example, the health score can indicate that 20% of the records within the system of record are inaccurate. In some embodiments, the health score can be calculated with respect to the other data processing systems. For example, the health score can indicate that the completeness of the systems of record’ database is in the 97th percentile when compared to the completeness of other systems of record.

The health score can be based on the completeness of data in the system of record and/or the accuracy of the data in the system of record. For example, each record object in a system of record can include a plurality of fields. In some embodiments, the completeness of the system of record can be based on the ratio of the total number of populated standard fields to the total number of unpopulated standard fields. In some other embodiments, the completeness of the system of record can be based on the ratio of the total number of populated standard and supplemental fields to the total number of unpopulated standard and supplemental fields. In some embodiments, fields of record objects in systems of record can be classified as standard fields if they are common among different systems or record. Examples of standard fields can include company name, company phone number, company address as record objects across different systems of records for the same company may each include this information. Similarly, for record objects directed towards individuals, the standard fields can include first name, last name, work phone number, title as record objects across different systems of records for the same individual may each include this information. Other fields that are not standard fields can include custom fields or fields that include supplemental information that is not common across different systems of record can be classified as supplemental fields. Examples of supplemental fields can include fields such as opportunity contact role, years of experience, industry, as these fields may not be common across multiple systems of record.

In some embodiments, the health score can be based on the total count of the fields that are populated or just the total count of the standard fields that are populated. In some embodiments, the health score can also be based on the accuracy of the data populated into the standard fields. The system can determine the accuracy of the data in the standard fields by comparing the data to other instances of the data in other systems of record or in the multi-tenant master instance. For example, the system can determine that the first tenant system of record indicates a phone number for a given contact is 555-5555. A second and third tenant system of record can indicate that the phone number for the given contact is 555-4433. The system can determine that the phone number in the first tenant system of record is incorrect or not current because more tenants (with health scores satisfying a certain threshold) include the 555-4433 phone number. The accuracy of the data can also be based on the health score associated with data source from which the data was received. For example, the phone number may not be changed when contradicted by a source with a low health score. The accuracy of data can also be based on electronic activities and the confidence score of values of fields maintained in node profiles of the system 200 . The accuracy of data included in a system of record can be determined by comparing data included in the record objects of the system of record to information included in corresponding node profiles maintained by the system 200 . As described above, the node profiles can be updated with information extracted from electronic activities, which are unbiased and not self-reported or manually entered. Based on the comparison of the data included in the record objects of the system of record and the corresponding node profiles, the source health scorer can determine a health of the system of record. The health score can also be time dependent. For example, the health score can decay with time because the data in the system of record can become stale if the data is not updated or not checked. In some embodiments, newer data can have a greater probability of being accurate. For example, a newly entered job title for a contact may be accurate and indicate a promotion.

In some embodiments, the health score can be based on the links between record objects. For example, the system of record may require that each opportunity record object be linked with a least one contact record object. In these examples, the data fields within the record objects may be complete but the source health scorer 215 can reduce the system of record's health score or assign a lower health score to a system of record responsive to determining that the system of record does not include proper links between one or more opportunity record objects and corresponding contact record objects or any other record objects with which the one or more opportunity record objects should be linked. In some embodiments, the source health scorer 215 can base the health score on the accuracy of the links between the record objects of the system of record. For example, the system can process the electronic activities already linked to the system of record to perform historical matching based on using the techniques described herein to generate predictions for linking between the system or record's record objects. If the linkages between the record objects do not match the predicted matches, the source health scorer 215 can assign the system of record a lower health score.

The source health scorer 215 can also calculate or otherwise determine a trust score for each data point included in an array of a value of a node profile maintained by the system 200 or that contributes towards a value in a record object maintained by the system 200 . The trust score can be based on the source of the data point. In some embodiments, the trust score can be based on a health score of the source of the data point. For instance, some systems of record can be better maintained than others. The source health scorer 215 can perform a health check on a system of record to compute a health score for the system of record. The health score of the system of record can be used to assign a trust score. In contrast to data points whose source is a system of record, a data point whose source is an electronic activity ingested by the system 200 can have a higher trust score since electronic activities do not have health related issues as they are not manually input or updated. Systems of record are generally manually input and updated and therefore can include inaccuracies or may be stale resulting in lower health scores, and thereby, lower trust scores. In some embodiments, the source health scorer 215 can assign a trust score of 100% or a maximum rating to data points derived from electronic activities.

6. Systems and Methods for Generating Recommendations to Improve Health Based on a Node Graph Generated from Electronic Activity

In some embodiments, the system described herein can make recommendations based on the health and trust scores associated with a system of record or data source provider. The source health scorer 215 or other components of the system can generate the recommendations based on metrics of the systems of record, record objects therein, and the trust and health scores associated with the systems of record.

The source health scorer 215 can determine, for each field type, of number of standard fields not populated with data. For example, the source health scorer 215 can determine, for a given system of record, that 75% of the contact record objects include domain fields that are not populated with a website field value. In this case, the recommendation can be that the data source provider should update the domain fields of the contact record objects. In some occurrences, the system can automatically fill in a predetermined percentage of the missing field values in a given system of record to automatically improve the health score of the given system of record. Given a significant number of systems of record, connected to the multi-tenant system of record instance and the source health scorer 215 , such a system can systematically and continuously improve the health scores of all connected systems of record. Stated in another way, by generating or maintaining a multi-tenant system of record that can be used to update one or more master system of records maintained by customers or enterprises, a network of systems of record are created with automated data entry, thereby allowing each of the master systems of records to get updated. This will result in an improvement in the health and corresponding health score of each of the master systems of record through the network effect until all of the master systems of record are identical and, in some embodiments, pristine or perfect.

In some embodiments, the recommendations can indicate to a data source provider that the data within the system of record is stale or out of date. For example, if a first company is sold to a second company, the system can alert the data source provider to update the company or other information in its systems of record based on the sale of the first company. The recommendations can also include updates to field values, organizational charts, job titles, employment changes, and changes to an organization, such as mergers and acquisitions.

7. Systems and Methods for Filtering and Database Pruning

At least one aspect of the present disclosure is directed to systems and methods for filtering and database pruning. For example, the tagging engine 265 can assign tags based on the contents of the electronic activity, associations of the electronic activity with specific nodes, people, or companies, confidence and trust scores, information in record objects, or other information associated with the electronic activity. The rules used by the tagging engine 265 to generate tags can be used by one or more systems or components described herein. In some cases, the rules used by the tagging engine 265 to generate tags can generate filter tags, which can be configured to cause the system to block, delete, remove, drop or redact the electronic activity associated with the filter tag.

A system, such as the data processing system 9300 depicted in FIG. 3 , the node graph generation system 200 depicted in FIG. 4 , the tagging engine 265 depicted in FIG. 4 , the electronic activity linking engine 250 depicted in FIG. 9 , or one or more components thereof, may perform significant computationally extensive processing on various types of electronic activities or records as depicted in FIG. 3 . Since a large volume of electronic activities associated with sending or receiving electronic activities are received by the systems or components depicted in FIG. 3, 4 , or 9 in accordance with the process flow 9302 depicted in FIG. 9 , it can be challenging to efficiently process such data without causing excessive delay or latency issues. Further, databases associated with the systems and components depicted in FIGS. 3, 4 and 9 , as well as third-party databases with which the systems depicted in FIGS. 3, 4 and 9 can interface or communicate, may store or maintain records that may be stale, sensitive, corrupt, erroneous, or otherwise not needed or not wanted. As such, systems and methods of the present technical solution can provide filtering at an ingestion step 9305 as depicted in the functional flow diagram of FIG. 9302 , as well as scrubbing of records maintained in one or more databases, using parsing techniques, rules or machine learning.

The node graph generation system 200 can, via ingestor 205 , receive electronic activities. The electronic activities can include, for example, electronic messages or electronic calendar events and associated metadata. The ingestor 205 can receive the electronic activities from one or more data source providers 9350 , which can include an electronic messaging or mail server. The ingestor 205 , upon receiving the electronic activities, can format the metadata or otherwise manage or manipulate the data to facilitate further processing. The ingestor 205 can receive the electronic activities in real-time, asynchronously, on a periodic basis, based on a time interval, in a batch process or batch download, or responsive to a trigger of event.

The tagging engine 265 can, using one or more rules, policies, or techniques, tag the electronic activities such that the filtering engine 270 can apply a content filter to the tagged electronic activities to determine whether to filter out the electronic activity or authorize or approve the electronic activity for further processing, or redact a portion of the electronic activity. The filtering engine 270 can filter out the electronic activity, which can refer to or include redacting out sensitive or private parts of the electronic communications or preventing the entire electronic activity (or metadata thereof) from being forwarded to another component or memory of the system so that the electronic activity is prevented or blocked from further processing or storage. Preventing the electronic activity from being further processed or stored can reduce unnecessary computing resource utilization or memory utilization as well as prevent sensitive or private information from being carried from systems of record or activity data sources to other systems of record.

The electronic activity parser 210 can provide an alert, tag, notification, label or other indication of the reason the electronic activity was filtered out, blocked or deleted or redacted. The indication can indicate the type of filter or rule that triggered or caused the removal or redaction.

In some embodiments, the tagging engine 265 can tag the electronic activities with a filter tag based on one or more rules or policies. The filtering engine 270 can then filter out the electronic activities based on the assigned filter tag or cause another system or component to filter out the electronic activity responsive to the filter tag. For example, the tagging engine 265 , using technologies such as regular expressions, pattern recognition or NLP, can tag the electronic activity to cause the filtering engine 270 to block ingestion of the electronic activities or perform other filtering in downstream systems.

The system 200 can be configured to provide, via the filtering engine 270 , various types of filtering techniques that may be applied to electronic activities during ingestion, during processing of the electronic activities, or when attempting to match electronic activities to record objects of shadow system of records or master system of records.

As described herein, the filtering engine 270 can be configured to apply different types of filtering techniques. As will be described herein, the filtering engine 270 can apply filters based on the content included in electronic activities. Such filters may be referred to as content filters. The filtering engine 270 can also apply logic based filters based on one or more logic based rules for filtering electronic activities. Such filters may be referred to as logic based filters. In addition, the filtering engine 270 may apply filters to restrict matching of electronic activities to node profiles or restrict matching of electronic activities to one or more record objects of systems of records. Additional details regarding the different types of filters are provided herein.

As described herein, the filtering engine 270 can apply various filtering techniques at a user specific level, a company level, a system level, among others. These filtering techniques can be controlled by users, administrators of a company, administrators of the system 200 , among others.

A. Content Based Filtering

The filtering engine 270 can be configured to perform content filtering. Content filtering involves performing one or more actions on an electronic activity based on the content of the electronic activity. In some embodiments, the actions can include restricting ingestion of the electronic activity into the system 200 . In some embodiments, the action can include redacting a portion or all of the content included in the electronic activity. In some embodiments, the action can include restricting matching the electronic activity to a node profile or restricting matching the electronic activity to one or more record objects.

As described herein, the tagging engine 265 or electronic activity parser 210 can identify terms, text, content or other information in the body or metadata of the electronic activity. The tagging engine 265 can then apply a rule, policy, logic, machine learning algorithm, or natural language processing techniques to assign one or more tags to the electronic activity based on the identified terms, text, content or other information in the body or metadata of the electronic activity. The tag can include a content filter tag or other type of tag that the filtering engine 270 can use to perform content filtering. In some embodiments, the tagging engine 265 can be configured to apply a tagging policy that uses keywords and NLP to identify portions of electronic activities that satisfy one or more filtering rules. The tagging engine 265 can then tag such electronic activities with appropriate content filter tags that the filtering engine 270 can use to either redact portions of the tagged electronic activity, block the entire tagged electronic activity from being ingested, stored, or otherwise processed. In some embodiments, the filtering engine 270 can be configured to parse electronic activities to determine if the respective electronic activity includes any of one or more predetermined keywords, phrases, regex patterns or content in the electronic activity. Responsive to determining that the electronic activity includes any of one or more predetermined keywords, phrases, regex patterns or content in the electronic activity, the filtering engine 270 can restrict ingestion of the electronic activity into the system 200 .

In some embodiments, the tagging engine can tag the electronic activity with a tag indicating that the electronic activity includes sensitive information. In some embodiments, the tagging engine 265 can be configured to assign specific content filter tags based on the type of content detected in the electronic activity. For instance, the tagging engine 265 can assign a social security tag responsive to detecting a social security number (or any other number that matches a regex pattern corresponding to a social security number). In some embodiments, the tagging engine 265 can run one or more algorithms to identify various types of information for which a content filtering rule applies. Accordingly, the tagging engine 265 may determine if the electronic activity includes content that satisfies a content filtering rule, the tagging engine 265 may assign one or more content filter tags to the electronic activity indicating that the electronic activity includes content that may be subject to a content filtering rule. In some such embodiments, the content filter tag can include additional information that the system 200 or the filtering engine 270 can use to determine a basis for why the electronic activity satisfies the content filtering rule.

Based on the type of content filter tag assigned to the electronic activity, the filtering engine 270 can take one or more actions on the electronic activity. In some embodiments, the tagging engine 265 can tag the electronic activity with a content filter tag that the filtering engine 270 can use to determine what action to take on the electronic activity. For instance, in the example of the tagging engine 265 assigning a social security tag responsive to detecting a social security number (or any other number that matches a regex pattern corresponding to a social security number) in the electronic activity, the filtering engine can be configured to parse the electronic activity to identify the content that matches the regex pattern of the social security number and can apply a redaction policy to the electronic activity, causing the filtering engine 270 to redact the number from the electronic activity. It should be appreciated that the filtering engine 270 can redact the content by either obscuring the text with a visual marker, replacing the numbers with text indicating that the content is redacted, or other techniques for redacting text. The system can be configured to determine other types of sensitive information including credit card numbers, bank account numbers, date of births, or other sensitive or confidential information for which the filtering engine 270 may include one more filtering rules.

In some embodiments, the tag can indicate a type of data or field present in the electronic activity, such as a social security number or credit card number, in which case the filtering engine 270 can be configured with a policy to redact out sensitive information from electronic activities or filter out electronic activities tagged as containing credit card numbers or social security numbers or other sensitive or private information or perform any other action.

B. Tag Based Filtering

As described above, the filtering engine 270 can use one or more content filters or content filtering policies to filter the electronic activity. In some embodiments, the filtering engine 270 can be configured to filter electronic activities based on one or more tags assigned by the tagging engine 265 . Some of the tags assigned by the tagging engine 265 can be used to filter electronic activities, either from ingestion by the system 200 or from matching or linking the electronic activity to record objects of one or more systems of record. The tags assigned by the tagging engine 265 can be used for purposes other than filtering, for instance, for updating node profiles, determining connection strengths between nodes, understanding context of electronic activities, among others.

The tagging engine 265 can first tag all electronic activities based on numerous tagging methods as described herein. Thereafter, the filtering engine 270 can determine or choose to filter content out based on one or more tags, and otherwise determine or choose to allow further processing or storage of electronic activity based on other tags. The tagging engine 265 can determine to generate, apply or assign a tag, such as a filter tag, based on a regular expression. A regular expression (or regex or regexp) can include a sequence of characters that define a pattern. Example regular expressions can be configured to detect credit card numbers, social security numbers, license numbers, date of birth or any other combination of words or numbers. The tagging engine 265 can be configured with a regex for a credit card number. For example, a regex for a credit card number can be defined as a sequence of 13 to 16 digits, with specific digits at the start that identify the card issuer. The tagging engine 265 can be configured with predetermined digits of card issuers. The tagging engine 265 can apply the credit card number detection technique to the electronic activity (or metadata thereof) to detect or determine whether the electronic activity contains a credit card number. If the tagging engine 265 determines that the electronic activity contains a credit card number responsive to applying or searching for the credit card regex, the tagging engine 265 can apply a filter tag to cause the filtering engine to filter out the electronic activity or redact out the credit card number.

The tagging engine 265 can determine to apply a filter tag based on predetermined keywords. The keywords can indicate topics, concept or terms. Keywords can include, for example, “Credit Card No.” or “License No.” or “SSM” or “SSID”, etc. Keywords for topics to be filtered out can include, for example, “medical record”, “health record”, “doctor visit”, etc. The system 200 can use a master list of keywords that can be used to form a Global Keyword Based Content Filter that can be applied across all (new and existing) customers or users of the system 200 . It should be appreciated that the system 200 can be configured to generate, maintain, use or otherwise access keyword ontology or one or more machine learning models trained on keywords, clusters of text or other documents to build the master list of keywords. The content filter can be global or the content filter can be specific to a customer, user or other category or level. The system 200 can continue to update this global list of keyword based content filter. The system 200 can use filters based on a natural language processing technique to determine or identify synonyms, translations into other languages, or related keywords.

As described herein, a filter or filter tag can be applied or generated for a type of electronic activity. For example, a type of electronic activity can be adding a non-human participant (e.g., a room, device, projector, printer, display, etc.) to an electronic meeting event. The system 200 can use a filter to prevent or block further processing on an electronic activity associated with adding a non-human participant or prevent a non-human participant from being matched or from being created as a new record in the multi-tenant, shadow, or other systems of record.

C. Logic-Based Filtering

The filtering engine 270 can be configured to perform logic-based filtering in which the filtering engine 270 applies one or more logic-based rules to filter electronic activities. The logic filter can include a set of logic-based rules that can be used to filter electronic activities. The filtering engine 270 can be configured to execute one or more logic filtering policies by identifying structured metadata around an electronic activity or record object, and then blocking the electronic activity or record object from being ingested by the system 200 based on identifying the structured metadata. In some embodiments, the logic-based filtering can apply one or more rules or heuristics to restrict matching an electronic activity to a node profile or to one or more record objects of systems of record. In some embodiments, the logic-based filtering can restrict an electronic activity from being matched to a particular record object if the electronic activity was sent by a bot or is sent to a personal email address (such as a gmail address or a hotmail address, among others).

In one example, the system 200 , an administrator of the data source provider or a user of the system 200 can establish a logic-based filter to restrict ingesting electronic activities that satisfy one or more logic-based rules. In this example, the administrator of the data source provider can establish a logic-based filter to restrict ingestion of electronic activities that relate to one or more predetermined federal, state, or local government agencies, for instance, the CIA, NSA or FBI. The administrator can create one or more logic based rules that restrict the system 200 from ingesting the electronic activity into the system 200 if the electronic activity can be matched to an account type field having a value of government, or if the electronic activity is sent from or received by a domain name that matches a contains a domain name that matches any of the predetermined federal, state, or local government agencies, or if the contents of the email include certain predetermined character strings (for instance, CIA, NSA or FBI) or if the system 200 otherwise determines that the electronic activity is in any possible way related to the CIA, NSA or FBI.

D. Matching Filter

As described above, matching filters can be a type of restriction strategy or restriction policy that can be used to restrict electronic activities from being matched to record objects. These matching filters can be a part of, include or use one or more restriction strategies to prevent electronic activities from being linked to particular record objects or a particular system of record in general. In some embodiments, the matching filter can restrict matching electronic activities to record objects if the matching score between the electronic activity and the record object is less than or equal to a predetermined threshold (e.g., 70%, 60%, 50%, etc.). The matching score can indicate how closely the electronic activity matches the record object.

In some embodiments, users of a system of record can be configured to establish one or more restriction strategies or matching filters to restrict matching electronic activities to certain record objects. The user can be a user associated with the record object. In some embodiments, the user can be an administrator of the system of record and can establish one or more matching filters that can be used to restrict matching. For instance, an administrator can establish a matching filter that restricts matching electronic activities including a credit card number to certain record objects. In some embodiments, the matching filters can include multiple rules, which when satisfied, restrict the electronic activity from being matched to a certain record object. In some embodiments, the matching filters can be used to restrict electronic activities from being matched to record objects even if the record object was selected by one or more matching strategies 1100 and 1104 as described above.

E. NLP Based Tags and Filtering

The tagging engine 265 can determine to apply a filter tag, or the filtering engine 270 can determine to perform filtering, based on natural language processing. Natural language processing can refer to parsing metadata associated with the electronic activity to identify a meaning, concept, topic or other higher level concept associated with the metadata. Natural language processing techniques or algorithms can determine whether the electronic activity contains or is regarding a concept that is to be filtered out.

Natural language processing can be used to determine whether an electronic activity is a personal electronic activity or a business electronic activity. The filtering engine 270 can perform or execute the filter to redact out sensitive content, block or prevent further processing of personal electronic activities, and authorize or approve further processing of business related electronic activities. The tagging engine 265 when determining to apply a filter tag, or the filtering engine 270 when determining whether to perform filtering, can determine whether the electronic activity is personal based on a tag from the tagging engine or an email identifier used by the sender or recipient (e.g., a domain of the email address indicating personal use (or typically used for personal use) versus a domain indicating a business use or corresponding to an employer of the sender or recipient). The system 200 (e.g., via electronic activity parser 210 , tagging engine 265 , or filtering engine 270 ) can further determine personal or business electronic activities based on keywords, terms, topics, or concepts of the electronic activity (e.g., vacation-related versus order or purchase related). In some cases, the system 200 can determine that an electronic activity was sent using a personal electronic mail address, but the content of the electronic activity was to further a business objective. Thus, the system 200 can initially determine to block the electronic activity, but then determine to authorize or approve the electronic activity, thereby overriding an initial filter layer.

The system 200 can use a natural language processing engine that can be configured to parse text or keywords in different languages and determine synonyms or equivalent concepts across multiple languages. For example, the system 200 , using the natural language processing engine, can determine the equivalent of a keyword in English but in Japanese, and, therefore, be configured to perform tagging and filtering in multiple languages. The NLP engine can further expand a keyword into a number of synonyms or related keywords. Thus, even if the list of keywords used for filtering are not comprehensive, the system can still perform robust tagging and filtering.

F. Machine Learning Based Filtering

The system 200 can use machine learning to determine whether to filter an electronic activity. Machine learning can refer to a training set of data that includes metadata for electronic activities that are to be approved or authorized for further processing, as well as metadata for electronic activities that are to be filtered out based on both structured data and also on vectorized content of the communications. For example, if words in the electronic activities are converted into vectors with word2vec or similar technology, a machine learning model can be trained based on the content of the electronic activities alongside (not mutually exclusive) with natural language processing systems. The machine learning based filter can automatically establish, based on the training set, features, weights or other criteria that indicate whether or how an electronic activity should be tagged. In some embodiments, the system 200 can then determine if the electronic activity should be approved or filtered out based on the one or more tags. Thus, by using a machine learning technique, the system 200 can automatically determine features, weights or criteria to detect in metadata of the electronic activity to determine whether to tag and then filter out or authorize the electronic activity for further processing.

G. Filtering Based on Bot Detection

The machine learning filtering technique can include bot detection. The system 200 (e.g., electronic activity parser 210 , tagging engine 265 or filtering engine 270 ) can use or be configured with a bot detection machine learning algorithm to detect whether the electronic activity was sent by a bot—such as an automatic electronic activity generator. If the electronic activity was transmitted by a bot, the tagging engine 265 or the filtering engine 270 can tag the electronic activity with a tag indicating that the electronic activity was generated by a bot. In some embodiments, the filtering engine 270 can remove or prevent further processing or storage of the electronic activity (e.g., responsive to the tagging engine 265 tagging the electronic activity with a filter tag or a tag indicating that the electronic activity was transmitted by a bot). The system 200 can leverage or use the node graph to automate populating a blacklist of email addresses or other unique identifiers associated with bots through bot detection for syncing. For example, if an electronic activity is from a bot, that information may not be matched, linked or synced to a system of record. In some embodiments, the system 200 can detect bots based on the node graph since the node graph can indicate that a node of the sender bot is associated with edges of interactions between other nodes that indicate heavy one-way interactions across a large number of nodes. Thus, by measuring or detecting edge connection strength between the sender bot node and other nodes, or in some embodiments, comparing the number of inbound interactions (received electronic activities) and outbound interactions (transmitted electronic activities) between the sender bot node and other nodes, the system can classify non-human participants. For instance, non-human participants, such as no-reply@example.com generally transmit emails to a large number of other nodes but only receive a much smaller number of emails from other nodes, thereby allowing the system 200 to classify the email no-reply@example.com as a bot. The system 200 can use or apply similar techniques to detect and classify other types of non-human communication patterns and activity participants. For example, conference room email addresses only get added to meetings but never send or receive regular (non-meeting invite) emails and thus can be classified as Conference Room bots. Furthermore, the system 200 can identify a bot by parsing the email address or name associated with the email address. For instance, the bot detection algorithm can detect that an email address including “no-reply” is associated with a bot. In some embodiments, the bot detection algorithm can parse an electronic activity and determine, using NLP, that the email address associated with the sender is a bot based on language indicating not to send a reply to the electronic activity.

H. Using Feedback to Improve Filtering Techniques

The system 200 can tune or improve the machine learning techniques based on feedback. For example, upon applying the machine learning techniques to electronic activities, the system 200 can provide the filter decision to an administrator or other user of system 200 . The user can input whether the filter decision was correct or incorrect. If the filter decision was correct, the machine learning filter can maintain the weights or rules used to make the filter decision, or increase weights used to make the filter decision. If the filter decision was incorrect, the system 200 can modify the features, weights or criteria in an attempt to correct the filter decision. Similarly, the system 200 can use user input to modify features, weights, or criteria for other types of tagging or filtering, including, for example, natural language processing, rules, linking, or other logic flows that can be improved, enhanced or otherwise benefit from user input. In some embodiments, the machine can be configured to update the weights based on feedback without any intervention of a user or administrator.

I. Global Pattern Based Process Filter

Since end users can send/receive sensitive information from various systems (e.g., Human Resource systems, payroll systems, benefits systems, applicant tracking systems, recruiting systems, medical bill payment systems, phone bill payment systems, utility bill payment systems, banking or financial institutions, ride sharing systems, etc.) that could include highly sensitive information like payroll, benefits, hiring/termination letters, feedback on hiring a candidate or a cell phone bill which includes call details, the filtering engine 270 can block or prevent such electronic activities from being further processed or ingested by one or more components of the node graph generation system 200 or electronic activity linking engine 250 by maintaining a Global Pattern Based Process Filter which is applicable for all nodes. This can include a pattern based process filter that can identify rules to detect automated emails based on a ‘from’ and other fields; trigger a job to generate an automated systems blacklist; obtain a global blacklist from a storage or database; and apply a global pattern based process to filter out automated system electronic activity. Patterns can also be based on or applied to different fields or aspects of electronic activities, such as other data in an electronic message, meeting or calendar entry, telephone transcript, etc.

To generate such filters, the tagging engine 265 or filtering engine 270 can use bot detection techniques to identify bots automatically and blacklist the identified bots. Further, and in some embodiments, the tagging engine 265 can use natural language processing or machine learning techniques to automatically assess sensitivity of data from a new sender. For example, if a new source starts sending emails to multiple users, and greater than a threshold percentage (e.g., 70%, 80%, 90% or some other percentage) of the emails contain sensitive or confidential information (e.g., social security numbers), then the system 200 can automatically generate and apply a global filter to automatically blacklist this source.

J. Hierarchy of Filtering Rules

The system 200 (e.g., via electronic activity parser 210 , tagging engine 265 or filtering engine 270 ) can apply one or more layers of filters. The system 200 can apply the one or more layers of filters in parallel or serially. The system 200 can select one or more layers of filters to apply to an electronic activity based on a policy, rule or other logic. Layers of filters can refer to or include different types of filters or different configurations for filters. Layers of filters can refer to or include different type of filter controls or thresholds. Layers of filters can correspond to a hierarchy. For example, a first filter layer can include filtering policies, rules or logic established, based on or customized for a node in the node graph (e.g., a member node, an employee node, a user node, or an individual node). A second filter layer can include filtering policies, rules or logic established, based on or customized for an account. The account can refer to buyer account established by a seller for the buyer. A third filter layer can include filtering policies, rules or logic established, based on or customized for an organization. The organization can refer to or include a buyer organization, such as a company. A fourth filter layer can include filtering policies, rules or logic established by governmental agencies. A fifth filter layer (or master filter layer) can include filtering policies, rules or logic established, based on or customized for an administrator or provider of the node graph generation system 200 or electronic activity linking engine 250 . Different entities can establish various types of filters with various thresholds, controls, rules or policies.

As described below, the system 200 can be configured to apply different types of filtering policies. Each of the filtering policies outlined below can correspond to one of the filter layers described above.

K. Entity-Defined Filtering Policies

The system 200 can select one or more filters to apply to an electronic activity or all electronic activity ingested. The system 200 can select the one or more filters based on the metadata associated with the electronic activity. The system 200 can select the one or more filters to apply based on filtering rules defined for an account, a user, a group of users within an enterprise, an enterprise, or the system 200 .

i. Account-Specific Filtering Policies

The filtering engine 270 can maintain account-specific filtering policies that include one or more rules defined for one or more accounts. For instance, the filtering engine 270 can be configured to apply filters to emails either transmitted by or received by a specific account, such as an email account. In some embodiments, the account-specific filtering policy can include one or more rules to apply one or more content filters, logic-based filters or matching filters on electronic activities corresponding to the specific account. For instance, the filtering engine 270 can apply an account-specific filtering policy to an account, such as an email address corresponding to a bot. In one example, the account-specific filtering policy can include a rule to restrict matching any emails transmitted by the account to a record object of a system of record. The account-specific filtering policy can be defined by a user, an administrator of the enterprise, or an administrator of the system 200 .

ii. User-Specific Filtering Policies

The filtering engine 270 can maintain user-specific filtering policies that include one or more rules defined for specific users. For instance, the filtering engine 270 can be configured to apply filters to emails either transmitted by or received by a specific user. In some embodiments, the user-specific filtering policy can include one or more rules to apply one or more content filters, logic-based filters or matching filters on electronic activities corresponding to the specific user. For instance, the filtering engine 270 can apply a user-specific filtering policy that includes restricting certain electronic activities sent by the user from being linked to one or more systems of record or to the node profile of the user. For instance, the user may define a rule to restrict any emails between the user and their lawyer from being linked to one or more systems of record or to the node profile of the user. In another example, the user may define a rule to restrict emails sent to the users spouse at a given company to be linked to record objects of the company. The user-specific filtering policy of a user can be defined by a user, an administrator of the enterprise, or an administrator of the system 200 .

iii. Group-Specific Filtering Policies

The filtering engine 270 can maintain group-specific filtering policies that include one or more rules defined for specific groups of users. For instance, the filtering engine 270 can be configured to apply filters to emails either transmitted by or received by users defined within a specific group of users. In some embodiments, the group-specific filtering policy can include one or more rules to apply one or more content filters, logic-based filters or matching filters on electronic activities corresponding to the specific group of users. For instance, the filtering engine 270 can apply a group-specific filtering policy that includes restricting certain electronic activities sent by a user of the group from being linked to one or more systems of record or to the node profile of the user. For instance, a user of the group or an administrator of the enterprise associated with the group or the system 200 may define a rule to redact text included in any emails between one or more users of the group before storing the electronic activity in the system 200 or any record object with which the electronic activity is matched. The group-specific filtering policy of a user can be defined by a user, an administrator of the enterprise, or an administrator of the system 200 .

iv. Enterprise-Specific Filtering Policies

The system 200 can select the one or more filters to apply based on enterprise-specific filtering policies. For example, an administrator of a first enterprise or customer of the system 200 can indicate to remove electronic activity accessed via a mail server of the first customer having metadata that matches a regex for a credit card number, whereas an administrator of a second enterprise or customer of the system 200 can indicate to remove electronic activity accessed via a mail server of the second customer having metadata that matches a keyword or regex pattern for a credit card number. In this example, the system 200 applies enterprise-level filtering rules that may be defined by specific enterprises on how to process electronic activities received from their electronic communications servers. The enterprise-specific filtering policy of a user can be defined by an administrator of the enterprise or the system 200 .

v. System Defined Filtering Policies

The filtering engine 270 can maintain system-specific filtering policies that include one or more rules defined for the system 200 . For instance, the filtering engine 270 can be configured to apply filters to all electronic activities processed by the system 200 . For instance, the system-specific filtering policy can include one or more rules to apply one or more content filters, logic-based filters or matching filters on electronic activities accessible by or ingested by the system 200 . For instance, the filtering engine 270 can apply a system-specific filtering policy that includes tagging all electronic activities that include numbers matching a credit card regex pattern with a credit card tag indicating that the electronic activity includes a credit card. The system 200 can then be configured to determine if the filtering engine 270 is to take any additional actions on the electronic activity with the credit card tag, for example, redacting the credit card information, restricting matching the electronic activity to record objects, among others. The system-specific filtering policy can be defined by an administrator of the system 200 .

L. Sensitive Information Filter

The system 200 can determine to filter out an electronic activity responsive to detecting sensitive information or data in or associated with the electronic activity. For example, upon detecting or identifying a social security number or a financial account number in the electronic activity, or a tag indicating sensitive information, the system 200 can filter out the electronic activity. This is an example of one type of content filtering.

M. Source Based Filtering

The system 200 can select the filter to apply based on who is a sender or recipient of the electronic activity or a source of the electronic activity (for example, whose mail server the electronic activity came from). In some cases, the system 200 can select one or more filters to apply or apply all filters that are configured or compatible with the electronic activity. This is similar to the user-specific filtering policy described above. In one example, the data source provider of a system of record can establish a rule that causes the system 200 to restrict any emails coming from a craigslist.org domain from being matched to any record object of the system of record.

N. Previous Communication Activity Filter

The system 200 can filter out the electronic activity if there have been no previous electronic activities between the sender and recipient of the electronic activity. However, the system 200 can authorize or approve the electronic activity if electronic activities have occurred between a node in close proximity in the node graph to the sender node or recipient node. In some embodiments, two nodes may be in close proximity in the node graph if they have a connection strength above a predetermined threshold. In some embodiments, two nodes may be in close proximity in the node graph if they have either exchanged electronic activity with each other or with a predetermined number of connection nodes in common. Thus, the system 200 can determine to approve or filter out electronic activities based on the extent to which prior electronic activities between the sender and recipient have occurred (e.g., a metric associated with one or more prior activities satisfying a threshold).

O. Geographic Location Based Filters

The system 200 can select filters based on a geographic location inferred for a node associated with the electronic activity. In some embodiments, a geographic location can be inferred for a node based on detecting a time zone based on timestamps of electronic activities transmitted by the sender node. In some embodiments, the filtering engine 270 can be configured to apply one or more filtering rules bas