Systems and methods for creating synchronized data structures for synchronized groups

1. A system, comprising:

one or more processors coupled to memory, the one or more processors configured to:

receive, from a first client device associated with a first player profile identified as a host of a synchronized group, a request to create a contest for the synchronized group, the request identifying an interaction type to be performed for participation in the contest;

generate the contest within the synchronized group, the contest defining criteria for participation including at least the interaction type;

receive an indication that a second player profile identified in the synchronized group performed an interaction having the interaction type;

determine that the second player profile includes a permission setting authorizing performance of actions to be included in the synchronized group;

update a data structure corresponding to a feed of the synchronized group to include data corresponding to the interaction and the second player profile responsive to determining that the second player profile includes the permission setting;

receive, from the first client device, a second request to view the feed of the synchronized group; and

provide, to the first client device, the feed of the synchronized group including a content item generated based on the data and comprising an identifier of the contest and the second player profile.

2. The system of claim 1 , wherein the one or more processors are further configured to:

receive, from a second client device associated with the second player profile, a third request to perform the interaction; and

generate a data record corresponding to the interaction performed via the second player profile.

3. The system of claim 2 , wherein the one or more processors are further configured to:

update the data structure corresponding to the feed of the synchronized group based on the data record.

4. The system of claim 1 , wherein the one or more processors are further configured to receive a fourth request to revoke the permission setting of the second player profile authorizing performance of actions to be included in the synchronized group.

5. The system of claim 1 , wherein the request further identifies at least one criteria for the interaction for participation in the contest.

6. The system of claim 1 , wherein the one or more processors are further configured to:

determine that the interaction performed via the second player profile satisfies the criteria for the contest; and

update the data structure corresponding to the feed of the synchronized group responsive to determining that the interaction satisfies the criteria.

7. The system of claim 1 , wherein the one or more processors are further configured to:

receive an expiration time for the contest; and

update the synchronized group with an indication that the contest is expired responsive to determining that a current time exceeds the expiration time.

8. The system of claim 1 , wherein the one or more processors are further configured to:

determine a score for the second player profile based on an outcome corresponding to the interaction; and

generate contest results for the contest of the synchronized group based on the score.

9. The system of claim 1 , wherein the one or more processors are further configured to:

restrict updates to the contest responsive to updating the contest based on a threshold number of interactions satisfying the criteria of the contest.

10. A method, comprising:

receiving, by one or more processors coupled to memory, from a first client device associated with a first player profile identified as a host of a synchronized group, a request to create a contest for the synchronized group, the request identifying an interaction type to be performed for participation in the contest;

generating, by the one or more processors, the contest within the synchronized group, the contest defining criteria for participation including at least the interaction type;

receiving, by the one or more processors, an indication that a second player profile identified in the synchronized group performed an interaction having the interaction type;

determining, by the one or more processors, that the second player profile includes a permission setting authorizing performance of actions to be included in the synchronized group;

updating, by the one or more processors, a data structure corresponding to a feed of the synchronized group to include data corresponding to the interaction and the second player profile responsive to determining that the second player profile includes the permission setting;

receiving, by the one or more processors, from the first client device, a second request to view the feed of the synchronized group; and

providing, by the one or more processors, to the first client device, the feed of the synchronized group including a content item generated based on the data and comprising an identifier of the contest and the second player profile.

11. The method of claim 10 , further comprising:

receiving, by the one or more processors, from a second client device associated with the second player profile, a third request to perform the interaction; and

generating, by the one or more processors, a data record corresponding to the interaction performed via the second player profile.

12. The method of claim 11 , further comprising updating, by the one or more processors, the data structure corresponding to the feed of the synchronized group based on the data record.

13. The method of claim 10 , further comprising receiving, by the one or more processors, a fourth request to revoke the permission setting of the second player profile authorizing performance of actions to be included in the synchronized group.

14. The method of claim 10 , wherein the request further identifies at least one criteria for the interaction for participation in the contest.

15. The method of claim 10 , further comprising:

determining, by the one or more processors, that the interaction performed via the second player profile satisfies the criteria for the contest; and

updating, by the one or more processors, the data structure corresponding to the feed of the synchronized group responsive to determining that the interaction satisfies the criteria.

16. The method of claim 10 , further comprising:

receiving, by the one or more processors, an expiration time for the contest; and

updating, by the one or more processors, the synchronized group with an indication that the contest is expired responsive to determining that a current time exceeds the expiration time.

17. The method of claim 10 , further comprising:

determining, by the one or more processors, a score for the second player profile based on an outcome corresponding to the interaction; and

generating, by the one or more processors, contest results for the contest of the synchronized group based on the score.

18. The method of claim 10 , further comprising restricting, by the one or more processors, updates to the contest responsive to updating the contest based on a threshold number of interactions satisfying the criteria of the contest.