Middle Home Page Banner ads require a simple "context' to be sent to Project Agora Commerce. A "context" is a bit of code that defines the conditions under which an ad is shown to a customer.
Middle Home Page Banner Ads use a similar context to Product Ads, you will need your contentStandardId and bannerSlotIds.
The placement attribute for Middle Home Page Banner ads has the value "banner-home".
The Middle Home Page Banner Ads use the "Agora Home" content standard.
You will receive your contentStandardId and bannerSlotIdsfrom Project Agora Commerce once your content standard is generated.
Please note that both contentStandardId and bannerSlotIds are different for the Middle Home Banner Ad format and will be provided by Project Agora Commerce in the beginning of the integration
The bannerSlotIdsprovided in the examples below are not the ones that will be used.
Context:
Below are the values needed to generate a middle home page ad:
No customer information or cart items are necessary in this simple context. The simple context consists only of necessary filters.
In order to serve a Banner Ad on your website you will have to use as a creative image the imageUrl , and as a landing page the linkUrl as taken from the above ad response. The id also from this response shall be saved for later use for Impression/Click reporting.
The product field is legacy and can be ignored
The text and gtins fields can be ignored in a standard integration
In gtin field of the above responses you will get the pa_id as in the product feed for the product to be displayed.
Reminder: the pa_id is the concatenation of the catalog prefix and each product SKU, so to identify which SKU to display on your side you may need to remove the catalog prefix and the symbols "--"
pa_id= catprefix--SKU
Requesting Product Ads
To request Product Ads and Banner Ads in the same request, use the maxNumberOfAds field to specify the number of Product Ads requested.
Below is an example requesting 3 Product Ads and 2 Banner Ads
It is necessary for the 2 bannerSlotIds to be created under the same content Standard in order to be used in the same ad request. bannerSlotIds created under different content Standards can't be used in the same request.
sessionId is needed to be included in the ad request as it will be used later in order reporting. For more information please check the "Syncing Order Data" page
If you are unsure of the strings displayed on this page. Take a look at the Reference page.