Payload Unit is working good!
Playing with adding add. parameters and sorting. See link below in playload.
It’s nice to be able to apply keyword and then titles again, and managing the AD units.
I’m still messing with the Contextual Unit on a Widget and sometimes it’s definitely in the right “SearchIndex” sometimes it’s way off. It’s great as it covers all content (static & dynamic) with 1 AD Unit without having to think about it. But that’s me being lazy.. I will likely be using a Payload or setup a Native Shopping ad. in most instances now.
Even AZ Recommendation ADs sucks at this, I haven’t looked too deep into your code to see how your parsing content, but scraping/parsing the page content and populating a payload is going to be the most robust method.
Maybe a Global/Sitewide default variable for the “SearchIndex”: could be enabled and it would apply to the other Ad. Unit types. ie, “SearchIndex”:”SportsAndOutdoors” In my case.
Thanks for the super-fast update on this.
P.S. These should be PRO (Paid) features.
######################
#payload sample#
######################
{
“Keywords”: “Kayak Paddle”,
“Resources”: [
“BrowseNodeInfo.BrowseNodes.SalesRank”,
“BrowseNodeInfo.WebsiteSalesRank”,
“CustomerReviews.StarRating”,
“Images.Primary.Large”,
“ItemInfo.Title”,
“Offers.Listings.DeliveryInfo.IsFreeShippingEligible”,
“Offers.Listings.Price”
],
“SearchIndex”: “SportsAndOutdoors”,
“Title”: “Kayak Paddle”,
“SortBy”: “Featured”, <———- This is nice — https://webservices.amazon.com/paapi5/documentation/search-items.html#sortby-parameter
“Properties”: {
“key1”: “value1” <— Still messing with this.
},
“PartnerTag”: “XXXXXXXXXXXXXXXXXX”,
“PartnerType”: “Associates”,
“Marketplace”: “www.amazon.com”,
“Operation”: “SearchItems”
}