Explore

PRD - Horizontal feed priority

Objective -

Creating a centralised tech serving platform to serve horizontal IG / IC components per feed with a consistent / systemic vertical catalog gap index

Problem context -

Browsing experience currently heavily relies on horizontal REs to help users channelise subdued intent / generate intent towards L0 DTB objectives. This includes mid feed visual / interstitial filters, feed-in-feed product widgets (Other REs / components to be introduced as part of intent generation KR)

Manual set up of these IC / IG REs has risks pertaining to cluttering of these components near adjacent slots

The non centralised serving of these widgets / filters leads is a blocker in terms of stress testing position of such components at a user cohort / persona level

Monitoring and updates to these horizontal REs is manually driven by Biz resulting in higher operational effort

Long term - Approach 1

Create an unified FHC (Feed horizontal component) setup and monitoring service which -

Identifies and flags horizontal components coming in across service from -

Widget infra

Filter infra

Any other horizontal feed component / card introduced for IC / IG at a later point

To do these, get a flag added for FHC at admin as a mandatory input when new widgets or filter labels are getting added

For already existing components, backfill the flag for all

Search widgets / Banners (Manually setup)

FIF widgets

IF / Mid feed filters

Proposed schema for this -

Horizontal component type - {’widget’,’filter’ etc}

Horizontal component ID - {’widget_id’,’filter_label_id’}

Feed name - {’pst’,’clp-name’,’collection-name’}

Feed ID - {’search-session-id’,’clp-id’,’collection-id’}

Priority / Position - Stack rank of horizontal components (1→2→3...n) coming from admin

Valid {0/1} - To track or later invalidate a horizontal feed component for a respective feed

Variant ID / Name

Audience ID

Maintains mapping of horizontal element position which can be configured at a variant and audience level and also be used to scale up to platform

Element position to be powered basis -

Heuristic / DS inputs

Tech default ranking

Short term - Approach 2

Persist configurable minimum catalog distance on Zookeeper with a variant config to test A/B on different vertical gaps, let’s say X

Update the position on client side whenever vertical gap <X between any 2 horizontal components (i.e. IF and FIF widgets)

Eg - Scenario 1 -

IF at position 6 / 12 / 18 / 24

FIF at position 9 / 15 / 36

Updated position with X=6

Pos1 - IF at 6

Pos 2 - FIF at 12

Pos 3 - IF at 18

Pos 4 - FIF at 24

Pos 5 - IF at 30

Pos 6 - FIF at 36

In case of conflicting position between IF and FIF, prioritise IF

In case the vertical distance between adjacent components >X, then use default positions

MoM -RBAC for FIF -

RBAC for FIF - Restrict FIFs position 1-10 first catalogs - Check feasibility for this

How to implement this for PDP recos / FY - To be picked from strategic pod

Want to print your doc?
This is not the way.

Try clicking the ··· in the right corner or using a keyboard shortcut (

CtrlP

) instead.