Three kinds of tracking are required to implement our tracking protocol: 

For click and impression tracking, Crealytics provides encrypted tracking links in the ad response. The retailer system simply has to send a GET request to the URL when the product is shown or clicked.

Conversion tracking requires the retailer to send a POST request with the userID and product/transaction information.

Fluid Ad Unit v2

Implement Tracking Events

endpoint for delivering impression events back to the tracking infrastructure via tracking link

Fluid Adserver API

Implementing the Crealytics Retail Media Platform

Pentaleap Fluid Adserver

Implementing Pentaleap
on a New Retailer

Minimum Specifications

Import the Product Feed

Request and Response Overview

FAQs about the ad response

SPA V3

SPA-Adserver

Display V3

Download OpenAPI file

Implement Fluid Ad Server

Spa-tracker

Display

SPA-Tracker

Warmup v2 Request (Beta)

RM-Demand-Mediator v2 API

[Optional] Implement Warmup for Demand Source calls