Search and Browse Pages

general in both search and browse pages, we have a high level of context (via organic products), and clear customer intent (via the search query or the category they are browsing) it's important to set the ads to closely match this intent, especially in grid our general recommendation is to prioritise fluid and/or organic ads above the fold, with an optional fallback of additional inventory slots in less visible positions below the fold across both search and browse, the impact of showing relevant ads in high grid positions is stark position wise, fluid (organic) ads can drive up to 5 5x higher engagement than traditionally placed static ads search pages in grid spa search pages are among the highest intent and highest context pages generally found on ecommerce site pentaleap's recommendation is to utilize fluid ads in particular within search pages we generally recommend limiting additional inventory slots to lower scroll positions, since the qualifying criteria for these ads is broader, and may not directly match the customer intent, generating a lower click through rate additionally, consider increasing the floor price for the additional inventory slots, to offset the click loss example setup fluid, desktop in grid search default products per page 24 max ads per page 8 max fluid ads 8 custom tiles additional inventory slots 12,16,20,24 bid impact medium outcome organically relevant ads will have high visibility less relevant ads can still be shown to maintain impression volume and allow cross selling, but do not impact the initial page experience note when considering eg mobile web or app with single column scroll, custom tile slots can generally be placed slightly higher browse pages in grid spa browse pages also benefit from fluid ads, but are generally broader than the result set in search as such, we recommend a higher bid impact value for browse, and higher/more additional inventory slots in thead request, ensure to call the browse page category in the categories object, to bring all potential sponsored ads from the category into consideration default products per page 24 max ads per page 8 max fluid ads 8 custom tiles additional inventory slots 2,4,6,8,12,16,20,24 bid impact high outcome only ads from the category are allowed, but will be highly visible organically relevant ads have an advantage and will be given the highest visibility, but we also look for ads with a high bid to maximize yield carousels and display ads many retailers augment their in grid ads with carousels and/or banner ads on search and browse for search pages, an additional sponsored products carousel above the fold can be highly effective bottom of page carousels are also possible, but can be expected to produce relatively low traffic sponsored brand ads are particularly attractive to advertiser in search pages, and can work well above the main grid pentaleap's relevancy tech ensures any sponsored brand candidates are closely related to the customer need and intent, and we advise switching allow category targeting off for search pages the same rules are typically true of browse pages, but here we recommend that banners ads have allow category targeting activated example ad request format here is a sample ad request structure the response includes both sponsored product and display ads in batched call, for a search page i e you can call multiple ad units at once, and those ad units can be both spa and display/sponsored brand ads { "user" { "id" "test" }, "adunitcontext" { //page context goes into adunitcontext it's shared by all ad units "searchquery" "shampoo", "products" \[ //ordered list of gtins/skus organically on the page max 200 (can contain multiple ui pages) { "gtin" "abc" }, { "gtin" "123" }, { "gtin" "def123" }, { "gtin" "345" }, { "gtin" "123" }, { "gtin" " " }, { "gtin" "xyz" } ] }, "adunits" \[ //max 6 per request { "adunitid" "\[spa ad unit id 1]"//search main grid }, { "adunitid" "\[display ad unit id 1]" //display above the fold search } ] } the response returns sponsored and in some cases organic content to be rendered, plus additional information required for rendering and reporting sample response { "adunits" \[ { "adunitid" "\[spa ad unit id 1]", //returns spa ad unit information + organic information "positions" \[ { "gtin" "string", "sponsored" false, "kind" "string", "ext" { "attr1" "val1", "attr2" "val2" } }, { "gtin" "string", "sponsored" true, "kind" "string", "beaconurls" \[ "string" ], "clickurls" \[ "string" ], "ext" { "attr1" "val1", "attr2" "val2" } }, { "adunitid" "\[display ad unit id 1]", //returns display ad unit information "positions" \[ { "banner" { "300x250" { "asseturl" "linktoasset com", "clickurls" \[ "https //trackerurl" ], "beaconurls" \[ "https //trackerurl" ], "ext" { "type" "image" } }, "970x250" { "asseturl" "linktoasset com", "clickurls" \[ "https //trackerurl" ], "beaconurls" \[ "https //trackerurl" ], "ext" { "type" "image", "adcopy" "this is an ad copy" } }, "dynamic" { "asseturl" "linktoasset com", "clickurls" \[ "https //trackerurl" ], "beaconurls" \[ "https //trackerurl" ], "ext" { //contains additional ad information for rendering display ad "type" "html image link" } } }, "kind" "display", "targeturl" "https //pentaleap com", "sponsored" true } ] } ] }