THIRD PARTY APPLICATION ACTIVITY DATA COLLECTION

• US 20150089354A1
• Filed: 12/04/2014
• Published: 03/26/2015
• Est. Priority Date: 02/10/2013
• Status: Active Grant

• Current Assignee: Wix.com Ltd.
• Original Assignee: Wixpress Ltd. (Wix.com Ltd.)
• Inventors: Achsaf, Nitzan, Abrahami, Yoav, Bloch, Kfir
• Granted Patent: US 11,669,584 B2
• Time in Patent Office: Days
• US Class Current: 715/235
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking

Abstract

A system includes at least one hub to coordinate at least one activity message between a website and at least one third party application where the at least one activity message has a standardized format, and an activity coordinator to listen to the at least one activity message and at least to add data extracted from the at least one message to a stream associated with at least one of an identified contact and an anonymous contact and where the at least one of an identified contact and an anonymous contact is a user of the website. The system also includes a contacts coordinator to retrieve and analyze contact related information from the stream and to enrich previously held information for the contact and at least one database to store the activity streams and the contact related information for use by the website and by the contact.

Claims

1. A system implementable on a website via a client/server system having at least one processor to process instructions defining said system, said system comprising:

at least one hub to coordinate at least one activity message between said website and at least one third party application wherein said at least one activity message has a standardized format;

an activity coordinator to listen to said at least one activity message and at least to add data extracted from said at least one message to a stream associated with at least one of an identified contact and an anonymous contact and wherein said at least one of an identified contact and an anonymous contact is a user of said website;

a contacts coordinator to retrieve and analyze contact related information from said stream and to enrich previously held information for said contact; and

at least one database to store said activity streams and said contact related information for use by said website and by said contact.

2. The system according to claim 1 and wherein said at least one hub comprises at least one of:

a router and tracker to route and track said at least one activity message between said website and said at least one third party application;

a private policy enforcer to enforce privacy policy between said website and said at least one third party application;

a translator and adapter to apply pre-specified at least one message translation and content adaptation rules between said website and said at least one third party application;

a private data proxy to implement at least one of a private data proxy and private data replacement and to enforce user permission field limitations between said website and said at least one third party application; and

a validator and signer to validate the signature of said at least one activity message using the incoming key of said at least one third party application, to translate the external ID associated with said at least one activity message with an internal said website ID and to sign an outgoing said at least one activity message using the outgoing key of said at least one third party application.

3. The system according to claim 1 and wherein said activity coordinator comprises at least one of:

a stream creator to identify said contact associated with said at least one activity message and to create said stream of data if no associated contact exists;

a stream merger to merge data from said at least one activity message to an existing stream and data from at least two of said activity streams into a single stream; and

a log creator to log activity data from said activity stream into said at least one database.

4. The system according to claim 1 and wherein said contacts coordinator comprises at least one of:

a data extractor to extract contact related information from at least one of said at least one activity message, said stream, other contacts and external sources.

a data merger to merge at least two contact information records wherein said records have an association with the same identified contact and to merge said extracted contact related information to that of an existing contact according to predefined merging rules;

a contact handler to create at least one of an identifiable new contact and an anonymous contact and to track contact activity during a session of said website; and

a data and permissions handler to handle the privacy protection and permissions of extracted contact related information.

5. The system according to claim 2 and wherein said router and tracker supports routing of said at least one activity message using said at least one third party application specified listening queries.

6. The system according to claim 3 and wherein said stream merger comprises an activity-to-stream merger to merge said data into said stream associated with said identified contact and a stream-to-stream merger to merge at least two separate streams into a single stream.

7. The system according to claim 6 and wherein said stream-to-stream merger comprises at least one of a horizontal stream merger to merge said at least two separate streams according to a identified common contact and a vertical stream merger to merge a stream created for an anonymous contact with a stream associated with a registered contact user upon a login or registration which may connect the two.

8. The system according to claim 4 and wherein said data merger comprises at least one of:

a contact identifier to at least one of;

locate identical primary ID field values in at least two of said contact information records, locate primary key field values within in least two of said contact information records which are identical when normalized, identify site users using a cookie, identify a site user using site login for registered users and identify a site user through a social login for site users with an account associated with a social network;

a uniter to unite contact information using at least one of linguistic, syntax, text analysis and consultation with external data sources and services;

a contradiction resolver to resolve contradictions between contact records according to predefined rules;

a list value creator to create list value fields to define a clear precedence between said contact records;

a horizontal contact merger to merge two unrelated contacts due to a detected common primary ID; and

a vertical contact merger to merge an anonymous contact with a contact associated with a registered user upon login or registration which may connect the two.

9. The system according to claim 8 and wherein said horizontal contact merger comprises a virtual merger to maintain at least two contact records as separate and to link them together so they are marked as representing the same contact.

10. The system according to claim 8 and wherein said vertical contact merger comprises a virtual merger to maintain an anonymous contact and a contact associated with a registered user as separate and to link them together so they are marked as representing the same contact.

11. The system according to claim 2 and wherein said user permission field is at least one of said website determined and said website owner determined.

12. The system according to claim 1 and wherein said standardized format is at least one of defined by a predefined schema, inheritance, a call back link, encoded and defined by said at least one third party application or based on external formal, industry or de-facto standard.

13. A method implementable on a website via a client/server system having at least one processor to process instructions defining said method, said method comprising:

coordinating at least one activity message between said website and at least one third party application wherein said at least one activity message has a standardized format;

listening to said at least one activity message and at least adding data extracted from said at least one message to a stream associated with at least one of an identified contact and an anonymous contact and wherein said at least one of an identified contact and an anonymous contact is a user of said website;

retrieving and analyzing contact related information from said stream and enriching previously held information for said contact; and

storing said activity streams and said contact related information for use by said website and by said contact.

14. The method according to claim 13 and wherein said coordinating comprises at least one of:

routing and tracking said at least one activity message between said website and said at least one third party application;

enforcing privacy policy between said website and said at least one third party application;

applying pre-specified at least one message translation and content adaptation rules between said website and said at least one third party application;

implementing at least one of a private data proxy and private data replacement and enforcing user permission field limitations between said website and said at least one third party application; and

validating the signature of said at least one activity message using the incoming key of said at least one third party application, translating the external ID associated with said at least one activity message with an internal said website ID and signing an outgoing said at least one activity message using the outgoing key of said at least one third party application.

15. The method according to claim 13 and wherein said listening and said at least adding comprise at least one of:

identifying said contact associated with said at least one activity message creating said stream of data if no associated contact exists;

merging data from said at least one activity message to an existing stream and data from at least two of said activity streams into a single stream; and

logging activity data from said activity stream into said at least one database.

16. The method according to claim 13 and wherein retrieving and analyzing comprise at least one of:

extracting contact related information from at least one of said at least one activity message, said stream, other contacts and external sources;

merging at least two contact information records wherein said records have an association with the same identified contact and merging said extracted contact related information to that of an existing contact according to predefined merging rules;

creating at least one of an identifiable new contact and an anonymous contact and tracking contact activity during a session of said website; and

handling privacy protection and permissions of extracted contact related information.

17. The method according to claim 14 and wherein said routing and tracking supports routing of said at least one activity message using said at least one third party application specified listening queries.

18. The method according to claim 15 and wherein said merging comprises merging said data into said stream associated with said identified contact and merging at least two separate streams into a single stream.

19. The method according to claim 18 and wherein said merging said data into said stream associated with said identified contact and merging at least two separate streams into a single stream comprises at least one of horizontally merging said at least two separate streams according to a identified common contact and vertically merging a stream created for an anonymous contact with a stream associated with a registered contact user upon a login or registration which may connect the two.

20. The method according to claim 16 and wherein said merging at least two contact information records comprises at least one of:

locating identical primary ID field values in at least two of said contact information records, locating primary key field values within in least two of said contact information records which are identical when normalized, identifying site users using a cookie, identifying a site user using site login for registered users and identifying a site user through a social login for site users with an account associated with a social network;

uniting contact information using at least one of linguistic, syntax, text analysis and consultation with external data sources and services;

resolving contradictions between contact records according to predefined rules;

creating list value fields to define a clear precedence between said contact records;

horizontally merging two unrelated contacts due to a detected common primary ID; and

vertically merging an anonymous contact with a contact associated with a registered user upon login or registration which may connect the two.

21. The method according to claim 20 and wherein said horizontally merging comprises virtual merging to maintain at least two contact records as separate and linking them together so they are marked as representing the same contact.

22. The method according to claim 20 and wherein said vertically merging comprises virtual merging to maintain an anonymous contact and a contact associated with a registered user as separate and linking them together so they are marked as representing the same contact.

23. The method according to claim 14 and wherein said user permission field is at least one of said website determined and said website owner determined.

24. The method according to claim 13 and wherein said standardized format is at least one of defined by a predefined schema, inheritance, a call back link, encoded and defined by said at least one third party application or based on external formal, industry or de-facto standard.