Variable ProfileGridEntrySchemaConst
ProfileGridEntrySchema: Struct<
{
authorId: optionalKey<String>;
followsAuthor: optionalKey<Boolean>;
mediaId: String;
mediaType: optionalKey<Number>;
page: $Array<
Struct<
{
authorId: optionalKey<String>;
dashManifest: optionalKey<String>;
id: String;
mediaType: optionalKey<Number>;
takenAt: optionalKey<Number>;
trackingToken: optionalKey<String>;
videoDuration: optionalKey<Number>;
},
>,
>;
pageCursor: optionalKey<
Struct<{ gridItemsCursor: String; maxId: String }>,
>;
position: Number;
takenAt: optionalKey<Number>;
trackingToken: optionalKey<String>;
userId: String;
videoDuration: optionalKey<Number>;
},
> = ...
One tile of the profile's media grid, as the page the tile opens into sees it: the media, its position in the grid and the whole grid page it belongs to. The page travels with every tile because the posts feed's first page is answered by the grid's own answer — the recorded app sends no request on the tap (the 2026-10-23 profile-video recording's
ContextualFeedFragment) — and the feed's own next page is the same query with the grid answer's continuation, which the tile carries too.The telemetry facts the posts feed's video view reports are the media answer's: its author, when it was taken, its organic tracking token and a video's duration; the feed's view also reports the viewer's relationship to the profile, which the tile carries from the profile's friendship answer.