Post Checkout Banner Ads are an opportunity for retailers to monetize their website experience after a customer has completed their order. As customers are unlikely to remain on the retailer's site or create an additional order, it is heavily advised that this opportunity is opened to third parties to advertise their relevant banners.
The Post Checkout Banner Ads should be implemented in the Thank you page after a user has completed an order.
Post Checkout 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 a product is shown to a customer.
Post Checkout Banner Ads use a similar context to Product Ads, you will need your contentStandardId and bannerSlotIds.
The placement attribute for Post Checkout Banner Ads ads has the value "banner-post-checkout".
Post Checkout Banner Ads will be integrated and serve only in the thank you pages of a website and the position is defined in the Project Agora Commerce Ad Proposal file provided during the beginning of the integration.
The Ingrid Banner Ads use the "Agora Post-checkout" content standard.
You will receive your contentStandardId andbannerSlotIdsfrom Project Agora Commerce once your content standard is generated.
Please note that both contentStandardId and bannerSlotIds are different for the Post Checkout 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.
Minimum Viable Context:
Below are the minimum values needed to generate a post checkout banner 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 products 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
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.