Implementing Pentaleap on a New Retailer

If you're not sure where to start with exploring the Pentaleap developer documentation, head to our start page first.

Pentaleap offers a modular onsite SSP and DSP for new and established retail media networks.

Retail Media Networks using Pentaleap need to implement the Fluid Ad Server to make use of SSP and DSP functionality, as described in this documentation.

Retailers and partners can also connect to existing Pentaleap environments via the Campaign and Reporting APIs documented here.

The Pentaleap Fluid Ad Server API is a REST API that is called before you render content to your end user. It is an adserver which connects multiple sources of demand and applies industry-leading relevancy technology to deliver the best possible onsite ads. Our ad server helps you leverage AI, inventory data, user data, product popularity, and business signals to show more relevant ads.

A single API call is used for all Pentaleap ad types (sponsored products, sponsored brand and onsite display ads) and demand types (first or third party), so one implementation unlocks all types of onsite advertising.

Using page context which you share with us, demand from first or third parties, and the rules that you set up in the Publisher Manager UI, you receive a response indicating ads to show, their positions, and some measurement beacons.

The overall information flow is as follows:

Integration timelines vary by retailer, but Pentaleap's Adserver API is designed to be deployed in max 2-4 weeks and with minimal development effort.

Provide a Product Feed for the system to work from based on your product catalog. See Import the Product Feed

Integrate the Fluid Ad Server into the retailer backend. See Implement Fluid Adserver API

Impression, click and conversion events to track ad performance, based on the pre-encrypted links which Pentaleap provides in the ad response - see Implement Tracking Events