Banner X Ad Integration Guide
Overview
The Banner X Ad Integration Guide explains what a retailer must provide in order to serve Banner X Ads. Project Agora Commerce generates Banner X Ads in a similar way that Project Agora Commerce serves Banner Ads. Retailers have control of generated banners.
Integration Process
The following steps on Project Agora Commerce side will be completed within the Project Agora Commerce staging environment. Once everything is working correctly, you will then be ready for production. The integration process for Banner X Ads is typically straightforward:
Provide necessary data to Project Agora Commerce to generate your content standard
Your content standard will be sent for approval
Once approved, your content standard will be loaded into your namespace and your content standard ID will be generated
Your Banner X endpoint will be generated
Your Banner X creator will be generated
You are ready to request Banner X Ads
Are You Ready to Request BannerX Ads?
This guide assumes you have already created your catalog, created your products, and are sending customer and order data to Project Agora Commerce.
Syncing Catalog & ProductsIn order to request Banner X Ads, you must provide a context. See "The Banner X Ad Context" for more information.
What's the difference between Banner Ads and Banner X Ads?
Banner X ads are responsive banner ads. These are multi-component banners that are served to a retailer's front end. Project Agora Commerce sends each individual component of the banner and the styling of these banners is handled by the retailer's front end. As Banner X banners are multi component, the context and requests are slightly different to normal banners.
There is one noticeable difference in the Banner X context. Where bannerSlotIds
is used in banner ads, slotIds
is used in Banner X ads. Additionally, you are able to call multiple of the same banner slots with the maxNumberOfAds
option.
This can be seen in the example below:
The returned object
As Project Agora Commerce is serving multiple components to a retailer instead of one, the returned object is different. Banner X integrations differ greatly depending on each integration. Below is an example of the banners
section of the returned object for a single Banner X. This would be a simple Banner X Ad:
The Banner X Ad Context
In order to request Banner X Ads, you must provide a context. See "The Banner X Ad Context"
Last updated